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 rhettinger
Recipients Steven.Barker, ideasman42, mark.dickinson, paul.moore, rhettinger, serhiy.storchaka, steve.dower, tim.golden, tim.peters, zach.ware
Date 2016-06-06.00:17:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465172265.53.0.438122412332.issue27072@psf.upfronthosting.co.za>
In-reply-to
Content
Sorry Steven, I'm going to mark this as rejected on the grounds that it is likely to do more harm than good.  We could in fact make the range larger but it easily creates terrible effects (encouraging bad design and creating a non-interruptable, long-running, total-memory-filling call).  

While we do allow ``2 ** 50 ** 50``, that call is more deliberately asking for trouble than getrandbits(2**60).  If someone really needed that number of bits, it isn't hard to multiple calls to getrandbits() and combine the results, deliberately and interruptably.
History
Date User Action Args
2016-06-06 00:17:45rhettingersetrecipients: + rhettinger, tim.peters, paul.moore, mark.dickinson, tim.golden, ideasman42, zach.ware, serhiy.storchaka, steve.dower, Steven.Barker
2016-06-06 00:17:45rhettingersetmessageid: <1465172265.53.0.438122412332.issue27072@psf.upfronthosting.co.za>
2016-06-06 00:17:45rhettingerlinkissue27072 messages
2016-06-06 00:17:44rhettingercreate