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 scoder
Recipients eli.bendersky, flox, jcea, pitrou, python-dev, scoder
Date 2013-08-23.21:20:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377292817.74.0.726429806158.issue17741@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think I understand what you mean.

In any case, it's not to late to remove the implementation. There was only one alpha release so far that included it, so it can't really break any existing code that relies on it. The longer we wait, the more damage will be done. That's why I am asking for removal now.

I would prefer not to rush in a replacement. The current state shows where that brings us. So, I request the removal of the current code, then we can calmly come up with a good implementation of the feature in question. If that can't be done for 3.4, well, then we have at least avoided adding something that will need to be deprecated and replaced later on. If it can be done for 3.4, the better.
History
Date User Action Args
2013-08-23 21:20:17scodersetrecipients: + scoder, jcea, pitrou, eli.bendersky, flox, python-dev
2013-08-23 21:20:17scodersetmessageid: <1377292817.74.0.726429806158.issue17741@psf.upfronthosting.co.za>
2013-08-23 21:20:17scoderlinkissue17741 messages
2013-08-23 21:20:17scodercreate