New submission from Marc Abramowitz <msabr...@gmail.com>:
>From a failing unit test with coverage.py, I noticed what seems to be a slight
>typo in the error message when a module cannot be imported:
diff -r 1186d68715cc Lib/imp.py
--- a/Lib/imp.py Wed Jul 04 19:33:45 2012 -0700
+++ b/Lib/imp.py Thu Jul 05 11:50:25 2012 -0700
@@ -230,7 +230,7 @@
continue
break # Break out of outer loop when breaking out of inner loop.
else:
- raise ImportError('No module name {!r}'.format(name), name=name)
+ raise ImportError('No module named {!r}'.format(name), name=name)
encoding = None
if mode == 'U':
Note the missing "d". This makes it match similar existing error messages:
Lib/importlib/_bootstrap.py
1238:_ERR_MSG = 'No module named {!r}'
Lib/modulefinder.py
185: self.msgout(4, "raise ImportError: No module named", qname)
186: raise ImportError("No module named " + qname)
198: self.msgout(4, "raise ImportError: No module named", mname)
199: raise ImportError("No module named " + mname)
215: raise ImportError("No module named " + subname)
Lib/runpy.py
106: raise ImportError("No module named %s" % mod_name)
I wonder if this can be centralized to ensure that all code uses the exact same
message?
----------
components: Library (Lib)
messages: 164693
nosy: Marc.Abramowitz, brett.cannon
priority: normal
severity: normal
status: open
title: Typo in error message
type: behavior
versions: Python 3.3
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue15256>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
