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 pitrou
Recipients Robert.Elsner, jcea, mark.dickinson, meador.inge, pitrou, r.david.murray, serhiy.storchaka
Date 2013-05-14.17:07:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368551263.2562.5.camel@fsol>
In-reply-to <1368549474.61.0.0332511924747.issue14596@psf.upfronthosting.co.za>
Content
Le mardi 14 mai 2013 à 16:37 +0000, Meador Inge a écrit :
> If we feel that this optimization is really critical, then I agree
> let's not hold it up and I will just work around it with my patch for
> issue3132.  I don't see it as that critical, but I understand that the
> PEP 3118 changes are dragging on and this optimization might be important
> for some now.

Are you sure the PEP 3118 changes will land in 3.4? It would be a pity
to lose a simple improvement because it was deferred to a bigger change.
History
Date User Action Args
2013-05-14 17:07:45pitrousetrecipients: + pitrou, jcea, mark.dickinson, r.david.murray, meador.inge, serhiy.storchaka, Robert.Elsner
2013-05-14 17:07:45pitroulinkissue14596 messages
2013-05-14 17:07:45pitroucreate