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 ncoghlan
Recipients Mariatta, ncoghlan, serhiy.storchaka, syncosmic
Date 2017-08-12.15:18:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1502551094.87.0.0208923026659.issue31183@psf.upfronthosting.co.za>
In-reply-to
Content
While I agree the line is blurry, extending automatic disassembly to cover new types is currently still considered a new feature in the dis module rather than a bug in the addition of those new types to the language.

Whether or not that's the *right* policy, or if we should consider tweaking it so that oversights in `dis` and `inspect` are treated as bugs in the addition of affected types, would be a question for python-dev (fortunately, the new cherry-pick based workflow means the current PR review can proceed independently of that question).
History
Date User Action Args
2017-08-12 15:18:14ncoghlansetrecipients: + ncoghlan, serhiy.storchaka, Mariatta, syncosmic
2017-08-12 15:18:14ncoghlansetmessageid: <1502551094.87.0.0208923026659.issue31183@psf.upfronthosting.co.za>
2017-08-12 15:18:14ncoghlanlinkissue31183 messages
2017-08-12 15:18:14ncoghlancreate