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-August/091464.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?Guido van Rossum guido at python.org
Mon Aug 31 02:26:08 CEST 2009 
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/)
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