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 Todd Dembrey, belopolsky, berker.peksag, jleedev, matrixise, ncoghlan, pitrou, rhettinger, serhiy.storchaka, torsten, vstinner
Date 2017-04-16.21:22:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1492377726.86.0.0633227267039.issue11822@psf.upfronthosting.co.za>
In-reply-to
Content
> if we modify dis() instead of adding a new function, then
> the default behaviour needs to be non-recursive for 
> backwards compatibility reasons

I don't see how we have any backward compatibility issues.  The dis() function is purely informational like help().  

The problem is it doesn't show important information, list comprehensions are now effectively hidden from everyone who isn't clever and persistent.   

I use dis() as a teaching aid in my Python courses and as a debugging tool when doing consulting.  From my point of view, it is effectively broken in Python 3.
History
Date User Action Args
2017-04-16 21:22:06rhettingersetrecipients: + rhettinger, ncoghlan, belopolsky, pitrou, vstinner, torsten, berker.peksag, serhiy.storchaka, jleedev, matrixise, Todd Dembrey
2017-04-16 21:22:06rhettingersetmessageid: <1492377726.86.0.0633227267039.issue11822@psf.upfronthosting.co.za>
2017-04-16 21:22:06rhettingerlinkissue11822 messages
2017-04-16 21:22:06rhettingercreate