Re: Docstrings and PEP 3174

2010-08-01 Thread Steven D'Aprano
On Sun, 01 Aug 2010 20:30:22 +1200, Gregory Ewing wrote: > Steven D'Aprano wrote: > >> If you mean a runtime optimization with no change to the source file, >> then maybe, tell me more. > > Note that you don't necessarily need a separate file for this. It could > just be a separate part of the s

Re: Docstrings and PEP 3174

2010-08-01 Thread Carl Banks
On Aug 1, 4:26 pm, Terry Reedy wrote: > On 8/1/2010 4:30 AM, Gregory Ewing wrote: > > > Steven D'Aprano wrote: > > >> If you mean a runtime optimization with no change to the source file, > >> then maybe, tell me more. > > > Note that you don't necessarily need a separate file for this. > > It cou

Re: Docstrings and PEP 3174

2010-08-01 Thread Terry Reedy
On 8/1/2010 4:30 AM, Gregory Ewing wrote: Steven D'Aprano wrote: If you mean a runtime optimization with no change to the source file, then maybe, tell me more. Note that you don't necessarily need a separate file for this. It could just be a separate part of the same file. Which is to say,

Re: Docstrings and PEP 3174

2010-08-01 Thread Gregory Ewing
Steven D'Aprano wrote: If you mean a runtime optimization with no change to the source file, then maybe, tell me more. Note that you don't necessarily need a separate file for this. It could just be a separate part of the same file. -- Greg -- http://mail.python.org/mailman/listinfo/python-li

Re: Docstrings and PEP 3174

2010-08-01 Thread Steven D'Aprano
On Sat, 31 Jul 2010 19:52:05 -0700, Carl Banks wrote: > PEP 3174 got me to thinking. > > There is now a subdirectory to deposit as many *.pyc files as you want > without cluttering the source directory (never mind the default case). > Which means you can pretty much write files with impunity. >