With 1.5 years per release, it'd be 10 years before we'd hit 3.10.
From a software engineering perspective, 10 years is indistinguishable from infinity, so I don't care what happens 10 years from now -- as long as you don't blame me. :-)
On Tue, Feb 26, 2013 at 11:21 AM, Brett Cannon <brett@python.org> wrote:
On Tue, Feb 26, 2013 at 2:12 PM, Guido van Rossum <guido@python.org> wrote:
Generally speaking, deferring something to Python 4 means "never".
Does that mean your aversion to double digit version numbers (i.e. 3.10) is gone or you expect to freeze Python in carbonite by then?
-Brett
On Tue, Feb 26, 2013 at 11:06 AM, R. David Murray <rdmurray@bitdance.com> wrote:
On Tue, 26 Feb 2013 18:14:26 +0000, Paul Moore <p.f.moore@gmail.com> wrote:
BTW, I assume that the intention is that both cffi and ctypes remain available indefinitely? Nobody's looking to deprecate ctypes?
I would expect that ctypes would be deprecated eventually simply because there aren't very many people interested in maintaining it, and probably fewer if cffi is accepted. That said, I would not expect it to leave the stdlib until either the bit rot was so bad it wouldn't be worth shipping it, or (more likely) we reach Python4 and decide at that time that it is time for it to go.
Of course, this is just me talking, we only have a *very* vague "sense of the house" for what Python4 means at this point :)
--David _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org
-- --Guido van Rossum (python.org/~guido) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/brett%40python.org
-- --Guido van Rossum (python.org/~guido)