Bugs item #1731068, was opened at 2007-06-04 16:21 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1731068&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Blake Ross (blakeross) Assigned to: Nobody/Anonymous (nobody) Summary: Importing a submodule after unloading its parent Initial Comment: It seems that if you import a submodule, cause its parent package to be destroyed, then attempt to re-import the submodule, the parent package is properly re-imported but the submodule does not get set on it. The session below demonstrates this. After the second xml.sax import, "xml" is the xml package module as expected, but xml.sax does not exist. I'm not familiar with all of the import semantics, but it seems odd to me that "foo.bar" could ever fail to exist right after an "import foo.bar". Python 2.5 (r25:51908, Sep 19 2006, 09:52:17) [MSC v.1310 32 bit (Intel)] o 32 Type "help", "copyright", "credits" or "license" for more information. >>> import sys, xml.sax >>> del xml, sys.modules["xml"] >>> import xml.sax >>> xml.sax Traceback (most recent call last): File "<stdin>", line 1, in <module> AttributeError: 'module' object has no attribute 'sax' >>> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1731068&group_id=5470 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
