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/2011-February/108109.html below:

[Python-Dev] "Some" .pyc files not ending up in __pycache__ during installation

[Python-Dev] "Some" .pyc files not ending up in __pycache__ during installation [Python-Dev] "Some" .pyc files not ending up in __pycache__ during installation"Martin v. Löwis" martin at v.loewis.de
Sat Feb 19 14:27:56 CET 2011 
Am 19.02.2011 14:14, schrieb Antoine Pitrou:
> On Sat, 19 Feb 2011 23:07:17 +1000
> Nick Coghlan <ncoghlan at gmail.com> wrote:
>>
>> While this is definitely untidy, it doesn't strike me as a release
>> blocker. More of a "fix it in 3.2.1", since the status quo will
>> *work*, it just means the precompiled file will be ignored on first
>> execution with newer Python versions.
> 
> Are you sure? If the package gets installed in a root-writable-only
> directory, later execution cannot create the right pyc files.

It will certainly work. It won't create pyc files, but it will still
work - right?

Regards,
Martin
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