[issue1180193] broken pyc files

2009-01-06 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: Committed to trunk and py3k, and backported to 2.6 and 3.0. Thanks! -- resolution: accepted - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1180193

[issue1180193] broken pyc files

2009-01-05 Thread Jean-Paul Calderone
Jean-Paul Calderone exar...@divmod.com added the comment: This is causing problems for me as well. The attached patch no longer applies cleanly to trunk. I've attached an updated version which addresses the conflicts. The new behavior fixes the issues I have with the current behavior. It'd

[issue1180193] broken pyc files

2009-01-05 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: As Armin said, I think it's safer and simpler not to rewrite the pyc file when the filenames have been changed. (if you thing changing the filenames can have a significant performance impact, you may want to benchmark it)

[issue1180193] broken pyc files

2009-01-05 Thread Jean-Paul Calderone
Jean-Paul Calderone exar...@divmod.com added the comment: New version of the patch which doesn't rewrite pyc files attached. Added file: http://bugs.python.org/file12599/update_co_filename.diff ___ Python tracker rep...@bugs.python.org

[issue1180193] broken pyc files

2008-01-23 Thread Antoine Pitrou
Antoine Pitrou added the comment: If code objects grew a __module__ attribute (which functions already have), wouldn't it be just a matter of falling back on sys.modules[my_code_object.__module__].__file__ when my_code_object.co_filename points to a non-existent file? -- nosy: +pitrou

[issue1180193] broken pyc files

2008-01-05 Thread Christian Heimes
Changes by Christian Heimes: -- type: - rfe versions: +Python 2.6 _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1180193 _ ___ Python-bugs-list mailing list