test on py3.12

[graingert]

No description provided.

[sethmlarson]

@graingert Is pytest-httpbin==2.0.0rc1 going to be promoted to stable?

[graingert]

@sethmlarson hopefully, just blowing the dust off of CI kevin1024/pytest-httpbin#76

can you get someone to look at https://github.com/postmanlabs/httpbin/pull/684/files ?

[nateprewitt]

@graingert, httpbin appears to be in a pretty rough state. It was moved under @postmanlabs when they started hosting the live endpoint but has since been relatively abandoned. They kicked all the previous maintainers off the project and don't appear to have any resourcing allocated to it. I've tried reaching out a few times without any meaningful response.

Going forward, we may either need to fork it or move Requests onto a different testing dependency.

[nateprewitt]

I cut postmanlabs/httpbin#702 to see if we can get a more public response there on maintenance status.

[graingert]

@graingert Is pytest-httpbin==2.0.0rc1 going to be promoted to stable?

@sethmlarson I've just pushed v2.0.0 to pypi!

[nateprewitt]

Thanks, @graingert!

[kevin1024]

They kicked all the previous maintainers off the project and don't appear to have any resourcing allocated to it. I've tried reaching out a few times without any meaningful response.

Well, I seem to have been removed as a maintainer on the github repo, but I am still a maintainer on pypi. Perhaps I can help with a new release!

I also (occasionally) maintain https://github.com/kevin1024/pytest-httpbin which relies on httpbin, and https://github.com/kevin1024/vcrpy/

Shall we fork under psf or would you like me to fork under my own name?

[nateprewitt]

Hey @kevin1024, thanks for checking in! I believe you, Ian, and myself are the three with release perms on PyPI so we can definitely go that direction. I was going to wait out a response on the issue above for a bit longer before we take on the task of forking.

I think there are also a number of changes Kenneth merge between the last release and now that may need vetting before we cut something new. If we don't hear anything back going into July, I think that's probably time to look at taking action.

Edit: Don't let me stop you from doing this sooner if you're motivated. I just wanted to minimize churn/maintenance overhead if possible.

[kevin1024]

Hello fellow maintainer! Works for me. Let's wait a bit longer for a response before forking. My main motivation for forking would be to fix:

postmanlabs/httpbin#673

So that I can fix:

kevin1024/pytest-httpbin#72

So that I can fix:

kevin1024/vcrpy#645

Basically: https://www.youtube.com/watch?v=AbSehcT19u0