Skip to content

Conversation

@selfisekai
Copy link
Contributor

No description provided.

@selfisekai selfisekai force-pushed the py3.10 branch 4 times, most recently from d5cc210 to 5f26f7c Compare December 16, 2025 19:33
@olzhasar-reef
Copy link
Collaborator

@selfisekai Thank you for your PR.
Python 3.8 support has been dropped after merging another PR. Could you kindly rebase your branch?

@ppolewicz
Copy link
Collaborator

Instead of dropping 3.9 can we use a variable version installation for phx-class-registry using qualifiers?

The thing is that a not-insignificant number of B2 customers install B2 on every system they own, even the legacy stuff that should have been upgraded years ago but wasn't. Well, at least it has backups :)

It's fine to drop support for 3.9, but lets do it when we really need to. If a little qualifier for the dependency will solve the problem, then I'd rather keep support for 3.9 until a stronger reason to drop it reveals itself (when we can revive this PR)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants