2009/11/3 Raymond Hettinger <pyt...@rcn.com>: > In all these matters, I think the users should get a vote. And that vote > should be cast with their decision to stay with 2.x, or switch to 3.x, or > try to support both. We should not muck with their rational decision making > by putting "carrots" in one pile and abandoning the other.
Agreed (up to a point). The biggest issue to my mind is that adoption by the ultimate end users is significantly hampered by the fact that big projects like Twisted, numpy and the like, have no current plans to move to Python 3. Even end users with a reasonable level of coding expertise don't have the time or resources to offer much in the way of help with a port, when the project as a whole isn't interested in starting the process. At the moment, it seems to me that this is the biggest blocker to Python 3 adoption. And it's a chicken and egg situation - I don't use Python 3, so I don't test the new features, so the projects I need see little take-up, so I can't use them in Python 3, so I don't use Python 3... And while I know I can run Python 2.x and Python 3.x side by side, at the end of the day, I want to just be able to type "python" to get my interpreter. I don't know how to solve this (assuming that "just wait" isn't going to do it). Maybe the core devs will have to offer resource to some of the key projects to get things moving (but as this is a volunteer effort, that isn't something that "just happens" either...) Paul. _______________________________________________ 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/archive%40mail-archive.com