On 7 Jan 2014 18:18, "Donald Stufft" <donald@stufft.io> wrote:
Given the low adoption rates for Python 3 it would not surprise me if
people
who are hampered by the lack of this change are willing to wait until a Python version is released that has it.
Once the code exists (regardless of the exact spelling), it also becomes much easier to extract as an extension module on PyPI for wire protocol formatting. That would allow folks to choose between just supporting 3.5+ and using the builtin formatting operations, or switching to the cross version compatible formatting module (if one was created). So I like the idea of restoring this capability for 3.5, but don't see a reason to consider rushing it into 3.4. Cheers, Nick.
On Jan 7, 2014, at 5:13 AM, Victor Stinner <victor.stinner@gmail.com>
wrote:
2014/1/7 Paul Moore <p.f.moore@gmail.com>:
Will the relevant projects actually support only 2.X and 3.4/5+? If they expect to or have to support 3.2 or 3.3, then this change isn't actually going to help them much. If they will only support versions of Python 3 containing this change, then it may well be worth considering the impact of delaying it till 3.5.
Twisted and Mercurial don't support Python 3.
(I heard that Twisted Core supports Python 3, but I don't know if it's true nor the Python 3 version.)
Victor _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe:
https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372
DCFA
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe:
https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com