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 wolma
Recipients mark.dickinson, rhettinger, serhiy.storchaka, tim.peters, wolma
Date 2018-03-28.14:57:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1522249063.63.0.467229070634.issue33144@psf.upfronthosting.co.za>
In-reply-to
Content
So, the PR implements the behaviour suggested by Serhiy as his cases 1 and 2.
Case 2 changes *existing* behaviour because before it was sufficient to have a user-defined getrandbits anywhere in the inheritance tree, while with the PR it has to be more recent (or be defined within the same class) as the random method.
I'm not 100% sold on this particular aspect so if you think the old behaviour is better, then that's fine with me. In most real situations it would not make a difference anyway (or do people build complex inheritance hierarchies on top of random.Random?).
History
Date User Action Args
2018-03-28 14:57:43wolmasetrecipients: + wolma, tim.peters, rhettinger, mark.dickinson, serhiy.storchaka
2018-03-28 14:57:43wolmasetmessageid: <1522249063.63.0.467229070634.issue33144@psf.upfronthosting.co.za>
2018-03-28 14:57:43wolmalinkissue33144 messages
2018-03-28 14:57:43wolmacreate