Message 57150 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	amaury.forgeotdarc
Recipients	amaury.forgeotdarc, christian.heimes, gvanrossum
Date	2007-11-06.00:39:57
SpamBayes Score	0.0405492
Marked as misclassified	No
Message-id	<1194309597.69.0.788229485502.issue1384@psf.upfronthosting.co.za>
In-reply-to

Content
Yes, the patch is needed. The problem arises when you run the python executable in different ways WITHOUT deleting the .pyc files. Example on my machine: Note that the exact path to run python is not the same: >cd C:\dev\python\py3k\PCbuild8 >del /s ..\*.pyc >c:\dev\python\py3k\PCbuild8\win32debug\python_d.exe -E -tt ../lib/test/regrtest.py -v test_inspect [test OK] >C:\dev\python\py3k\PCbuild8\win32debug\python_d.exe -E -tt ../lib/test/regrtest.py -v test_inspect [test FAILED] If I always use the same path the tests succeed.

Yes, the patch is needed.
The problem arises when you run the python executable in different ways
WITHOUT deleting the .pyc files.

Example on my machine: Note that the exact path to run python is not the
same:

>cd C:\dev\python\py3k\PCbuild8
>del /s ..\*.pyc
>c:\dev\python\py3k\PCbuild8\win32debug\python_d.exe -E -tt
../lib/test/regrtest.py -v test_inspect
[test OK]
>C:\dev\python\py3k\PCbuild8\win32debug\python_d.exe -E -tt
../lib/test/regrtest.py -v test_inspect
[test FAILED]

If I always use the same path the tests succeed.

History
Date	User	Action	Args
2007-11-06 00:39:57	amaury.forgeotdarc	set	spambayes_score: 0.0405492 -> 0.0405492 recipients: + amaury.forgeotdarc, gvanrossum, christian.heimes
2007-11-06 00:39:57	amaury.forgeotdarc	set	spambayes_score: 0.0405492 -> 0.0405492 messageid: <1194309597.69.0.788229485502.issue1384@psf.upfronthosting.co.za>
2007-11-06 00:39:57	amaury.forgeotdarc	link	issue1384 messages
2007-11-06 00:39:57	amaury.forgeotdarc	create