On Tue, Mar 2, 2010 at 02:06, Steven D'Aprano <st...@pearwood.info> wrote:
> On Tue, 2 Mar 2010 11:59:55 am Barry Warsaw wrote: > > Thanks everybody for providing great input on this aspect of the PEP. > > I've updated the open issues section to include a list of the > > possible resolutions for bytecode-only imports. Unless anybody has > > more ideas, it might just be time to get a BDFL pronouncement. > > Please excuse me if these minor points have already been discussed, but > I couldn't see them in the PEP. > > (1) What happens if the __cache__ directory doesn't exist and the > enclosing directory is unwriteable, or if it does exist, but is > unreadable? > > I expect that the byte code files will simply not be created, and > everything will continue without them. > > (2) Presumably this only effects imports, not running python source code > as a script. If I do this: > > python myscript.py > > from the shell, I would expect that no __cache__ directory will be > created, just like today. > > BTW, you have some sort of automated warning in the PEP: > > System Message: WARNING/2 (pep-3147.txt, line 237) > Title underline too short. > > http://www.python.org/dev/peps/pep-3147/#id47 It's now fixed. Barry forgot to run the Makefile for the PEPs before checking in. Shame! =) -Brett > > > > > -- > Steven D'Aprano > _______________________________________________ > 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/brett%40python.org >
_______________________________________________ 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
