Message873
The problem appears to be that "imp" in its import_name method is setting the name of the module to Py.None if it can't find it the first time. This causes the system to block the import from that point onward:
if (topMod == Py.None || topMod == null) {
if (topMod == null) {
modules.__setitem__(parentNameBuffer.toString().intern(),
Py.None);
}
parentNameBuffer = new StringBuffer("");
// could throw ImportError
topMod = import_first(firstName, parentNameBuffer, name, fromlist);
}
The question is, if this changed, what is going to be broken... |
|
Date |
User |
Action |
Args |
2008-02-20 17:17:16 | admin | link | issue837308 messages |
2008-02-20 17:17:16 | admin | create | |
|