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

[Steven D'Aprano]

On Mon, 17 Jan 2011 06:31:00 -0800, jmfauth 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.

No, I'm sorry, they're not obvious at all. I too have been using Python 
since version 1.5 (although I don't remember the minor point release), 
and I've also been testing Python 3.2, but I'm afraid I have no idea why 
you think that __pycache__ is a nightmare.


-- 
Steven