-
Notifications
You must be signed in to change notification settings - Fork 42
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
pipenv install fails on macOS 10.15.2 #95
Comments
The error occurs after Not being familiar with pipenv, I presume the registration in its system failed somehow. |
@bnavigator I dunno... I just ran |
I can reproduce this on Ubuntu 18.04, with Slycot 0.3.5 from PyPI. Using current Slycot master, I tried I then built a wheel and installed that with pipenv (I'm not really a pipenv user, so this might be nonsensical), and I ended up with the same CMake-F2PY build error. Despite the error, slycot was installed in the pipenv-managed virtual environment. It looks to me like this error happens in the lock process; why CMake, etc., are being run at that point I don't know. For now I'd recommend using conda instead of pipenv for Slycot; as I understand, they are mutually exclusive, but achieve similar "dependency locking" ends. If anyone can provide a fix for whatever Slycot's build does that prevents pipenv use, that would of course be welcome. |
Is this still an issue with Slycot 0.4.0? |
This is fine on Ubuntu 20.04 with pipenv 2020.11.15 and Slycot 0.4.0 (see pipenv output below). Within the created venv, I tested
|
Installing in a fresh virtualenv works, but installing via pipenv does not.
Somehow opening up ipython and importing slycot still works even after it fails though...
The text was updated successfully, but these errors were encountered: