views:

758

answers:

3

This is a very basic question - but I haven't been able to find an answer by searching online.

I am using python to control ArcGIS, and I have a simple python script, that calls some pre-written code.

However, when I make a change to the pre-written code, it does not appear to result in any change. I import this module, and have tried refreshing it, but nothing happens.

I've even moved the file it calls to another location, and the script still works fine. One thing I did yesterday was I added the folder where all my python files are to the sys path (using sys.append('path') ), and I wonder if that made a difference.

Thanks in advance, and sorry for the sloppy terminology.

+3  A: 

One way to do this is to call reload.

Example: Here is the contents of foo.py:

def bar():
    return 1

In an interactive session, I can do:

>>> import foo
>>> foo.bar()
1

Then in another window, I can change foo.py to:

def bar():
    return "Hello"

Back in the interactive session, calling foo.bar() still returns 1, until I do:

>>> reload(foo)
<module 'foo' from 'foo.py'>
>>> foo.bar()
'Hello'

Calling reload is one way to ensure that your module is up-to-date even if the file on disk has changed. It's not necessarily the most efficient (you might be better off checking the last modification time on the file or using something like pyinotify before you reload), but it's certainly quick to implement.

One reason that Python doesn't read from the source module every time is that loading a module is (relatively) expensive -- what if you had a 300kb module and you were just using a single constant from the file? Python loads a module once and keeps it in memory, until you reload it.

Mark Rushakoff
+1  A: 

I'm not really sure that is what you mean, so don't hesitate to correct me. You are importing a module - let's call it mymodule.py - in your program, but when you change its contents, you don't see the difference?

Python will not look for changes in mymodule.py each time it is used, it will load it a first time, compile it to bytecode and keep it internally. It will normally also save the compiled bytecode (mymodule.pyc). The next time you will start your program, it will check if mymodule.py is more recent than mymodule.pyc, and recompile it if necessary.

If you need to, you can reload the module explicitly:

import mymodule

[... some code ...]

if userAskedForRefresh:
    reload(mymodule)

Of course, it is more complicated than that and you may have side-effects depending on what you do with your program regarding the other module, for example if variables depends on classes defined in mymodule.

Alternatively, you could use the execfile function (or exec(), eval(), compile())

RedGlyph
Thank you all for your answers. I have tried using reload, and closing/reopening the program.The problem turned out to be caused by a file that was named the same, in the original code. Even though I thought I was importing it from a new location, it was still using the old file.
womble
+1  A: 

It's unclear what you mean with "refresh", but the normal behavior of Python is that you need to restart the software for it to take a new look on a Python module and reread it.

If your changes isn't taken care of even after restart, then this is due to one of two errors:

  1. The timestamp on the pyc-file is incorrect and some time in the future.
  2. You are actually editing the wrong file.

You can with reload re-read a file even without restarting the software with the reload() command. Note that any variable pointing to anything in the module will need to get reimported after the reload. Something like this:

import themodule
from themodule import AClass

reload(themodule)
from themodule import AClass
Lennart Regebro