Is latest v0.9.23 unsafe (like 0.9.22)?

@MilesCranmer I noticed that you avoid 0.9.22 (and that you're aware of 0.9.23):

https://github.com/MilesCranmer/PySR/commit/ca7706ef8ffc2ce3b927b0f578a2bb8c4c68b968

If 0.9.23 is ok, then you may want to support it there, and was this an issue only for juliacall, or also PythonCall.jl?

I want to know mainly that latest version works for all users (not just you), and more about the hack to disable then enable GC. Is that something people need to be aware of or maybe outdated now?

I know packages can't be removed from the (Julia General) registry, but can't certain (older) versions be revoked? Is that needed here? That applies from the Julia side, and I'm not sure how things are handled from the Python side, pip, conda etc. So where might revoking be needed for Python packages, or would you way it's the responsibility of package authors (only) to avoid bad releases? It would not stop people to use non-latest of your package with the issue...

Start by reviewing commit ca7706ef8ffc2ce3b927b0f578a2bb8c4c68b968 and the discussion of versions 0.9.22 and 0.9.23. Investigate whether the concern affects PythonCall.jl, juliacall, or both, and how Julia General, pip, and conda handle bad releases. Done means an agreed, evidence-based explanation of the release safety and any required action.

Escrita pelo modelo de indexação a partir do texto da issue.