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 isandler
Recipients
Date 2005-03-26.05:06:57
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=971153

Seems like the main motivation for the original patch was to
prevent accidental conflicts between user's and standard
module names

Would emitting a warning (with an easy way to explicitly
suppress it) in such a case solve the original problem?

I am not sure whether such a warning should be limited to
user/system name conflicts or to any module name conflicts?
History
Date User Action Args
2007-08-23 15:37:36adminlinkissue946373 messages
2007-08-23 15:37:36admincreate