-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
State of Maintenance #702
Comments
Hello there! Well, I seem to have been removed as a maintainer on the this repo, but I am still a maintainer on pypi. Perhaps I can help with a new release! Shall we fork the repo? |
Yes, please. Patches and workarounds are now piling up in Gentoo. I'm happy to help getting things merged and moving them forward once there's a single place for them. |
If postman folks are amenable, I'd support taking this on in the @psf org, and possibly hosting for httpbin.org itself in the PSF infrastructure. (Though I would be interested to know what the current traffic numbers look like first). |
I've raised this at https://community.postman.com/t/status-of-maintenance-for-httpbin/48649 to try to get some response. |
No response on discussion forum. I went ahead and sent a support request 🤷🏼. |
I am getting random time-outs now:
I would recommend people switch to: |
The problem is not really the online instance but the package that (unlike online instances) can be used to test stuff offline. |
Still no response from postman folks. @kevin1024 @nateprewitt are you interested in forking at this point? I'd be happy to setup such a fork in the @psf organization, mapping the current owners on PyPI to the admins of the project. |
I’m still game for a fork. |
Yep, let's do it. |
Will proceed! |
Invites dispatched to the org/team for @nateprewitt, @kevin1024, @sigmavirus24, and @timofurrer. |
https://github.com/psf/httpbin now exists as a fork. Once accepted, the names above will have Maintainer privileges on the repository. We can have a discussion there over Admin level privileges. |
What will happen with the existing issues? I am currently looking into replacing a home-grown solution with I would like to open an Issue about this. But the fork currently has issues disabled. Should I open it here instead? Or wait until they are available in the fork? |
Thanks for flagging. I’ve enabled Issues on the fork. |
Well, I merged a couple of PRs that should fix the major issues with werkzeug 3 incompatibility and packaging over on the branch and have pushed a new version of httpbin to pypi. I hope this doesn't break too many builds out there and is a net positive for the world of open source http libraries :) |
We're strictly pinned for Requests currently but I'll take a look at testing the new release soon. Thanks @kevin1024! |
unsubscribe
…--
祝好!
连文静
在 2023-07-10 23:27:44,"Ee Durbin" ***@***.***> 写道:
Will proceed!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Actually, the project offers a nice Swagger/OpenAPI spec but it's invalid on multiple aspects (eg. uses old SmartAPI fields). |
@immanuelfodor please send that to the psf fork to get it merged |
Thanks for the suggestion! Where is the pfs fork deployed, in which domain will the change be live once merged? |
The repo is here: https://github.com/psf/httpbin |
Yes, I've found it, but my question was more about if the psf repo is the one that's deployed to https://httpbin.org/ now instead of the postmanlabs repo? Or if not, is there a "live" version of the psf one somewhere? Or it's just a Docker-only release for psf? BTW thanks for checking the Docker release! |
Unfortunately I don't know the answer to this. I assume that the domain is still owned by K. Reitz so chances are - currently - small that it will be deployed there. |
Hi there 👋
I'm reaching out regarding the maintenance of httpbin. There have been a couple outstanding PRs to help move httpbin forward with changes around Flask and its underlying components. Specifically that there's currently no working CI to test changes and #684 to help enable launching Python 3.12 support.
I wanted to check on the current maintenance status for the project and if there's intention to continue its development. Is there a good point of contact to help get the repo cleaned up or feature requests reviewed?
The text was updated successfully, but these errors were encountered: