[Python-Dev] how important is setting co_filename for a module being imported to what file is set to? (original) (raw)
P.J. Eby pje at telecommunity.com
Tue Sep 1 00:06:37 CEST 2009
- 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 ]
At 02:57 PM 8/31/2009 -0700, Brett Cannon wrote:
Ignoring that 'new' is not in Python 3.x (luckily 'types' is), I want a proper solution that doesn't require reconstructing every code object that I happen to import.
Practicality beats purity. ;-) (Especially if it allows importlib to run on older Pythons.)
Also, surely you're not worried about performance here?
- 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 ]