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.
HungryKonata
commented
3 years ago
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.