Werkzeug in general, but in Python 3.1
I am very keen on ** ** you can create web applications using Python. For reference, we are using RHEL 64bit, apache, mod_wsgi.
History:
- PHP + MySQL years ago
- PHP + Python 2.x + MySQL recently and current
- Python + PostgreSQL is working on it
We are using an excellent library to exchange information between PHP and Python (frontend in PHP, backend in Python) ... However, when starting a larger upcoming project, using 100% python can be very beneficial.
We usually prefer not to have a monolithic structure dictating how things are done. A set of useful helpers and utilities (be it PHP or Python) is very useful.
Question 1:
While reading several answers from experienced Python users, I've seen Werkzeug several times . I would be very pleased if several people with direct experience of using Werkzeug to develop professional web applications could comment (as detailed as their fingers) why they use it, why they like it, and something what you need to consider.
Question 2:
Is there a version of Werkzeug that supports Python 3.1.1. I have successfully installed mod_wsgi on Apache 2.2 using Python 3.1.1.
If there is no version available, what will it take to update it to work with Python 3.1?
Note. I ran 2to3
Werkzeug in source code and it does python compilation without
Edit:
The project we are launching is not planned to be completed until almost a year. At this point, I am guessing that Python 3.X will be much more popular. Also, given that we are running the app (without distributing it), can anyone comment on the viability of beating through some Python 3 issues, so that when a year later we are more or less
Thoughts appreciated!
source to share
mod_wsgi for Python 3.x is also not ready. There is still no satisfactory definition of WSGI for Python 3.x; WEB-SIG are still troubleshooting issues. mod_wsgi is targeting what might be in it, but there will likely be changes to both the spec and the standard libraries. Any web application you write in Python 3.1 today is likely to break in the future.
It's crumbling a little. Today for webapps you can actually use Python 2.x.
source to share
I haven't used Werkzeug, so I can only answer question 2:
No, Werkzeug does not work in Python 3. In fact, there is very little work in Python 3 to date. Porting isn't difficult, but you can't port until all your third party libraries have been ported, so progress is slow.
One big cork was setuptools, which is a very popular package to use. Setuptools is not supported, but there is a supported fork called Distribute. The distribution was released with Python 3 support just a week or two ago. Hopefully Python 3 batch support goes up now. But it will be a long time, at least months, probably a year or so, before any major project like Werkzeug gets ported to Python 3.
source to share
I can only answer one question:
I started using it for a small website, but have now moved on to rework large applications with it. Why Werkzeug? The modular concept is really useful. You can plug in modules as you want, customize the context easily, and you get free request file processing that can handle 300mb + files without storing them in memory.
Disadvantages ... Well, sometimes modularity requires some prior thought (django f.ex. gives you everything at once, clean up stuff, hard to do there), but it works great for me.
source to share