From: SourceForge.net <no...@so...> - 2006-07-12 17:48:37
|
Bugs item #1521362, was opened at 2006-07-12 12:48 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112867&aid=1521362&group_id=12867 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 Submitted By: Charles Groves (cgroves) Assigned to: Nobody/Anonymous (nobody) Summary: second import of broken module succeeds Initial Comment: If I have a module that throws an exception on import, the first time I try to import it I get an ImportError. The second time I try to import it, the import succeeds. milo:~/dev/jython groves$ jytip Jython 2.2a1 on java1.5.0_06 (JIT: null) Type "copyright", "credits" or "license" for more information. >>> try: ... import badmodule ... except: ... pass ... >>> import badmodule >>> print badmodule <module 'badmodule' from '/Users/groves/dev/jython/badmodule.py'> milo:~/dev/jython groves$ python Python 2.4.3 (#1, Apr 7 2006, 10:54:33) [GCC 4.0.1 (Apple Computer, Inc. build 5250)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> try: ... import badmodule ... except: ... pass ... >>> import badmodule Traceback (most recent call last): File "<stdin>", line 1, in ? File "/Users/groves/dev/jython/badmodule.py", line 1, in ? import nonexistentmodule ImportError: No module named nonexistentmodule ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112867&aid=1521362&group_id=12867 |
From: SourceForge.net <no...@so...> - 2006-07-12 18:14:13
|
Bugs item #1521362, was opened at 2006-07-12 12:48 Message generated for change (Comment added) made by cgroves You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112867&aid=1521362&group_id=12867 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 Submitted By: Charles Groves (cgroves) Assigned to: Nobody/Anonymous (nobody) Summary: second import of broken module succeeds Initial Comment: If I have a module that throws an exception on import, the first time I try to import it I get an ImportError. The second time I try to import it, the import succeeds. milo:~/dev/jython groves$ jytip Jython 2.2a1 on java1.5.0_06 (JIT: null) Type "copyright", "credits" or "license" for more information. >>> try: ... import badmodule ... except: ... pass ... >>> import badmodule >>> print badmodule <module 'badmodule' from '/Users/groves/dev/jython/badmodule.py'> milo:~/dev/jython groves$ python Python 2.4.3 (#1, Apr 7 2006, 10:54:33) [GCC 4.0.1 (Apple Computer, Inc. build 5250)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> try: ... import badmodule ... except: ... pass ... >>> import badmodule Traceback (most recent call last): File "<stdin>", line 1, in ? File "/Users/groves/dev/jython/badmodule.py", line 1, in ? import nonexistentmodule ImportError: No module named nonexistentmodule ---------------------------------------------------------------------- >Comment By: Charles Groves (cgroves) Date: 2006-07-12 13:14 Message: Logged In: YES user_id=1174327 The attached patch fixes this problem. It surrounds the actual import code with a try catch, and if an exception is thrown it removes the module from the modules list and rethrows the exception. I think all import code eventually flows through here to actually run the import so I think it fixes everything, but someone with more knowledge of the Jython import system should probably take a look at this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112867&aid=1521362&group_id=12867 |
From: SourceForge.net <no...@so...> - 2006-07-12 18:19:22
|
Bugs item #1521362, was opened at 2006-07-12 12:48 Message generated for change (Settings changed) made by cgroves You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112867&aid=1521362&group_id=12867 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: Deleted Resolution: None Priority: 5 Submitted By: Charles Groves (cgroves) Assigned to: Nobody/Anonymous (nobody) Summary: second import of broken module succeeds Initial Comment: If I have a module that throws an exception on import, the first time I try to import it I get an ImportError. The second time I try to import it, the import succeeds. milo:~/dev/jython groves$ jytip Jython 2.2a1 on java1.5.0_06 (JIT: null) Type "copyright", "credits" or "license" for more information. >>> try: ... import badmodule ... except: ... pass ... >>> import badmodule >>> print badmodule <module 'badmodule' from '/Users/groves/dev/jython/badmodule.py'> milo:~/dev/jython groves$ python Python 2.4.3 (#1, Apr 7 2006, 10:54:33) [GCC 4.0.1 (Apple Computer, Inc. build 5250)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> try: ... import badmodule ... except: ... pass ... >>> import badmodule Traceback (most recent call last): File "<stdin>", line 1, in ? File "/Users/groves/dev/jython/badmodule.py", line 1, in ? import nonexistentmodule ImportError: No module named nonexistentmodule ---------------------------------------------------------------------- Comment By: Charles Groves (cgroves) Date: 2006-07-12 13:14 Message: Logged In: YES user_id=1174327 The attached patch fixes this problem. It surrounds the actual import code with a try catch, and if an exception is thrown it removes the module from the modules list and rethrows the exception. I think all import code eventually flows through here to actually run the import so I think it fixes everything, but someone with more knowledge of the Jython import system should probably take a look at this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112867&aid=1521362&group_id=12867 |