pyscipopt: Update to 4.3.0, use tarball without generated .c files, run Cython instead

[dimpase]

📚 Description

pyscipopt's tarball has generated with an old Cython .c files. This breaks it on Python 3.11+, see
#35299

This fixes #35299 by switching to a tarball without .c files.

📝 Checklist

• [x ] I have made sure that the title is self-explanatory and the description concisely explains the PR.
• [x ] I have linked an issue or discussion.

[codecov-commenter]

Codecov Report

Patch coverage has no change and project coverage change: -0.01 ⚠️

Comparison is base (f449b14) 88.62% compared to head (c53044b) 88.61%.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #35303      +/-   ##
===========================================
- Coverage    88.62%   88.61%   -0.01%     
===========================================
  Files         2148     2148              
  Lines       398653   398653              
===========================================
- Hits        353308   353284      -24     
- Misses       45345    45369      +24     

see 26 files with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[mkoeppe]

You need to change the tarball line in checksums.ini because a file of this name is already on our mirrors and does not have the right checksum

[mkoeppe]

and now 4.3.0 is out

[mantepse]

works for me! Thank you!

[dimpase]

and now 4.3.0 is out

with 7.6MB scip.c file in PyPI tarball 🤦🏽‍♂️

[mkoeppe]

We can just keep using the github tarball

[dimpase]

We can just keep using the github tarball

I'm curios how they manage to keep these C files in. I can't figure it out.

[mkoeppe]

Their setup.py generates the .c file unconditionally, no matter what command is passed to setup.py.

[dimpase]

I don't know, but I don't get this issue on https://github.com/dimpase/primecountpy

[mkoeppe]

Yes, because there you call cythonize from within build_ext.

[dimpase]

would upstream accept such a change for pyscipopt?

[mkoeppe]

They accepted some other build system work that I sent as PRs

[github-actions]

Documentation preview for this PR is ready! 🎉
Built with commit: c53044b