-
Notifications
You must be signed in to change notification settings - Fork 508
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
Flask-RESTPlus is dead, long life to Flask-RestX #770
Comments
Merged
iksaif
added a commit
to iksaif/flacon
that referenced
this issue
Feb 19, 2020
leollon
pushed a commit
to leollon/yet-another-image-bed
that referenced
this issue
Apr 15, 2020
* Update:requirements:switched flask-restplus to flask-restx" due to issues [#777](noirbizarre/flask-restplus#777) [#770](noirbizarre/flask-restplus#770)
garaud
added a commit
to garaud/jitenshea
that referenced
this issue
Oct 20, 2020
Replace Flask-RESTPlus which is unmaintained by Flask-RESTX. Take a look at: * noirbizarre/flask-restplus#593 * noirbizarre/flask-restplus#770 fix #60
garaud
added a commit
to garaud/jitenshea
that referenced
this issue
Oct 20, 2020
Replace Flask-RESTPlus which is unmaintained by Flask-RESTX. Take a look at: * noirbizarre/flask-restplus#593 * noirbizarre/flask-restplus#770 fix #60
This was referenced Jun 4, 2021
yep |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello everyone,
It has now been almost a year since we first started discussions about the future of Flask-RESTPlus in #593.
During the past months, a few of us have been granted maintainers access on github: @SteadBytes, @j5awry, @a-luna and myself. Unfortunately, we never had access to the Flask-RESTPlus Pypi project, hence we have never been able to release any new version.
This situation led us to fork the project under a different name so we can move forward.
The new project name is flask-restx and it will be handled by the python-restx organization.
We are at the early stages and we still have a lot of setup/organization to do, such as CI, renaming, copyright checking, etc.
Our current milestone is to deliver the equivalent of the v0.14.0 that has been discussed in #743
After that, we will start migrate issues and PR that are still relevant and build a roadmap.
We'll let you know here when things are ready.
The text was updated successfully, but these errors were encountered: