This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Give some clue why modules fail...
Type: Stage:
Components: Build Versions: Python 2.2
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: mwh Nosy List: benl, mwh
Priority: normal Keywords: patch

Created on 2002-11-28 18:52 by benl, last changed 2022-04-10 16:05 by admin. This issue is now closed.

Messages (4)
msg41828 - (view) Author: Ben Laurie (benl) Date: 2002-11-28 18:52
--- Python-2.2.2/       Thu Oct 10 00:59:16 2002
+++ Python-2.2.2-ben/   Thu Nov 28 17:45:51 2002
@@ -163,9 +163,9 @@
-        except ImportError:
-            self.announce('WARNING: removing "%s"
since importing it failed' %
+        except ImportError, e:
+            self.announce('WARNING: removing "%s"
since importing it failed: %s' %
+                          (,str(e)))
             assert not self.inplace
             fullname = self.get_ext_fullname(
             ext_filename = os.path.join(self.build_lib,
msg41829 - (view) Author: Michael Hudson (mwh) (Python committer) Date: 2002-11-29 11:45
Logged In: YES 

1) please don't paste patches into the textarea!
2) would you be happier if we adopted the 2.3 solution of
just renaming the failed module rather than deleting it? 
I've been thinking for a while that that would be worthwhile.
msg41830 - (view) Author: Ben Laurie (benl) Date: 2002-11-30 21:21
Logged In: YES 

1) Sorry, attaching a file for a small patch wasn't the
obvious thing to do...

2) The issue isn't the disposal of the module after its
failed, its that you get no clue as to why its failed...
msg41831 - (view) Author: Michael Hudson (mwh) (Python committer) Date: 2002-12-06 15:33
Logged In: YES 

This should be fixed in revision of
Date User Action Args
2022-04-10 16:05:57adminsetgithub: 37548
2002-11-28 18:52:37benlcreate