Update aiohttp constraints #74
Conversation
With aiohttp releasing 3.9.0, which supports 3.12, we need to update the current constraints
|
ping @Esmeray6 |
Ping someone from the top.gg team (if someone actually cares to look into these 🙃). I don't maintain the library anymore. Or did you just want a second pair of eyes? |
I'll take care of maintaining the library if you want me to do so. I'll contact the topgg team if they are able to merge this pr |
|
If nothing has changed by now, you'll have to run your changes through someone from the team (no collaborator permissions, you just create PRs and the team merges them). My wonder is whether anyone from the team will bother with this library after... 3? years of no updates to this repo. With this said, it's entirely up to you. |
True, but this PR doesn't really have any changes. The updated requirements for aiohttp follow the same exact requirements as discord.py's aiohttp version requirements. I'll try and ask someone on the team if I can help out |
|
It's more about the fact that maintainers, as far as I recall (3 years ago, give or take), don't have write access to the repositories. So, they're simply stuck with waiting for whoever to review the changes and accept the PRs. Correct me if that's changed at any point after that. Nevertheless, I'm just ranting off-topic at this point. My apologies. |
|
@No767 Additionally if you still want to maintain this library, I would prefer to be contacted by someone from the staff to transfer ownership of the PyPi package. |
|
@Esmeray6 Sure |
|
Any update on this? |
|
This PR is overwritten by #74, can be closed if that gets merged. |
With aiohttp releasing 3.9.0, which supports 3.12, we need to update the current constraints
Fixes #
Proposed Changes