Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update information about Python 3 #1264

Merged
merged 4 commits into from Dec 4, 2014
Merged

Update information about Python 3 #1264

merged 4 commits into from Dec 4, 2014

Conversation

svenstaro
Copy link
Contributor

Python 3 and Flask is a good combination nowadays that works rather well. In fact, most PyPI libs are now ported and it's generally ok to encourage people to use Python 3 for new projects.

Python 3 and Flask is a good combination nowadays that works rather well. In fact, [most PyPI libs](https://regebro.wordpress.com/2014/10/23/59-of-maintained-packages-support-python-3/) are now ported and it's generally ok to encourage people to use Python 3 for new projects.
@DasIch
Copy link
Contributor

DasIch commented Dec 2, 2014

-1

While availability of Python 3 libraries has improved, the market share remains small.

Python 2 will further be supported until at least 2020 and has recently even gained pip. The advantages of Python 3- in so far as they exist -are almost nonexistent. The conservative choice therefore remains Python 2, for the foreseeable future.

I doubt that will change within the next 4 years.

@svenstaro
Copy link
Contributor Author

The information is still outdated, though. Most extensions are compatible. Also, my current suggestion does take into account what you said. "Unless you require absolute compatibility, you should be fine with Python 3" which implies Python 2 is a valid choice still if you need absolute compatibility. We've been using Python 3 for our new app and indeed, it's almost without problems.

I just feel the current page is way too pessimistic about Python 3 (as we all know mitsuhiko's personal stance towards Python 3). Python 3 is the way forward and we should encourage people to use it. At the very least, the information on the page should be updated.

@untitaker
Copy link
Contributor

Using Flask or Werkzeug with Python 3 is absolutely not a stable affair. There are around 20 Python 3-related bugfixes in Werkzeug's master, and I don't think the majority Python 3 ports of any software currently are. I agree the ecosystem did catch up though, and the text on that page is outdated and way too pessimistic (which represents Armin's opinions very well!).

@svenstaro
Copy link
Contributor Author

@untitaker What would you have me change in order to merge this pull request?

@untitaker
Copy link
Contributor

@svenstaro I think we can say at this point that Python 3 is already a sensible choice (regarding completeness of the ecosystem), but the user might run into encoding-related bugs when using it.

@svenstaro
Copy link
Contributor Author

How's that?

@@ -30,30 +30,15 @@ details as it was written before WSGI was updated to Python 3. While the
API for Werkzeug and Flask on Python 2.x should not change much we cannot

This comment was marked as off-topic.

@untitaker
Copy link
Contributor

@DasIch Any opinion on this now? We discussed this in IRC a bit and I like the current phrasing.

@untitaker untitaker added this to the 1.0 milestone Dec 2, 2014
@DasIch
Copy link
Contributor

DasIch commented Dec 4, 2014

Agreed, this is better.

untitaker added a commit that referenced this pull request Dec 4, 2014
Update information about Python 3
@untitaker untitaker merged commit 86525d9 into pallets:master Dec 4, 2014
@untitaker
Copy link
Contributor

@svenstaro Thanks for this!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants