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.

Author brett.cannon
Recipients Olivier.Grisel, brett.cannon, eric.snow, ncoghlan, pitrou, sbt
Date 2013-12-10.20:27:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1386707252.97.0.998240004224.issue19946@psf.upfronthosting.co.za>
In-reply-to
Content
So at the bare minimum, the multiprocessing code should raise an ImportError when it can't find the spec for the module to help debug this kind of thing. Also that typo should get fixed.

Second, there is no way that 'nosetests' will ever succeed as an import since, as Oliver pointed out, it doesn't end in '.py' or any other identifiable way for a finder to know it can handle the file. So this is not a bug and simply a side-effect of how import works. The only way around it would be to symlink nosetests to nosetests.py or to somehow pre-emptively set up 'nosetests' for supported importing.
History
Date User Action Args
2013-12-10 20:27:33brett.cannonsetrecipients: + brett.cannon, ncoghlan, pitrou, sbt, eric.snow, Olivier.Grisel
2013-12-10 20:27:32brett.cannonsetmessageid: <1386707252.97.0.998240004224.issue19946@psf.upfronthosting.co.za>
2013-12-10 20:27:32brett.cannonlinkissue19946 messages
2013-12-10 20:27:32brett.cannoncreate