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 MLModel
Recipients MLModel, georg.brandl
Date 2009-05-07.03:19:22
SpamBayes Score 2.0417017e-06
Marked as misclassified No
Message-id <1241666364.76.0.940055680817.issue5953@psf.upfronthosting.co.za>
In-reply-to
Content
I just discovered to my (deep) surprise that
        range(n) != range(n)
I think that's worth including in the what's new document.
I realize that the document essentially says that in python 3 range
behaves the way xrange did in python 2 and that ranges have very little
behavior, but surely the lack of equality of two ranges whose string
representations are equal is enough of a surprise and difference from
python 2 to be worth an explicit comment. (Or maybe no-one ever compares
ranges? They are just for iteration? Even that should be said
explicitly. This is one of those things that I'm sure expert developers
look at and think is obvious but might trip up ordinary users.)
History
Date User Action Args
2009-05-07 03:19:25MLModelsetrecipients: + MLModel, georg.brandl
2009-05-07 03:19:24MLModelsetmessageid: <1241666364.76.0.940055680817.issue5953@psf.upfronthosting.co.za>
2009-05-07 03:19:23MLModellinkissue5953 messages
2009-05-07 03:19:22MLModelcreate