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
conda install: incompatible with existing python 3.8 #487
Milestone
Comments
I see that the python version for conda was incremented from 3.6 to 3.7 in our latest release in October (see history of file brainiak/.conda/bin/build).
I don’t know why 3.7, perhaps we’re being conservative.
I think for now it’s better to update the instructions rather than try to increment this version with another release.
From: Samuel Nastase <notifications@github.com>
Reply-To: brainiak/brainiak <reply@reply.github.com>
Date: Saturday, November 14, 2020 at 6:13 PM
To: brainiak/brainiak <brainiak@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [brainiak/brainiak] conda install: incompatible with existing python 3.8 (#487)
I assume this is a "known" issue, but I'm curious what the recommendation is. When creating newer conda environments, the default python installation is going to be 3.8 (or apparently 3.9 at this point), but our BrainIAK specification is pinned at python <3.8... This means that the conda installation instructions on the website<https://brainiak.org/docs/installation.html#conda> will only work if BrainIAK is one of the first things you install in the conda environment—right? (This has happened to me a couple times where I start building an environment with other generic python packages, then get to BrainIAK and am stuck.) Why are we pinned at <3.8, and what's the recommended fix here? Is the recommendation to just roll back the python version in my conda environment to please BrainIAK? Unless we're planning to unpin this soon, we might want to explicitly mention this on the installation page.
$ conda install -c brainiak -c defaults -c conda-forge brainiak
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: \
Found conflicts! Looking for incompatible packages.
This can take several minutes. Press CTRL-C to abort.
failed
UnsatisfiableError: The following specifications were found
to be incompatible with the existing python installation in your environment:
Specifications:
- brainiak -> python[version='>=3.6,<3.7.0a0|>=3.7,<3.8.0a0']
Your python: python=3.8
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#487>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AH7ZDPPL7ALBGCECTKRWL23SP4FKRANCNFSM4TV2GDVQ>.
|
hi there. Having the exact same issue -- so brainiak is not compatible with python 3.8? How can I work around this? This may have been stated in the response above but if so, it went over my not-so-techy brain. Thanks, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I assume this is a "known" issue, but I'm curious what the recommendation is. When creating newer conda environments, the default python installation is going to be 3.8 (or apparently 3.9 at this point), but our BrainIAK specification is pinned at python <3.8... This means that the conda installation instructions on the website will only work if BrainIAK is one of the first things you install in the conda environment—right? (This has happened to me a couple times where I start building an environment with other generic python packages, then get to BrainIAK and am stuck.) Why are we pinned at <3.8, and what's the recommended fix here? Is the recommendation to just roll back the python version in my conda environment to please BrainIAK? Unless we're planning to unpin this soon, we might want to explicitly mention this on the installation page.
The text was updated successfully, but these errors were encountered: