Alternate name for __pycache__

[rhettinger]

BPO	11154
Nosy	@warsaw, @birkenfeld, @rhettinger, @pitrou, @merwok, @davidmalcolm

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/warsaw'
closed_at = <Date 2011-02-09.17:54:52.595>
created_at = <Date 2011-02-08.22:43:55.834>
labels = ['type-feature']
title = 'Alternate name for __pycache__'
updated_at = <Date 2011-02-09.17:54:52.594>
user = 'https://github.com/rhettinger'

bugs.python.org fields:

activity = <Date 2011-02-09.17:54:52.594>
actor = 'rhettinger'
assignee = 'barry'
closed = True
closed_date = <Date 2011-02-09.17:54:52.595>
closer = 'rhettinger'
components = []
creation = <Date 2011-02-08.22:43:55.834>
creator = 'rhettinger'
dependencies = []
files = []
hgrepos = []
issue_num = 11154
keywords = []
message_count = 6.0
messages = ['128194', '128221', '128222', '128224', '128225', '128227']
nosy_count = 6.0
nosy_names = ['barry', 'georg.brandl', 'rhettinger', 'pitrou', 'eric.araujo', 'dmalcolm']
pr_nums = []
priority = 'high'
resolution = 'rejected'
stage = None
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue11154'
versions = ['Python 3.2']

[rhettinger]

It would be great if the "__pycache__" name could be set by an environment variable. I would like to rename it to ".pycache" so that it doesn't pollute my directory listings.

[warsaw]

Hmm. That's problematic. How would that interact with a system Python that is already looking in __pycache__ for its pyc files? Would it suddenly start ignoring those and wanting to write them to .pycache?

IIRC we thought about something like this during the PEP discussions and Guido nixed it.

-1

[davidmalcolm]

On Wed, 2011-02-09 at 16:41 +0000, Barry A. Warsaw wrote:

IIRC we thought about something like this during the PEP discussions and Guido nixed it.

FWIW, the closest I could find was this mail:
http://www.mail-archive.com/python-dev@python.org/msg45203.html
(doesn't seem to be in the mail.python.org archives)
where GvR said:

Because we don't want to completely hide the pyc files. Also the dot
naming convention is somewhat platform-specific.

(FWIW, I wish we'd gone for .pycache too, but I guess it's too late to change now)

[pitrou]

I agree with barry's argument and also with Marc-André's argument on python-ideas. Your directories are far cleaner than before with pyc files all around, so what is the problem exactly?

[rhettinger]

That makes sense. Making it configurable would lose some of the benefits.

What we could do though, before 3.2 goes out, is change the name to ".pycache" to follow the dot-file naming convention and avoid cluttering directory listings.

[rhettinger]

I just saw a post from Guido saying that he doesn't want the directory to be invisible.