__pycache__, one more good reason to stck with Python 2?

[Brian Curtin]

On Mon, Jan 17, 2011 at 08:31, jmfauth <wxjmfauth at gmail.com> wrote:

> As a scientist using computer tools, and not as a computer
> scientist, I discovered Python long time ago (it was in its
> 1.5.6 version) and I remain an happy user up to now date.
> Yesterday, I was happy to download and test Python 3.2rc1.
> Python is still this powerful and pleasant language, but...
>
> I fall on this cached pyc's directory, __pycache__. Without
> to many explanations (I think they will be obvious for an
> end user), one word: a nithtmare.


What are the specific problems you've seen with __pycache__? Have you read
PEP 3147 [0], at least through the rationale section?

[0] http://www.python.org/dev/peps/pep-3147/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20110117/f2ff0d84/attachment-0001.html>