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 dwt, eric.snow, ezio.melotti, mrabarnett, pitrou, rhettinger, terry.reedy
Date 2011-12-22.21:44:28
SpamBayes Score 4.92966e-05
Marked as misclassified No
Message-id <>
"I don't see how eval()able repr is a big deal. Most reprs aren't, ..."

Sometimes, I wonder if we're even talking about the same programming language.  Historically, a good deal of effort has gone into creating evalable reprs, if only because they accurately describe an object and because they teach users how to create similar objects.  

But it only takes one committer who doesn't care about evalable reprs to permanently break the pattern for everyone :-(
Date User Action Args
2011-12-22 21:44:29rhettingersetrecipients: + rhettinger, terry.reedy, pitrou, ezio.melotti, mrabarnett, eric.snow, dwt
2011-12-22 21:44:28rhettingersetmessageid: <>
2011-12-22 21:44:28rhettingerlinkissue13592 messages
2011-12-22 21:44:28rhettingercreate