92e9e35292
Add a test to check the current MAGIC_NUMBER against the expected number for the release if the current release is at candidate or final level. On test failure, describe to the developer the procedure for changing the magic number. This ensures that pre-merge CI will automatically pick up on magic number changes in maintenance releases (and explain why those are problematic), rather than relying on all core developers to be aware of the implications of such changes. |
||
|---|---|---|
| .. | ||
| builtin | ||
| extension | ||
| frozen | ||
| import_ | ||
| namespace_pkgs | ||
| source | ||
| __init__.py | ||
| __main__.py | ||
| abc.py | ||
| test_abc.py | ||
| test_api.py | ||
| test_lazy.py | ||
| test_locks.py | ||
| test_namespace_pkgs.py | ||
| test_spec.py | ||
| test_util.py | ||
| test_windows.py | ||
| util.py | ||