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
Need nb_conda for Python 3.6 #1423
Comments
same here,
|
Same here... |
Apparently, I'm not alone with this issue... |
Getting this same error, thanks in advance guys. |
conda-forge doesn't help out Anaconda Repo customers who mirror the main
repo but not channels (and have firewalls).
On Feb 24, 2017 3:58 PM, "Martin Durant" <notifications@github.com> wrote:
As far as I understand, conda-forge/nb_conda-feedstock#4
<conda-forge/nb_conda-feedstock#4> should build a
py36 conda-forge package automatically.
—
Yoou are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1423 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACRTeY999AQoT1bV1u74udG9ASO_3QtVks5rf0RjgaJpZM4L4e05>
.
|
UnsatisfiableError: The following specifications were found to be in conflict:
|
I'm joining the bandwagon...getting the same error. Thanks in advance. |
I was traveling and didn't have a chance to verify conda-forge, but nb_conda is also not there for the latest Python/Anaconda: 505-tmp % conda install nb_conda -c conda-forge
Fetching package metadata .............
Solving package specifications: .
UnsatisfiableError: The following specifications were found to be in conflict:
- nb_conda -> python 3.5* -> sqlite 3.9.*
- nb_conda -> python 3.5* -> xz 5.0.*
- python 3.6*
Use "conda info <package>" to see the dependencies for each package. |
If I were only trying for Python 3.5 I guess this would succeed using conda-forge, but that's not what we need. We need it in the main channel, and also for 3.6. |
It seems rather cumbersome to me that the four nb packages (nbpresent, nb_anacondacloud, nb_conda, nb_conda_kernels) depend on one another as we have to wait for all four packages to be updated in order to install the one we may want. As of today, I believe it is just nb_anacondacloud (a package I have no intention of using) which has yet to be updated, but stops me using nb_conda (and thereby Python 3.6). |
I am new to Anaconda. It is on Windows 10 with latest Anaconda 64 bit install. ` UnsatisfiableError: The following specifications were found to be in conflict:
C:\Users\Ajit>conda info
` |
Packages will be available in the next few weeks. I will let you know when it is done. Thanks. |
does it work for 3.5? If so, I'll just drop back to Miniconda 3.5 |
FWIW, I am creating a 3.5 environment and it works, i.e. it allows me to switch between different environment kernels. e.g.
|
Same here.... UnsatisfiableError: The following specifications were found to be in conflict:
|
+1 |
@DavidMertz I am getting the same error.
with
Is there any temporary work around for this? |
Create conda env using python 3.5 and it works fine then. |
@trmanish: Yes, that is exactly what the bug reports! There's no support for the latest Python. As indicated in all the above comments, there is support for older Python versions. |
It's kinda strange that the current Anaconda-package for python 3.6 makes you default stuck in this situation. I just installed it, and instantly hit this road block when trying to use jupyter with environments (which everybody tells you to use..) |
All, finally, I have some time to work on this. |
@damianavila, putting a package on |
This extension are no longer shipped with Anaconda by default... so... do you want to have it available from repo.cio before closing this issue? @mingwandroid @csoja |
Yes. bugs in |
Fair enough... sorry for the premature closing. Let's figure out how we can ship the latest release into repo.cio as soon as you (or the team) have time availability. |
I could install |
I also succeeded in installing |
Hi all,
|
@oshribr just get it from conda-forge with |
@damianavila ;-(
|
You have very old extensions there. Suggestion:
and then
and finally
If that works for you, then you should clean you root environments getting rid of the old extensions. |
Can we not just get this fixed in defaults? What's currently blocking it? |
I think nobody has had the time to create packages for 3.6. |
There are further complications, I will open an issue to describe them and discuss how we solve it properly. |
How does one "clean" the root environment? |
In this case, essentially conda remove ANY extension from your environment. Plus, IF there is some leftover in the activation/enabling step, you probably need to audit some notebook config files (such as PREFIX/etc/jupyter/nbconfig/*). |
Over three months since this issue was first opened... are we any closer to a new release in official channels? |
Yes - it is high on the list after the upcoming Anaconda v4.4 release. The way the notebook extensions were installed from defaults was different than from conda-forge. The current defaults method requires all the extensions to be updated for Python 3.6 - and not all of them are. We are looking into changing the approach for defaults so that the notebook extensions can be updated individually (including nb_conda). |
@csoja, yes separating out the extensions would certainly be my preference (see original comment) |
Changed sentence from reveal wasn't working with Python 3.6 to nb_conda wasn't working with 3.6 (see here ContinuumIO/anaconda-issues#1423).
What about nbpresent ? |
@ilanschnell is updating the extensions in defaults now - these should be available later today. Please let us know if you continue to have issues with them. |
(moved from conda/conda#4539 (comment))
There currently does not seem to be support for
nb_conda
that is compatible with Python 3.6. This makes it cumbersome to work with Py36 environments that use Jupyter. Or in Jupyter when you need to choose an environment (whichever way you want to look at it).The text was updated successfully, but these errors were encountered: