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 chrish42
Recipients Arfrever, arigo, barry, chrish42, eric.snow, eryksun, larry, ncoghlan, ozialien, pitrou, r.david.murray, rhettinger
Date 2015-04-14.14:27:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
As a newbie to the CPython source code (and as someone who started working on this bug because it was on the lists of easy bugs for PyCon 2014), I don't have a strong attachment either way, as long as some kind of decision is reached, and I can check this off my list.

If forced to take a stance, I would probably agree that this might be reaching into "foolish consistency" territory, as I just don't see myself ever using the new possibilities that this added code would allow.

If the decision is made to fix this, I'll improve the tests to actually call these new callables (and check that the result of the call is correct). I'll wait until the "we should fix this" decision is made to work on the patch again, though. But if this is closed as not-a-bug, I'll be a happy camper too (as I've learned some stuff about CPython internals in the process).
Date User Action Args
2015-04-14 14:27:13chrish42setrecipients: + chrish42, barry, arigo, rhettinger, ncoghlan, pitrou, larry, Arfrever, r.david.murray, eric.snow, eryksun, ozialien
2015-04-14 14:27:13chrish42setmessageid: <>
2015-04-14 14:27:13chrish42linkissue20309 messages
2015-04-14 14:27:13chrish42create