➜

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 _doublep
Recipients _doublep, amaury.forgeotdarc, arigo, georg.brandl
Date 2008-01-21.20:53:31
SpamBayes Score 0.11835767
Marked as misclassified No
Message-id <1200948813.56.0.0527175620509.issue1878@psf.upfronthosting.co.za>
In-reply-to
Content 
I personally think that this bug is a showstopper for the caching patch
in 2.6.  Well, the problem can be deemed insignificant, but it is sure a
break of backward compatibility and, worse yet, it results in _very_
obscure fails.  Even if type dictionary changes are not all that common,
I'm sure there are extensions out there that do it.

For Py3k things can be different.  I'm not sure what would be the best
way, but at least Py3k is not required to be compatible with 2.x in all
aspects.
History
Date User Action Args
2008-01-21 20:53:33_doublepsetspambayes_score: 0.118358 -> 0.11835767
recipients: + _doublep, arigo, georg.brandl, amaury.forgeotdarc
2008-01-21 20:53:33_doublepsetspambayes_score: 0.118358 -> 0.118358
messageid: <1200948813.56.0.0527175620509.issue1878@psf.upfronthosting.co.za>
2008-01-21 20:53:31_doubleplinkissue1878 messages
2008-01-21 20:53:31_doublepcreate