-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Remove depreacted use2to3 option from setup.py #60
Conversation
I am also getting the same error while building the pipelines - error in Flask-OpenID setup command: use_2to3 is invalid. |
@nikhil-2011 you can buy time by using older version of setuptools like |
Thanks for the suggestion @getumen , Is there any other way out to solve this issue or this will be corrected by upstream team? |
This deprecation is an important one to fix. |
There was a change to It would be great if we could have a new release of |
Yep. That would really be helpful - as it breaks pretty much all historical installations of Airflow, and there is basically nothing we can do about it unless a new version of flask-opeind is released without the option. @mitsuhiko @puiterwijk - any chance for that ? or maybe you give access to someone (happy to do so) in GitHub/PyPI to rebuild/release it. |
FYI. We have forked and created a release in apache/airlfow (we were able to workaround the problem because we are using constraints mechanism to install airflow): So the .tar.gz is there - https://github.com/apache/airflow-flask-openid-fork/releases/tag/v1.2.6 We literally need to release it to PyPI to solve it for others too @mitsuhiko @puiterwijk ? The Airflow Issue where we track it is here: apache/airflow#18075 |
More context: pallets-eco/flask-openid#60 apache/airflow#18075 Using Airflow patched fork for now
Does this codebase even work without 2to3? I haven't touched it in years. |
First of all thanks for coming back @mitsuhiko ! I do realise it's pretty much "abandoned" for you and you are more into Rust than Python now, but I appreciate, you get back even after so long time. The problem was not about the code and it's functionality - we could likely very easilly incorporate it - either to FlaskAppBuilder or Airflow (I am talking now about the two impacted projects that I know of). But more of the problem is that it breaks already released versions of our software (of course it's because of setuptools, not flask-openid, but well - it breaks). It looks like it should work. I believe 2to3 was not introducing any serious changes, just removing some extra stuff that is not needed any more in Python 3 - not at least in the last version. And yeah. I will defer to @dpgaspar to test but I could actually very easily release a package "after" pre-processing it by 2to3 and I could change requirements to Python 3 only to be absolutely sure (happy to take on the task if you can trust me :) ).
|
Just getting access to GitHub and PyPI to release it would be enough. Releasing 1.2.6 with Python 3 only compatibility afer processing it manually by 2to3 is something I am happy to do (just in case both IDs for GitHub and PyPI for me is @potiuk and you can likely check - especially my Airflow activity if you are afraid if you can trust me :). |
I own ~ 140 packages on pypi (all apache-airflow related :D) |
Looks like @mitsuhiko I'm also willing to share ownership of the project. Let us know what you'd like to see for it. I'm interested in getting this fixed as it's the most prominent blocker to avoid reverting Setuptools 58. |
#61 extends this PR to apply the Python 3 only changes. |
basestring is only used in if Python <3 branch |
Happy to hand this over to someone who wants to take care of it. |
I volunteer :) @mitsuhiko |
I gave you both access to this repository. Please send me an email / leave a comment for pypi access. |
sent |
Added |
Would it be possible to grant me PyPI access? I’m also an Airflow maintainer and can help publish some wheels for the project. (Actually already have the 1.3.0 one ready.) My PyPI account name is the same as GitHub (@uranusjr). |
Ah. too late @uranusjr - I just released them :) |
Brand new https://pypi.org/project/Flask-OpenID/1.3.0/ released now! |
Still without wheels though 😉 |
Would be good to get wheels too |
Thanks again @mitsuhiko ! That is really helpful and thanks for being so responsive and open! It's not often, even in open-source world ! |
I just encountered this issue #59 Monday morning and a Google search led me here. |
Since Septembre 6th, 2021, the use of the setup option is no longer accepted and leads to failed builds. This is reported in issue #59.
This pull request proposes to removing this option from setup.py.
I didn't see any test suite though, so I couldn't should make sure all the code is compatible with newest version of Python (which seems so).