Socksio is archived but it's what we use in the extra

[mbeijen]

First of all I don't like proxies and I really feel for all people needing to use them.

Then again, there are people that need to use them and there also are a bunch of issues with the implementation in httpx.

The HTTPX2 [socks] extra uses socksio which is ARCHIVED at this point.

I think the best alternative is to maybe deprecate this altogether and use a plugin such as https://github.com/romis2012/httpx-socks

[Kludex]

I've asked Seth to donate the package and he suggested to unarchive and to add me to the maintainer list there.

That package has 5 million downloads, so I assume it's slightly relevant anyway (given that I think only httpx depends on it).

[Kludex]

What are the issues with httpx?

[hugovk]

For reference, there's a brief httpx discussion about using python-socks instead of socksio at encode/httpcore#667.

If this project does vendor socksio, or you take it over, one thing to watch out for is that sethmlarson/socksio#61 removed the upper <3 pin on flit-core, but it still uses flit-specific metadata which was removed in v4.

Thanks to @mgorny for spotting this.

[Kludex]

I prefer the sans-io design from socksio.

@sethmlarson I mentioned this during PyCon US to you, which approach would you prefer us to take here?

[sethmlarson]

Hey @Kludex, I can add you and I'll also be adding @illia-v as a stakeholder from urllib3 to both be co-maintainers with me. I'll unarchive the project on PyPI and GitHub, please open GitHub issues and assign me if there are buttons that only I can press during this transition.

[illia-v]

I've joined as a socksio maintainer.
@Kludex would you still like to join as well so we can make the final touches before a release?

[Kludex]

I think I've accepted the invite. No need to wait for me, release as you wish.

As long as it doesn't break httpx2, and it's maintained, I'm happy. 🙏

[illia-v]

As I understand it, the idea is for the project to be maintainable with minimal ongoing involvement from Seth. With the repository set up as it is today, that means having two maintainers who can take care of releases without depending on Seth.