-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
bpo-29514: Check magic number for bugfix release #54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,6 +4,7 @@ | |
machinery = util.import_importlib('importlib.machinery') | ||
importlib_util = util.import_importlib('importlib.util') | ||
|
||
import importlib.util | ||
import os | ||
import pathlib | ||
import string | ||
|
@@ -757,5 +758,48 @@ def test_source_from_cache_path_like_arg(self): | |
) = util.test_both(PEP3147Tests, util=importlib_util) | ||
|
||
|
||
class MagicNumberTests(unittest.TestCase): | ||
""" | ||
Test release compatibility issues relating to importlib | ||
""" | ||
@unittest.skipUnless( | ||
sys.version_info.releaselevel in ('final', 'release'), | ||
'only applies to candidate or final python release levels' | ||
) | ||
def test_magic_number(self): | ||
""" | ||
Each python minor release should generally have a MAGIC_NUMBER | ||
that does not change once the release reaches candidate status. | ||
|
||
Once a release reaches candidate status, the value of the constant | ||
EXPECTED_MAGIC_NUMBER in this test should be changed. | ||
This test will then check that the actual MAGIC_NUMBER matches | ||
the expected value for the release. | ||
|
||
In exceptional cases, it may be required to change the MAGIC_NUMBER | ||
for a maintenance release. In this case the change should be | ||
discussed in python-dev. If a change is required, community | ||
stakeholders such as OS package maintainers must be notified | ||
in advance. Such exceptional releases will then require an | ||
adjustment to this test case. | ||
""" | ||
EXPECTED_MAGIC_NUMBER = 3379 | ||
actual = int.from_bytes(importlib.util.MAGIC_NUMBER[:2], 'little') | ||
|
||
msg = ( | ||
"To avoid breaking backwards compatibility with cached bytecode " | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Wouldn't be better to use a multiline string literal if you want such verbose error message? But I think that "broken *.pyc files compatibility" would be enough. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Then you'd have to dedent it, etc. This message is perfectly legible to me. |
||
"files that can't be automatically regenerated by the current " | ||
"user, candidate and final releases require the current " | ||
"importlib.util.MAGIC_NUMBER to match the expected " | ||
"magic number in this test. Set the expected " | ||
"magic number in this test to the current MAGIC_NUMBER to " | ||
"continue with the release.\n\n" | ||
"Changing the MAGIC_NUMBER for a maintenance release " | ||
"requires discussion in python-dev and notification of " | ||
"community stakeholders." | ||
) | ||
self.assertEqual(EXPECTED_MAGIC_NUMBER, actual, msg) | ||
|
||
|
||
if __name__ == '__main__': | ||
unittest.main() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be better to write this as a comment rather than a docstring. If you want, add a one-line docstring, but most test methods don't have docstrings.