$ python
>>> import myapp
>>> reload(myapp)
<module 'myapp' from 'myapp.pyc'>
>>>
ctrl+D
$ python
>>> from myapp import *
>>> reload(myapp)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
NameError: name 'myapp' is not defined
Why this behaves differently? How can I reload when using from myapp import *?
From http://docs.python.org/library/functions.html#reload :
If a module imports objects from another module using from ... import ..., calling reload() for the other module does not redefine the objects imported from it — one way around this is to re-execute the from statement, another is to use import and qualified names (module.name) instead.
So, you should do something like:
from myapp import *
....
import myapp
reload(myapp)
from myapp import *
With from myapp import *, you don't have a reference to your module in a variable name, so you can't use a variable name to refer to the module.
Of course, there's nothing preventing you from importing it again to get the reference to the module in a name you can use. Since it's already been imported once, it won't actually be imported again:
import myapp
reload(myapp)
You can also get the reference directly from sys.modules.
import sys
reload(sys.modules["myapp]")
from foo import *. This may or many not make the reload useless.
To clarify Wooble's comment, using "from foo import *" brings everything from foo into the current namespace. This can lead to name collisions (where you unintentionally assign a new value to a name already in use) and can also make it harder to tell where something came from. While a few libraries are often used this way, it generally causes more problems than it is worth.
Also, since it has been brought into the current namespace it cannot simply be reloaded. It is generally better to keep it in a separate namespace (perhaps with a shorter convenience alias like just m). This allows you to reload (which is useful for testing, but rarely a good idea outside of testing) and helps keept he namespace pure.
reloadis to be used with a lot of caution. It behaves unexpected in many ways, the worst of which is that classes exist in many versions inside the VM, depending on whether you have old instances of reloaded classes hanging around.reloadwas removed from Python 3 for that reason. Often it's much easier to set up a small script setting up all the modules you need and then drop into a shell usingimport code; code.interact(local=locals()). The Python interpreter starts up really fast, so this is usually even faster then searching forreloadin the readline history.