A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2009-September/091511.html below:

[Python-Dev] how important is setting co_filename for a module being imported to what __file__ is set to?

[Python-Dev] how important is setting co_filename for a module being imported to what __file__ is set to? [Python-Dev] how important is setting co_filename for a module being imported to what __file__ is set to?P.J. Eby pje at telecommunity.com
Tue Sep 1 00:06:37 CEST 2009
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?

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4