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
Not attaching to xonsh installation #2
Comments
Hmm, it should work with IPython 4, is it listed under |
No it isn't...
|
What version of xonsh are you on? |
I just released a new version, please try |
Awfully sorry guys - I figured out it was due to the xonsh program at I installed
I ran ... the bad news is there are now 2, one seemingly installed via
Sorry if I've gone about this the wrong way. I was getting /usr/bin/env: python -u: No such file or directory so I rewrote the #!/usr/bin/env sh
export PYTHONUNBUFFERED="XONSH_SET"
/usr/bin/env python -c "from xonsh.main import main; main()" and solved this issue. The kernel still doesn't work though so I'll leave the logs above in case they help debug the issue. |
Does it work if you: |
@blink1073: No change there unfortunately |
Bummer, I'm afraid I'm out of ideas on this one. |
I get the same as @lmmx, both with using xonsh and xonsh_kernel as the kernel. |
There is more discussion of the fix at xonsh/xonsh#565, which I think just needs to be cleaned up to provide a |
Cheers, I still get this problem even with PYTHONUNBUFFERED set - I get no response from the "xonsh" kernel, while the "xonsh_kernel" kernel gives me the error in the TypeError referenced in the first post. An interesting thing to note is that when when I use the "xonsh" kernel, i while I get very high CPU usage: effectively one CPU fully utilised. When I look at whats using it, it is a bash process, running a scrip that I think is created by foreign_shells.py, at least it starts:
When I kill jupyter, this continues to run, one of these had been running for 18 hours before I caught it. |
Hi @IanSudbery, Ok can you try a couple of things then please? The first is to see if we can get this to stop by not loading bash. Set the foreign shells section of your config file (~/.local/config/xonsh/config.json) to empty: {"foreign_shells": []} Does the high-cpu Bash process still get spawned? The second thing to try is to turn off the safety and have bash throw an exception. For this, set you config file to: {"foreign_shells": [
{"shell": "bash", "safe": false}
]
} Does this throw an error, and if so, what? Note that these can be separate files that you pass in at the command line via |
Hi @scopatz, Thanks for your help. If I set foriegn_shells to empty, then I don't get the high CPU Bash process. The kernel sort of works... In python mode, I can type python and get responses. However, in subprocess mode, the output goes to the terminal I started jupyter from rather than to the notebook. At this point, I have lost control of the terminal ^C, ^Z do nothing and I have to kill the juptyer process from elsewhere. If I set bash to unsafe, I get the same as before ... no response at all from the kernel and a high-cpu Bash process. |
@IanSudbery - OK, some progress at least. What version of jupyter are you using? |
@scopatz -jupyter 4.0.6 |
Hmmm OK. I am seeing this issue now too. |
This should be fixed on master xonsh now. |
I can't verify, because I could not reproduce, I'll wait for @IanSudbery or @lmmx to chime in. |
Sorry, I've been away, I'll try to test this out today. |
Works great now from both Xonsh master and here. |
Great, thanks, closing as fixed. |
I installed with
pip install xonsh_kernel
on IPython 4.0, Python 3.5 (Anaconda on Linux Mint)pip show xonsh-kernel
says it's installed:But no entry in
~/.local/share/jupyter/kernels
(wherematlab_kernel
went for example) nor in~/.ipython/kernels
nor in/usr/local/share/jupyter/kernels
, and so no entry in the 'select kernel' menu item, and "No such kernel error" when I runipython qtconsole --kernel=xonsh_kernel
Have I missed something obvious here or is this a work in progress..? Or perhaps not compatible with IPython 4 yet ?
The text was updated successfully, but these errors were encountered: