On Saturday, May 19, 2012 7:54:18 PM UTC+8, Colin J. Williams wrote:
> On 18/05/2012 7:20 PM, Tony the Tiger wrote:
> > On Sun, 13 May 2012 23:36:02 +0200, Irmen de Jong wrote:
> >
> >> Why do you care anyway?
> >
> > Wanna hide his code...?
> >
> > /Grrr
> Curiosity. Perhaps there are st ack-ba
On 18/05/2012 7:20 PM, Tony the Tiger wrote:
On Sun, 13 May 2012 23:36:02 +0200, Irmen de Jong wrote:
Why do you care anyway?
Wanna hide his code...?
/Grrr
Curiosity. Perhaps there are stack-based processors out there which
could use the .pyc code more directly.
Colin W.
--
http://mail
On Sun, 13 May 2012 23:36:02 +0200, Irmen de Jong wrote:
> On 13-5-2012 23:27, Colin J. Williams wrote:
>> Is there some way to ensure that a .pyc file is produced when executing
>> a .py file?
>>
>> It seems that for small files the .pyc file is not produced.
>>
>> Colin W.
>
> All modules no
On 05/13/12 16:36, Irmen de Jong wrote:
> Why do you care anyway? Pyc files are an implementation detail.
I could see wanting to pre-compile .pyc files for performance if
they'll then be stored on a read-only medium (a CD/DVD, a RO network
share, or a RO drive partition all come to mind).
You can
On 13-5-2012 23:27, Colin J. Williams wrote:
> Is there some way to ensure that a .pyc file is produced when executing a .py
> file?
>
> It seems that for small files the .pyc file is not produced.
>
> Colin W.
All modules no matter how small produce a .pyc file *when they are imported*.
If yo
