In article ,
Baz Walter wrote:
>
>i thought that python automatically compiled pyc files after a module is
>successfully imported. what could prevent this happening?
Looks like you got your problem fixed, but for the record, not having
write permission on a directory also causes this. It's eve
Peter Otten wrote:
You did not set the PYTHONDONTWRITEBYTECODE environment variable in a former
life, or did you?
thanks peter
no i didn't, but i've just discovered a script in /etc/profile.d that
did. now i'll have to try to find out how that script got in there :-|
--
http://mail.python.o
Baz Walter wrote:
> i thought that python automatically compiled pyc files after a module is
> successfully imported. what could prevent this happening?
>
>
> Python 2.6.1 (r261:67515, Apr 12 2009, 03:51:25)
> [GCC 4.3.2] on linux2
> Type "help", "copyright", "credits" or "license" for more info
On Jul 26, 5:22 pm, Baz Walter wrote:
> hello
>
> i thought that python automatically compiled pyc files after a module is
> successfully imported. what could prevent this happening?
>
> Python 2.6.1 (r261:67515, Apr 12 2009, 03:51:25)
> [GCC 4.3.2] on linux2
> Type "help", "copyright", "credits"
hello
i thought that python automatically compiled pyc files after a module is
successfully imported. what could prevent this happening?
Python 2.6.1 (r261:67515, Apr 12 2009, 03:51:25)
[GCC 4.3.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import os
