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
test_packaging failure #56329
Comments
I get the following failure under a fresh checkout: ====================================================================== Traceback (most recent call last):
File "/home/antoine/t/cpython/Lib/packaging/tests/test_command_build_py.py", line 64, in test_package_data
self.assertIn("__init__.pyc", files)
AssertionError: '__init__.pyc' not found in ['README.txt', '__init__.py'] |
on it |
I cannot reproduce this. there's exactly the same test in distutils, so I am wondering why it passes there and not in packaging for you. Any special way to run the tests ? |
It doesn't. Have you seen http://bugs.python.org/issue12119 ?
No. This is a fresh checkout on a fresh Linux install. Only zlib is |
This is due to PYTHONDONTWRITEBYTECODE being set. Not sure this is worth fixing. |
a well, we can skip that pyc test in case PYTHONDONTWRITEBYTECODE is set, thanks ! |
It's better to test sys.flags.dont_write_bytecode, actually. |
New changeset 9d1fb6a9104b by Tarek Ziade in branch 'default': |
Duplicate of bpo-12117. |
I have improved packaging to be independent of -B/-O in http://hg.python.org/cpython/rev/dad02a080bbc. See commit message for rationale. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: