Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Python 3 port is available #587

Closed
puzzlet opened this Issue Sep 2, 2012 · 22 comments

Comments

Projects
None yet

puzzlet commented Sep 2, 2012

I'm porting Flask (and Werkzeug) to run in Python 3.2:

At this time of writing it passes all the tests, and capable of running simple web applications.

Owner

untitaker commented Sep 2, 2012

That is awesome, but... what now? Do you want to continue it as a parallel project?

Owner

untitaker commented Sep 2, 2012

Kenneth Reitz notifications@github.com wrote:

http://lucumr.pocoo.org/2012/8/27/about-the-lack-of-updates/


Reply to this email directly or view it on GitHub:
mitsuhiko#587 (comment)

@kennethreitz I don't think that does invalidate OP's work.

Contributor

kennethreitz commented Sep 2, 2012

I didn't say anything about invalidation. I'm just pointing it out because it is of interest.

Armin's planning on potentially making sweeping changes to Flask at the same time as adding Python 3 support.

This also coincides with the plans on my front:

http://kennethreitz.com/the-future-of-python-http.html

puzzlet commented Sep 2, 2012

I wanted to port it right away so I can use it, and it actually took me no more than few days. I'm not certain when the new implementation would come out, and whether it will support Python 3. So it doesn't matter.

And about the fork problem: I'm planning to merge future changes in the master branch to the py3 branch. We could use 2to3, but the code will be more complex and obscure if we choose to make it work in both Python 2 and 3. Instead I'm making as small changes to the upstream code as possible.

Owner

mitsuhiko commented Sep 2, 2012

I started a secret branch for experimenting with API changes right before that blog post with the intention of making Werkzeug on Python 3 suck less. But I don't want to push it just yet :)

@mitsuhiko Any updates on this? Are these changes that you don't want help from the community to implement?

@mitsuhiko Also interested in updates! Or at least an idea of the time frame in which this could happen.

Contributor

kennethreitz commented Nov 29, 2012

Earth to @mitsuhiko.

desimone commented Jan 6, 2013

@mitsuhiko joining the chorus. Any updates?

As anybody here, I too would love to read about the progress towards the 3-compatible version of Flask. Not really because I am in need of adopting it, but rather because I would love to read one of @mitsuhiko insightful blog posts on good software design. :)

The more time I spend learning python, the more time I would like to spend learning something forward compatible. Flask is a great project to be sure, but I would really like to see it actively moving toward Py3+. Lest I simply ask with no offer to help, consider this as a statement to help to my ability.

After reading this and other links, I'm still not sure if I can get Flask to run on Python 3 or not. What is the current stance? I don't want to sound like a freeloader (demanding without contributing), but why not publish a port, to allow people to move to Python 3, before moving towards Flask 2.0 or something like that?

(just for the record, I'm going to try the fork pointed above)

apiguy commented Feb 11, 2013

Carlos,

AFAIK, the official stance is that Armin has a Python 3 branch he is
working on. There currently isn't even a Flask 1.0, let alone work being
done on a 2.0.

  • Freedom

On Mon, Feb 11, 2013 at 6:59 AM, Carlos Ribeiro notifications@github.comwrote:

After reading this and other links, I'm still not sure if I can get Flask
to run on Python 3 or not. What is the current stance? I don't want to
sound like a freeloader (demanding without contributing), but why not
publish a port, to allow people to move to Python 3, before moving towards
Flask 2.0 or something like that?


Reply to this email directly or view it on GitHubhttps://github.com/mitsuhiko/flask/issues/587#issuecomment-13377252..

Well, Flask depends on Werkzeug so we'll have to see some progress here (mitsuhiko/werkzeug#212) first. (But that thread is deader than this one.)

Thanks for the reply! It's a shame, I know some folks who have used Flask
recently and swear that's the best thing since sliced bread :-) Having a
Flask 1.0 would be really nice.

On Mon, Feb 11, 2013 at 12:48 PM, Freedom Dumlao
notifications@github.comwrote:

Carlos,

AFAIK, the official stance is that Armin has a Python 3 branch he is
working on. There currently isn't even a Flask 1.0, let alone work being
done on a 2.0.

  • Freedom

On Mon, Feb 11, 2013 at 6:59 AM, Carlos Ribeiro notifications@github.comwrote:

After reading this and other links, I'm still not sure if I can get
Flask
to run on Python 3 or not. What is the current stance? I don't want to
sound like a freeloader (demanding without contributing), but why not
publish a port, to allow people to move to Python 3, before moving
towards
Flask 2.0 or something like that?


Reply to this email directly or view it on GitHub<
https://github.com/mitsuhiko/flask/issues/587#issuecomment-13377252>..


Reply to this email directly or view it on GitHubhttps://github.com/mitsuhiko/flask/issues/587#issuecomment-13382893..

Carlos Ribeiro
Consultoria em Projetos
twitter: http://twitter.com/carribeiro
blog: http://rascunhosrotos.blogspot.com
mail: carribeiro@gmail.com

Yes, and for what I have seem, plans are ambitious (things like redefining
the entire architecture). I used Werkzeug before, in a Django project, and
I really loved it. Hope they get back to work on it. The lack of progress
on the Werkzeug project was what convinced me to look around, I'm probably
going to try Bottle...

On Mon, Feb 11, 2013 at 1:09 PM, Timothy Farrell
notifications@github.comwrote:

Well, Flask depends on Werkzeug so we'll have to see some progress here (
mitsuhiko/werkzeug#212 mitsuhiko/werkzeug#212)
first. (But that thread is deader than this one.)


Reply to this email directly or view it on GitHubhttps://github.com/mitsuhiko/flask/issues/587#issuecomment-13383929..

Carlos Ribeiro
Consultoria em Projetos
twitter: http://twitter.com/carribeiro
blog: http://rascunhosrotos.blogspot.com
mail: carribeiro@gmail.com

Any New Update on Python 3 support for the Flask please

Owner

untitaker commented Apr 28, 2013

I'm kinda tired of posting this everywhere, but here goes: https://gist.github.com/untitaker/5321447

(document that summarizes and tracks the current status on Werkzeug being ported)

...and just to keep the thread update and spread the news about the progress...
https://github.com/mitsuhiko/pocoo-sprint-18052013

Owner

untitaker commented May 24, 2013

I'd also like to add that the port Werkzeug is now in a somewhat stable state.

The urls module of Werkzeug has to be rewritten and merged with some other code forked from the stdlib (urlparse), but i don't think the current implementation hinders the Flask port for now. There's some work left for Flask itself too. IIRC especially flask.json was mentioned by @mitsuhiko because of the difference in behavior of json in Py2, json in Py3, and simplejson.

You can help us by testing experimental versions of Flask and Werkzeug from the following branches:

Flask's port: https://github.com/mitsuhiko/flask/tree/sprint-branch
Werkzeug's port: https://github.com/mitsuhiko/werkzeug/tree/sprint-branch

These should work for simple apps, but i'd love to know if they work for more complex ones too.

Contributor

DasIch commented Jun 19, 2013

Flask supports 3.3 now.

@DasIch DasIch closed this Jun 19, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment