Issue 12120: test_packaging failure - Python tracker (original) (raw)

Created on 2011-05-19 16:22 by pitrou, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (10)
msg136302 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2011-05-19 16:22
I get the following failure under a fresh checkout: ====================================================================== FAIL: test_package_data (packaging.tests.test_command_build_py.BuildPyTestCase) ---------------------------------------------------------------------- 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']
msg136308 - (view) Author: Tarek Ziadé (tarek) * (Python committer) Date: 2011-05-19 16:43
on it
msg136310 - (view) Author: Tarek Ziadé (tarek) * (Python committer) Date: 2011-05-19 16:48
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 ?
msg136311 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2011-05-19 16:50
> 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. It doesn't. Have you seen http://bugs.python.org/issue12119 ? > Any special way to run the tests ? No. This is a fresh checkout on a fresh Linux install. Only zlib is available (not bz2 etc.).
msg136319 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2011-05-19 17:30
This is due to PYTHONDONTWRITEBYTECODE being set. Not sure this is worth fixing.
msg136324 - (view) Author: Tarek Ziadé (tarek) * (Python committer) Date: 2011-05-19 17:44
a well, we can skip that pyc test in case PYTHONDONTWRITEBYTECODE is set, thanks !
msg136325 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2011-05-19 17:51
> 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.
msg136326 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2011-05-19 17:56
New changeset 9d1fb6a9104b by Tarek Ziade in branch 'default': Issue #12120, Issue #12119: tests were missing a sys.dont_write_bytecode check http://hg.python.org/cpython/rev/9d1fb6a9104b
msg136347 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2011-05-20 00:12
Duplicate of #12117.
msg146942 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2011-11-03 16:24
I have improved packaging to be independent of -B/-O in http://hg.python.org/cpython/rev/dad02a080bbc. See commit message for rationale.
History
Date User Action Args
2022-04-11 14:57:17 admin set github: 56329
2011-11-03 16:24:48 eric.araujo set assignee: tarek -> eric.araujostage: resolvedmessages: + versions: + 3rd party
2011-05-20 00:12:55 vstinner set status: open -> closednosy: + vstinnermessages: + resolution: fixed
2011-05-19 17:56:24 python-dev set nosy: + python-devmessages: +
2011-05-19 17:51:45 pitrou set messages: +
2011-05-19 17:44:16 tarek set messages: +
2011-05-19 17:30:59 pitrou set messages: +
2011-05-19 16:50:22 pitrou set messages: +
2011-05-19 16:48:17 tarek set messages: +
2011-05-19 16:43:44 tarek set messages: +
2011-05-19 16:22:08 pitrou create