New maintainer or fork needed?

[gpflaum]

@prkumar Are you still out there? This is a useful package but needs some maintenance. Would you consider adding someone to maintain it? Perhaps @djbios or @leiserfg would be willing to help?

[djbios]

I would love to help!

[leiserfg]

I could help next year, I'm semi offline til then.

[prkumar]

Hi ya'll - Apologies for my long silence. It's clear that I’m becoming a bottleneck for this package, and I want to make sure others can contribute without relying on me. Over the next couple of days and weeks, I’ll carve out some time to keep things moving and onboard additional maintainers. It’s a relay, and in the near-to-medium term, I’d like to pass the baton to a pool of maintainers.

@djbios and @leiserfg (or anyone else) - let me know if ya'll still have cycles to help out. I'll work on getting ya'll the access you need.

[djbios]

Hi ya'll - Apologies for my long silence. It's clear that I’m becoming a bottleneck for this package, and I want to make sure others can contribute without relying on me. Over the next couple of days and weeks, I’ll carve out some time to keep things moving and onboard additional maintainers. It’s a relay, and in the near-to-medium term, I’d like to pass the baton to a pool of maintainers.

@djbios and @leiserfg (or anyone else) - let me know if ya'll still have cycles to help out. I'll work on getting ya'll the access you need.

Hello :) Yeah, I am happy to help. Gonna need some accesses (github, pypi)

[leiserfg]

@prkumar I have some other ideas:

• Drop old pythons (ideally all older than 3.10, if not, at least 3.8)
• Move to uv
• Use ruff for formating/linting.

[djbios]

@prkumar I have some other ideas:

• Drop old pythons (ideally all older than 3.10, if not, at least 3.8)
• Move to uv
• Use ruff for formating/linting.

Agree with everything ^

[leiserfg]

I'll start with points 1 and 2. What version of python should I use as target? 3.10?

[leiserfg]

Points 1 and 3 are done and waiting for review.

[rafalkrupinski]

I'm maintaining a similar project https://github.com/python-lapidary/lapidary, although it's not as mature or elastic. Works only with httpx (planning migration to aiohttp) and pydantic2. It works together with lapidary-render, a client generator for OpenAPI 3.0

[leiserfg]

Uplink is back alive, we should have a new release soon.

[leiserfg]

@prkumar What is missing for a new release?

[prkumar]

@leiserfg - I think we are close! Created #320 to migrate our publish job to GitHub Actions. We can do an "alpha" release just to make sure everything looks good.

[prkumar]

New preview release v0.10.0a1 is published on PyPI: https://pypi.org/project/uplink/0.10.0a1/

Before official release, it would be good to update:

1. Public documentation to reflect changes (e.g., dropping Python 3.9 and below)
2. CHANGELOG
3. Anything else?

I'm working on #1 right now.