-
Notifications
You must be signed in to change notification settings - Fork 35
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
Import error on Python 3.9 #164
Comments
celerite is tested and regularly used on Python 3.9 so I'm not sure that this is a generic issue. Can you say more about your system, setup, and exactly what commands you ran? |
System:macOS Catalina Terminal commands from scratch, leading to error:
|
I can't reproduce this issue, but I'm currently on an ARM mac with osx v11.6 so I can't directly test on your environment. I'd recommend trying to uninstall celerite and then re-install it from conda-forge: conda install -c conda-forge celerite or from source python -m pip install --no-binary celerite |
Thanks for your quick responses, Dan! Unfortunately the two suggested ways also did not work. The conda-forge install got stuck in an endless "solving environment" loop, while the source install resulted in a C compiler error. I also updated to Mac OS Big Sur 11.6, but still face the same issue. I think the reason is that I am using a custom gcc-8 compiler instead of the Mac compiler, because other Python packages (like ellc) do not work with the default Mac compiler. In any case, I think this issue can just be closed, seen that it is unique to me and works for other Python 3.9 users, as you said above. I will just use celerite1 on Python 3.8 and switch over to celerite2 in the future. |
I'm happy to try to help you debug this. Do you want to share the error message you get when compiling from source? There shouldn't be any gcc compatibility issues. |
Thanks Dan! I didn't want to steal more of your time, but since you offer it... ;) First, I set up a fresh environment, just as described above. Next, I clone celerite into a local folder. Finally, I go into said folder and execute
|
Note: I used the above approach because
resulted in the following error:
|
(Side note: the correct I pulled out my old laptop to try this out and I can reproduce your issues on it when using gcc. I got confused because the log in your first message said that you were installing using a wheel, but there is no wheel released for py3.9, so you must have already tried to install it from source with gcc as your compiler. The actual issues are two different pybind11 incompatibilities with gcc, so if you have to install celerite from source, I'd recommend using clang. I'll push a new set of wheels later today so that a wheel installation will work. |
|
Awesome, thanks Dan! Works like a charm, now I can pip-install, import, and run celerite on Python 3.9 while using gcc-8! |
Hi Dan,
I understand celerite is superseded by celerite2, but it would still be nice to keep the functionality alive for allesfitter users on Python 3.9.
To replicate the error: I set up a brand new conda environment with Python 3.9 and full anaconda. Then I pip-installed celerite and tried to import it as shown below:
The text was updated successfully, but these errors were encountered: