On Tue, Apr 29, 2008 at 5:18 PM, Benjamin Peterson <[EMAIL PROTECTED]> wrote: .. > > Put another way: range(n) currently works, in Py3k, for n > sys.maxsize. > > What's the rationale for breaking that? > > So we can support other sequence methods. (I think.) > This is not true. The missing sequence methods are slicing and __contains__ and neither requires len <= sys.maxsize . The rationale was that a huge range is most likely a programming or input error which is detected early in 2.x while in 3.x may result in strange errors later on. _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
- Re: [Python-3000] range() issues Guido van Rossum
- Re: [Python-3000] range() issues Greg Ewing
- Re: [Python-3000] range() issues Guido van Rossum
- Re: [Python-3000] range() issues Benjamin Peterson
- Re: [Python-3000] range() issues Guido van Rossum
- Re: [Python-3000] range() issues Benjamin Peterson
- Re: [Python-3000] range() issues Guido van Rossum
- Re: [Python-3000] range() issues Nick Coghlan
- Re: [Python-3000] range() issues Guido van Rossum
- Re: [Python-3000] range() issues Facundo Batista
- Re: [Python-3000] range() issues Alexander Belopolsky
- Re: [Python-3000] range() issues Martin v. Löwis
- Re: [Python-3000] range() issues Richard Boulton
- Re: [Python-3000] range() issues Martin v. Löwis
- Re: [Python-3000] range() issues Nick Coghlan
- Re: [Python-3000] range() issues Mark Dickinson
- Re: [Python-3000] range() issues Martin v. Löwis
- Re: [Python-3000] range() issues Terry Reedy