-
Notifications
You must be signed in to change notification settings - Fork 258
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
PyScipOpt references old Scip version. Problem at import of pyscipopt #944
Comments
Hey @windgaetter, thanks for letting us know. In the meantime, can you try |
That works for me. No error when I try to import it. We use PyScipOpt in one of our conda packages. So,when you have that fix ready, we will be happy to use it again ! |
Hi. I was wondering if there are any news when there will be a new conda-forge version of pyscipopt, that could fix this issue here ? |
Hey @windgaetter, sorry for keeping you hanging. We suspect this is because we haven't released in a while. We're working on a new release, which should come out in the coming days |
Hey @windgaetter! We just released. Can you please let us know if your problem was fixed? |
@Joao-Dionisio Thanks for the new update. We can update to that new version, but run into the following: We run into the warning
when loading the Model class. Interestingly, in our conda environment, PyScipOpt is installed in conjuction with Scip 9.2.1. So the warning pops up a bit unexpected. We have this issue in both our remote pipelines as well as locally. Also
outputs version 9.0.2 instead of 9.2.1 . |
Thank you, @windgaetter, glad to hear that it's at least running now. This warning also showed up for other people (#951), maybe it's a problem with the linking we're doing. We'll look into it this week. |
@windgaetter, can you check whether the current master version is working as expected? |
We have the same issue a warning when using the package from PyPI version PySCIPOpt-5.3.0 |
@TheZwieback, can you please check whether the behavior persists with the current master? We still haven't released the version with the fix, but it shouldn't take long. Meanwhile, if you don't mind me asking: When you say "We", are you part of a company or a research group? We're always very happy to see our software being used :) |
Hi @Joao-Dionisio |
@Joao-Dionisio Thanks for the update. Locally it seems to work now without warnings. The master branch version worked. But remotely it still links the wrong SCIP version. I guess the fixed version is not yet published to conda ? |
@windgaetter yes, that's right, we need to do another release. Either the end of this week, or the next one, I'm guessing. |
@windgaetter, @TheZwieback we just released today. Would you mind checking if it's working now with the newest release? |
Describe the bug
Since the last Scip update, PyScipOpt references the wrong libscip version. This results in an error when importing pyscipopt. Currently conda automatically installs Scip 9.2 and PyScipOpt 5.2.1
To Reproduce
Create conda environment and install pyscipopt from conda-forge. Try loading pyscipopt
Expected behavior
I would have expected, that the version is automatically updated or the referencing scip version fixed.
Screenshots
System
Additional context
The text was updated successfully, but these errors were encountered: