[Python-Dev] On porting to Python 3 as the answer (original) (raw)
Guido van Rossum guido at python.org
Sun Mar 23 18:45:27 CET 2014
- Previous message: [Python-Dev] On porting to Python 3 as the answer
- Next message: [Python-Dev] On porting to Python 3 as the answer
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, Mar 23, 2014 at 9:33 AM, "Martin v. Löwis" <martin at v.loewis.de>wrote:
Am 23.03.14 17:22, schrieb Guido van Rossum: > At Dropbox I work with a large group of very capable developers on > several large code bases that are currently in 2.7. We are constantly > changing our code to make it more secure (there are several teams > specifically in charge of that). And yet porting to Python 3 is > completely out of scope, for a variety of reasons. > > Please stop your wishful thinking.
I can stop expressing it; I don't think I can stop wishing it :-) If it's really unrealistic that Dropbox will ever port the code to Python 3, would you then think that Python 3 is a doomed project, since it won't ever see significant usage?
No, it's just that the timescale is drastically different.
-- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140323/03d2cce6/attachment.html>
- Previous message: [Python-Dev] On porting to Python 3 as the answer
- Next message: [Python-Dev] On porting to Python 3 as the answer
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]