Conversation
|
We need to remove |
|
Actually, I'm not sure that's true, since 3.8 still has wheel, so it should not trigger the warning. We probably can drop at the same time. |
Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>
09f7a7b to
b3c6282
Compare
|
Yes. Technically pypy3.11 is the only non-EoL PyPy now, but it's easier to match since there isn't a way to maps python-requires depend on the Python implementation. But yes, pypy3.8 should not be present! |
|
Ok, thanks! Wwould you welcome a pull request with that cleanup (note/clarification: only the removal of |
|
Sure. :) If you want to add pypy3.11 while you are at it, you can, but fine if you want to leave that up to us eventually, too. |
|
Great, OK. I'll offer an advancement of the PyPy versions, in that case (removing It also seems to me that we can remove the |
|
Ah; my mistake - because PyPy v3.9 is still supported, there are some older runtime versions of that could be affected by the |
|
If there's any version with 3.9 that is fine (pypy3.9-v7.3.16?), I'd be tempted to simply say that we don't support anything older than whatever that version is (7.3.16 or 7.3.11?). People should not be using old PyPy versions that are unsupported; if we can say "please update to 7.3.16 to fix the bug", I think that's fine. Depends on the opinion of other maintainers, though. |
…924) * chore: drop PyPi v3.8 Follow-up to #891 * tox: add `pypy311` to `env_list` matrix Ref: #891 (comment)
Dropping 3.8.