[Format recovered from top posting.]
"James Martin" <[EMAIL PROTECTED]> writes:
>
>
> "Amir Dekel" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>> Hello everyone,
>> First, I have to say that Python is one of the coolest programing
>> languages I have seen.
>> And now for the problem (must be a silly one):
>> When I import a module I have wrote, and then I find bugs, it seems that
>> I can't import it again after a fix it. It always shows the same
>> problem. I try del module but it doesn't work.
>> (I use Python 2.4 with the ActivePython pack (PythonWin IDE)
>>
>> Solution anyone?
> Try deleting the Compiled Python File that was created during import --
> extension pyc. Then import again.
>
> It seems to me (I'm a novice too) that, when you import a module, Python
> automatically compiles it. Then when you import it later, the compiled
> version is imported if it exists.
It compares the dates on the .py file with the .pyc file, and
recompiles the .py file if it's newer.
Doing a second import will find the module in sys.modules and not
bother looking in the file system. The solution is to reload(module)
instead of import module.
<mike
--
Mike Meyer <[EMAIL PROTECTED]> http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
--
http://mail.python.org/mailman/listinfo/python-list
