Nick Maclaren wrote: > Currently logins are disabled to sourceforge.net, and (despite the > comments) it won't let me report a bug anonymously. Does anyone > know whether this is short or long term? I have a bug in 2.5 to > report - which has been there for a while and isn't overwhelmingly > critical and has been there for a while. > > Create a file called '<stdin>' in your current directory containing > 'print "Oh, yeah?\n"' and then import a module that doesn't exist. > Don't include the single quotes.
You should have said what the bug is. To save others reproducing this: you get a traceback akin to $ python Python 2.4.3 (#1, May 8 2006, 18:29:03) [GCC 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import xyzzy Traceback (most recent call last): File "<stdin>", line 1, in ? print "Oh, yeah?\n" ImportError: No module named xyzzy >>> The problem is that Python does not know whether a file name is bogus or an actual file. So it was assumed that names like "<stdin>" or "<string>" are safe enough to use them as subsitutes. I don't know whether this is worth fixing. Geor -- http://mail.python.org/mailman/listinfo/python-list