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
unhandled AttributeError on listing current env #39
Comments
Confirmed. I get the same:
|
@csoja: this may be one we want to get fixed quickly before 4.3 is finalized. @kalefranz it looks like the |
I think this is related to https://github.com/ContinuumIO/navigator. It's an egregious leak of conda's internal abstractions. I didn't realize it was all just being barfed out as json, and that's what the interface was relying on then. The problem we've solved internally in conda relates to a line of code
apparently in nb_conda and a ton of other places. This string parsing of the package name is NOT reliable, and it will become more unreliable over time. I'm going to try to reconstruct the json output for the interface in 4.3 to what I think are the important pieces from 4.2. |
@timsnyder @ijstokes which version of conda are you using?
@kalefranz what do you recommend us to use instead? Thanks! |
@damianavila I'm facing the same problem when I update my conda to 4.3.5 but it's working fine with my downloaded conda version of 4.2.9 |
conda v4.3.6 should fix this issue - it is available in the conda-canary channel, if you'd like to give it a try to confirm that it fixes the issue. https://anaconda.org/conda-canary/conda |
Thanks for the info @csoja! |
4.3.6 didn't, but 4.3.7 should. Should be out in another 36-48 hours.
… On Jan 19, 2017, at 3:10 PM, Damian Avila ***@***.***> wrote:
conda v4.3.6 should fix this issue - it is available in the conda-canary channel,
Thanks for the info @csoja!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
4.3.7 is out now. |
I have conda version 4.3.8 installed and I'm still getting this error. |
@tikwanleap Can you post your stack trace, even if it's exactly the same? Also please provide |
Conda is working as expected, but I've created an additional test. I'm making a PR here that brings nb_conda up-to-date with conda 4.3. |
stack trace:
conda info:
|
@kalefranz Thanks for fixing this bug so quickly in PR #42! May I propose an alternative version that avoids using the hasattr() function? I read this article that advises against using hasattr(): https://hynek.me/articles/hasattr/ I have tested it locally on my computer and it also fixes the bug.
|
@tikwanleap I updated the PR with different code. The exceptional case now should actually be the string splitting. Apparently, calling
in both python2 and python3. |
@kalefranz Looks good! Thanks! |
I'm also still getting this error in 4.3.8. Stack trace:
conda info:
I've also tried 4.3.9 using
|
There is a question regarding this bug on stackoverflow. I've posted my temporary solution using the branch containing the fix there. Have I missed a more official channel to pull in the fix? |
@damianavila sorry I missed your question from a few weeks ago. Looking at the env export I attached in the original bug description, I had whatever was pulled in by 'anaconda 4.2.0'. I don't see the conda package itself in the env export output. Let me know if you want me to take a closer look at the conda I had installed when I opened this. BTW, I'm also around at AnacondaCON today and tomorrow morning. |
Nop, this is the official one but a little bit behind because of other priorities... sorry about that. Soon we will have some time to address all these issues. |
No problem, the issue is identified. We just need to merge things and wrap up a release. Hopefully this will happen in the next few weeks. |
Just a head's up... since my userbase is starting to run into this more and more in our install of AEN, I've resorted to monkeypatching Kale's fix into the wakari-compute site-packages. It made me a little nausious for a minute but I couldn't wait any longer. |
I'm still seeing this as of 20170325 - what's the latest temporary fix / workaround? BTW, I'm stuck at Python 3.5 (or 2.7) because of ContinuumIO/anaconda-issues#1423 Maybe I should just drop back to Conda 4.2.0?? |
I understand... I will ping here when the fix is merged and packaged. |
Two option for now:
The fix lives here: #42, but still not merged nor packaged
That would be a workaround for the time being... hopefully I will be able to build packages containing the fix by next week. |
Is nb_conda 2.2.0 published to any conda channel yet? I have Anaconda 4.3.1 running and I am facing the same issue. I saw that PR has been merged and released in version 2.2.0 but I am not able to find a way to update nb_conda. Newer version isn't being displayed with conda search or conda update command. Could you suggest a way to get this updated version in conda env? Thanks! |
Never mind, found it on conda-forge! |
@csoja looks like nb_conda 2.2.0 is tagged. In case you didn't already have it on the package build list... |
@kalefranz it is tagged but we still have to figure out (discuss) some things before putting it in defaults. I am pretty sure @csoja already have it on her package build list 😉 |
Fixes 'dict' object has no attribute 'rsplit' caused by versioning information returned by conda being a dictionary See anaconda/nb_conda#39
I have tried all the links in this page and still it doesn't work... This is the information in my console after all these attempts...
Now I am stuck with Jupyter here and can't move on... Please help, thanks! |
@wesleyzhan, what is your conda version? And the nb_conda version? |
I too was having this issue (conda 4.3.25, Linux Mint 17.2 Rafaela, Ubuntu 14.04.2 LTS, Trusty Tahr). I attempted the usual update remedies to no avail so I patched the code on line 16 of .../site-packages/nb_conda/envmanager.py.
becomes:
This seems minimally invasive, since examination of the dict that is passed always contains a well formed dist_name, and apparently the code expects exactly that. This was helpful to me, YMMV. |
When trying to use the Kernel->Conda Packages menu entry provided by nb_conda, I'm encountering the following unhandled exception:
cat-1.yaml.txt is the output of conda env export for my environment. Before filing this ticket, I also had @groutr repro the behavior.
The text was updated successfully, but these errors were encountered: