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 arigo
Recipients
Date 2004-11-10.21:31:15
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=4771

This indicate that similar breakage will probably occur in user code if we add range checking.  Do we want to take the risk?  It looks overkill, but what about issuing a warning and turning it into an error in the next version?
History
Date User Action Args
2007-08-23 15:40:01adminlinkissue1038854 messages
2007-08-23 15:40:01admincreate