On Mon, 22 Mar 2010 18:15:01 -0000, Antoine Pitrou <solip...@pitrou.net> wrote: > Isaac Morland <ijmorlan <at> uwaterloo.ca> writes: > > > > > IMO, all these issues militate for putting __pycache__ creation out of > > > the interpreter core, and in the hands of third-party package-time/ > > > install-time tools (or distutils). > > > > Speaking only for myself, but really for anybody who likes tidy source > > directories, I hope some version of the __pycache__ proposal becomes part > > of standard Python, by which I ideally mean it's enabled by default but if > > that is just not a good idea then at most it should be required to set a > > command-line option to get this feature. > > This doesn't contradict by my proposal. > > What I am proposing is that the creation of __pycache__ /directories/ be put > outside of the core. It can be part of distutils, or of a separate module, or > delegated to third-party tools. It could even be as simple as > "python -m compileall --pycache", if someone implements it.
Or even as simple as 'mkdir __pycache__', if you are working in your own library and don't want .pyc clutter. -- R. David Murray www.bitdance.com _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
