-
Notifications
You must be signed in to change notification settings - Fork 119
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
Issue with Anaconda Python on Mac (and Intel compiler on Mac, problem with PYTHONHOME) #618
Comments
I would like to share the output I get. In my case I installed python through Anaconda.
|
@alexsavulescu : I think this is worth adding to our next release milestone. I thought this is only with Intel Python but now reproducible with Anaconda python on MacOS as well. |
* Azure CI can be launched manually to upload wheels to nmodl-nightly or nmodl projects on pypi.org * Open Azure Web UI and set following variables: - `ReleaseWheelBuild = True` to build the wheels without nightly tag i.e. release wheel - `UploadWheel = False` to disable uploading wheels to pypi.org. This is useful for testing where wheels are built but they are not uploaded - `NMODL_WHEEL_VERSION = x.y` to override the version number created by `git describe --tags` command. This is helpful for testing/development purpose as pypi.org doesn't allow to upload same version wheels.
I tested this with the latest neuron (e.g. #3088) and Anaconda installation, I see that everything is working fine: $ PYTHONPATH=/Users/kumbhar/workarena/repos/bbp/nrn/build_conda_native/install/lib/python:$PYTHONPATH /opt/anaconda3/bin/python3
Python 3.12.4 | packaged by Anaconda, Inc. | (main, Jun 18 2024, 10:07:17) [Clang 14.0.6 ] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import neuron
>>> I will close this as the Intel toolchain on Mac is not that relevant anymore. |
Pull request #608 left off with a comment about building with
For dynamic python loading this is resolved with pull request #617 but there remain two issues with
-DNRN_ENABLE_PYTHON_DYNAMIC=OFF
First, when launching nrniv one needs an explicit PYTHONHOME
That is not a huge problem. Much worse is launching
Perhaps some hints that can help are
The text was updated successfully, but these errors were encountered: