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 Rob Bairos
Recipients Rob Bairos, brett.cannon, eric.araujo, eric.smith, ncoghlan
Date 2011-11-03.21:36:32
SpamBayes Score 7.69441e-07
Marked as misclassified No
Message-id <1320356192.97.0.43889339662.issue13314@psf.upfronthosting.co.za>
In-reply-to
Content
Why is a module name syntactically improper simply because it contains a slash?  That seems an arbitrary definition, that serves no purpose, except to discourage accidentally specifying a filename.

Module with unusual characters all reach the meta_path stage,
eg:  my,mo*d1?2my##m;o#d13

But as soon as a slash is introduced, a warning that filenames not being supported is thrown.

1) If the issue is that its not syntactically correct, it should state so.
2) If the issue is that its not syntactically correct, the syntax of a module name should be documented to include *,?#  or throw the same exception.
3) Whats the purpose of the 'Import my filename' exception anyhow? Will it not fail soon thereafter at any rate?

This behaviour is definitely inconsistent and arbitrary.
History
Date User Action Args
2011-11-03 21:36:33Rob Bairossetrecipients: + Rob Bairos, brett.cannon, ncoghlan, eric.smith, eric.araujo
2011-11-03 21:36:32Rob Bairossetmessageid: <1320356192.97.0.43889339662.issue13314@psf.upfronthosting.co.za>
2011-11-03 21:36:32Rob Bairoslinkissue13314 messages
2011-11-03 21:36:32Rob Bairoscreate