Stefan Behnel added the comment:

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.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue17741>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to