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 georg.brandl, r.david.murray, rhettinger, skip.montanaro, swamiyeswanth, takayuki
Date 2011-02-13.23:41:53
SpamBayes Score 0.00013093623
Marked as misclassified No
Message-id <1297640514.25.0.145998269475.issue11205@psf.upfronthosting.co.za>
In-reply-to
Content
How much to change and how far to backport may make for a good python-dev discussion.  

ISTM that changing generated code goes hand-in-hand with changing opcode semantics (as long as the magic number gets bumped).  OTOH, none of this may be worth backporting at all since no one seems to have noticed or cared for eight years.   

I don't have any feelings about it one way or the other, but it would great to see Py3.2.1 get fixed properly.
History
Date User Action Args
2011-02-13 23:41:54rhettingersetrecipients: + rhettinger, skip.montanaro, georg.brandl, r.david.murray, swamiyeswanth, takayuki
2011-02-13 23:41:54rhettingersetmessageid: <1297640514.25.0.145998269475.issue11205@psf.upfronthosting.co.za>
2011-02-13 23:41:53rhettingerlinkissue11205 messages
2011-02-13 23:41:53rhettingercreate