➜

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 meador.inge
Recipients Robert.Elsner, jcea, mark.dickinson, meador.inge, pitrou, r.david.murray, serhiy.storchaka
Date 2013-05-14.20:35:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368563719.92.0.141992716312.issue14596@psf.upfronthosting.co.za>
In-reply-to
Content 
> 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.

No, I am not sure.  That is why I said that I understand if others felt
this bug was critical to fix now since the PEP 3118 changes were dragging
on.  In that case I will just rework my patch.

I am not trying to stand in the way of this patch.  I just wanted folks
to be aware that this approach was implemented in the PEP 3118 work.
History
Date User Action Args
2013-05-14 20:35:19meador.ingesetrecipients: + meador.inge, jcea, mark.dickinson, pitrou, r.david.murray, serhiy.storchaka, Robert.Elsner
2013-05-14 20:35:19meador.ingesetmessageid: <1368563719.92.0.141992716312.issue14596@psf.upfronthosting.co.za>
2013-05-14 20:35:19meador.ingelinkissue14596 messages
2013-05-14 20:35:19meador.ingecreate