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

Showing content from https://mail.python.org/pipermail/python-dev/2011-February/108107.html below:

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

• Previous message: [Python-Dev] "Some" .pyc files not ending up in __pycache__ during installation
• Next message: [Python-Dev] "Some" .pyc files not ending up in __pycache__ during installation
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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.

This certainly looks like a critical issue (hopefully not release
blocker).

• Previous message: [Python-Dev] "Some" .pyc files not ending up in __pycache__ during installation
• Next message: [Python-Dev] "Some" .pyc files not ending up in __pycache__ during installation
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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