[Python-Dev] how important is setting co_filename for a module being imported to what file is set to? (original) (raw)
Guido van Rossum guido at python.org
Mon Aug 31 02:26:08 CEST 2009
- Previous message: [Python-Dev] how important is setting co_filename for a module being imported to what __file__ is set to?
- Next message: [Python-Dev] how important is setting co_filename for a module being imported to what __file__ is set to?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, Aug 30, 2009 at 5:23 PM, Brett Cannon<brett at python.org> wrote:
Right; the code object would think it was loaded from the original location it was created at instead of where it actually is. Now why someone would want to move their .pyc files around instead of recompiling I don't know short of not wanting to send someone source.
I already mentioned replication; it could also just be a matter of downloading a tarball with .py and .pyc files.
-- --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] how important is setting co_filename for a module being imported to what __file__ is set to?
- Next message: [Python-Dev] how important is setting co_filename for a module being imported to what __file__ is set to?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]