These are chat archives for evhub/coconut

6th
Sep 2016
x10an14
@x10an14
Sep 06 2016 08:32
@evhub Hiya! Still can't get an interactive Coconut console opened, even with your description of how to here and here. I got time to attempt it on Linux @ home before I went to work, and I've now tried here at work on Windows too. Again, I still get the same error as shown here, even though I activated the virtualenv and ran the --update command on a clean, new, venv =/.
I reckon we've got some timezone difference, but I'll check in here throughout my day, and try to remember to log on again at home =)
Evan Hubinger
@evhub
Sep 06 2016 19:32
@x10an14 Strange. Just to be clear, does it work if you try it outside of a virtualenv? Like, if you do:
pip install coconut jupyter
coconut --jupyter console
x10an14
@x10an14
Sep 06 2016 19:49
@evhub You mean without having activated a virtualenv? I haven't tried that.
If you meant without activating a virtualenv, but utilizing its binaries directly, (or even with activating it), then yes, I have tried that.
The error message on Linux differs from the one on Windows though, I'll upload it to a gist now.
@evhub Here's the attempt on Linux. A different error message, but a hunch tells me they're related.
If you check the gist's revision history, the latest revision shows the attempt with added "--verbose" flag.
x10an14
@x10an14
Sep 06 2016 19:54
Meanwhile you get to see this, I'll work on the assumption that you meant attempting to install jupyter and coconut in the global space of a machine, with no virtualenv involved whatsoever, and try and see how that goes.
x10an14
@x10an14
Sep 06 2016 20:03

@evhub Here's my attempt in invoking your

pip install coconut jupyter
coconot --jupyter console

commands with no virtualenv involved whatsoever. All binaries/libraries/installations were in the machine's "global" space. (Which as you can see from the pip freeze commands is already sufficiently polluted).