9 ms·
> I really hoped Armin would come around, and I committed to Werkzeug for a new project with eyes on 3. All commits to Werkzeug are currently happening with a
by the_mitsuhiko 16y ago
> I really hoped Armin would come around, and I committed to Werkzeug for a new project with eyes on 3.
All commits to Werkzeug are currently happening with a port to Python 3 in mind. However I am not going to do the same mistake the standard library made in many parts and change the semantics of the library for Python 3 and trusting 2to3 to do the correct thing.
A full port of Werkzeug to Python 3 will take time but it will happen eventually. The point here is that everybody should go with Python 2.7 and write the code forwards compatible. Then you have all the options (of going with PyPy if you need and upgrading to Python 3 if it's worth the effort).
All I can say right now is that so far users are not too eager with Python 3 yet and I have limited resources as well. If anyone wants to help out, I am more than happy to assist in any way possible to make Werkzeug run on Python 3. I also monitor changes in the stdlib that could affect WSGI on Python 3, so it's not that I'm ignoring it.
Python is not on the way to suicide. All I said was that right now you shouldn't be too concerned with Python 3 yet and instead make your own code upwards compatible. If your base Python version is 2.7 upgrading will not be the biggest problem, especially not if you are working on a high level like you do when you use a web framework.
- jedsmith 16y ago> I have limited resources as well I'd like to make clear that I wasn't bitching, because I know exactly how the limited resources dance goes. Disappointment with further confusion between Python 2 and 3, yes; disappointment with you, no (are you kidding? half my stack is Pocoo stuff). > All I said was that right now you shouldn't be too concerned with Python 3 yet The real question is when "yet" will be. Python 3's been out two years, and I don't think I'm alone in the community in wondering if it'll ever be completely figured out. The fact that PEP 3333 was just accepted is a testament to the slow nature of the thing. It's getting tiring to want to use 3 but instead having to stick with 2to3. Even that is a distant goal: when will I be able to finally run 2to3 and move entirely to 3? If I'm entrenched in a lot of Python 2 libraries, I'm beginning to believe (two years later) that the big day will never come. Python 3 is great. I want to use it. It's fights like Web3 vs. WSGI and the resistance to (or impossibility of) porting the libraries I use that are personally keeping me away from it. I think that speaks for the lack of eagerness to move to 3 that you've observed. It's very real, and entirely, I think, due to libraries. I'll be at PyCon as well on behalf of my employer, and I'm interested (as it sounds like you are, from your blog post) to hear what the consensus is on Python's future. Right now, I have a lot of questions, and nobody seems to have answers.
- jnoller 16y agoWe have had answers for the past two years: Python 3 adoption will be measured in terms of years and will only come as third party modules (such as Numpy, Scipy, and many others) slowly make the port. No one has ever claimed it to be publicly ready for product, but more and more libraries are porting every single day - forward progress is being made, but like all change in the community, it takes time. I'm a core developer: and even I stick to python 2 right now because of my dependencies. I know full well that me being able to run Python 3 in production is at least another year, to two years off.
- jedsmith 16y agoThat's what I've been told for the last two years -- it'll come, give it time, etc. Then the developer of a library I use announces that a port to Python 3 is unlikely two years after Python 3 is released, and I'm left with even more questions. I'm curious since you continue to advise patience how you'd react in my position. I've been patient, and now my library of choice for WSGI coming to Python 3 is, quote, "unlikely". What now? Why should I bother caring about 3, if an influential voice in the Python community doesn't? Armin makes excellent points in his post, to be frank. The fault line is widening, honestly, because of the lack of forward momentum. Your estimate of Python 3 in production being a year to two years off sounds like it come completely out of thin air, as I'm starting to wonder if it will ever happen.
- cookiecaper 16y agoMost Python libraries are considering and/or starting a port now. Py3 is just now starting to be taken seriously, which is fine by me; we don't need to rush to use the "latest cool thing" as long as we get there eventually. It's good for Py3 to be tested and developed without being flooded for its initial lifecycle, which is what happens here. Note that this attitude has mostly been guided by the Python Foundation in the first place. Until a few months ago, Python 2 was still actively developed. It has entered maintenance mode with 2.7; all future features or enhancements now go to Py3. Again, please note that 2.7 was released only about six months ago. Since then, libraries, distributions, and other major players that push normal users to adopt new stuff have been moving to Python 3. As popular low-level libraries make the move higher-level stuff will begin to consider it too; Django's reason for not porting to Python 3 is basically "none of our dependencies run there yet". This post actually demonstrates the strength of Python 3; while the author doesn't feel that this library specifically is a good candidate for a port, he is thinking about it, and he recommends that users still prepare for the transition. He says, in effect, "write code so that 2to3 can handle it easily when the moment comes", not "give up on Python 3 entirely".