-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CNApy&CPLEX error under Mac OS X #491
Comments
Hello and thank you for submitting this issue! We had a user with a similar issue, it could only be solved by using the x86 version of Anaconda, and then using it with CNApy instead of Anaconda's ARM version. The problem is that, while CPLEX itself has its own Mac ARM version, CPLEX's Python binding somehow does not yet have an ARM version :-| We likely have to wait for the next (or one of the next) CPLEX versions to resolve this problem in a satisfying way, without the performance drop due to using Rosetta. |
Thanks, Paulo! It worked perfectly. Hopefully they will fix the issue |
@fcatrambone Hello once again :D We noticed that IBM pushed MacOS ARM PyPI wheels for the cplex package. Hence, with our switch to PyPI and the resulting new install procedures (for the latest version 1.2.2, see https://github.com/cnapy-org/CNApy?tab=readme-ov-file#installation-options), it might now be possible to directly use ARM-based python on MacOS. We're just lacking an Apple machine to confirm this :3 |
Hello!
I'm trying to install CNApy on an Arm Mac (M1) using miniConda (yes, the Arm version). However, it appears that the cplex package for arm64 does not exist in the repos. In fact, i get this error message:
LibMambaUnsatisfiableError: Encountered problems while solving:
Could not solve for environment specs
The following package could not be installed
└─ cnapy 1.1.9** is not installable because it requires
└─ cplex, which does not exist (perhaps a missing channel).
I have tried to install the regular cplex OSX64 package using conda install directly from the compressed file, but i still get the same error.
Anyone knows how to solve the issue? Thanks!
The text was updated successfully, but these errors were encountered: