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

Compatibility with Python 3.9 #95

Closed
honzajavorek opened this issue Mar 3, 2020 · 10 comments
Closed

Compatibility with Python 3.9 #95

honzajavorek opened this issue Mar 3, 2020 · 10 comments

Comments

@honzajavorek
Copy link
Contributor

I'm getting following warnings:

/Users/honza/.local/share/virtualenvs/python.cz-s2NxYiyq/lib/python3.7/site-packages/flask_frozen/__init__.py:29
  /Users/honza/.local/share/virtualenvs/python.cz-s2NxYiyq/lib/python3.7/site-packages/flask_frozen/__init__.py:29:
  DeprecationWarning: Using or importing the ABCs from 'collections' instead
  of from 'collections.abc' is deprecated since Python 3.3,and in 3.9 it will stop working
    from collections import Mapping, namedtuple

tests/views_test.py::test_get_involved_cs_renders_ordinary_issue
  /Users/honza/.local/share/virtualenvs/python.cz-s2NxYiyq/lib/python3.7/site-packages/ics/icalendar.py:59:
  DeprecationWarning: Using or importing the ABCs from 'collections' instead
  of from 'collections.abc' is deprecated since Python 3.3,and in 3.9 it will stop working
    elif isinstance(imports, collections.Iterable):
@tswast
Copy link
Member

tswast commented Mar 3, 2020

Thanks for reporting. PRs welcome!

@hroncok
Copy link
Contributor

hroncok commented Mar 3, 2020

Is preserving Python 2 compatibility required?

@tswast
Copy link
Member

tswast commented Mar 3, 2020

I'd lean towards keeping in line with the latest version of Flask, but they do still support Python 2.7. https://github.com/pallets/flask/blob/64ba43411fbfb2e435455b0df2453d7809b7c5a8/setup.py

I think it's probably worth dropping 2.7 so long as Python 3.5 is still supported.

@honzajavorek
Copy link
Contributor Author

FYI, I'm getting failures with Travis CI trying to install Py 2.x versions under #97. But it also fails to install the PyPy versions, so I'm unsure what's the issue.

@honzajavorek
Copy link
Contributor Author

Added a tested solution here: #98

@tswast tswast closed this as completed in e9eb467 Mar 16, 2020
honzajavorek added a commit to honzajavorek/Frozen-Flask that referenced this issue Nov 26, 2020
@jayaddison
Copy link
Contributor

@tswast @honzajavorek Do you know if there are any plans to release a py3.9-compatible release of Frozen-Flask to PyPi?

@honzajavorek
Copy link
Contributor Author

I think it's mainly a matter of whether there's a contribution adding the support.

I'm unsure whether it's a big task or not, given we still support 2.7. If supporting 3.9 is easier (and cleaner) without 2.7, there's probably no big harm in watching when Flask drops 2.7 and only then add support for 3.9. I don't have any strong opinions about this though.

@jayaddison
Copy link
Contributor

Ok, that makes sense. The good news: running the Flask-Frozen test suite under Python 3.9, it seems to pass as-is. I'll open a pull request to enable CI in a moment.

@honzajavorek
Copy link
Contributor Author

OK so previously I've replied from my phone and I missed the fact this is closed already. I recalled I wanted to tackle this problem in #98, which even mentions 3.9 and I think it tests the issues and fixes them, but for some reason, I forgot to add it to the testing matrix 😄 So that probably explains why it passes as-is.

@jayaddison
Copy link
Contributor

No probs, thanks! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants