Xonsh support about euporie HOT 16 CLOSED

Hi,

This should "just work" by installing xonsh's Jupyter kernel and selecting the "xonsh" kernel in euporie.

However, it looks like there is currently an unresolved bug in the xonsh kernel which prevents it from working properly in the latest version of xonsh.

from euporie.

With xonsh_jupyter fixed as per xonsh/xontrib-jupyter#10, if you change your kernel to xonsh, you can run xonsh in euporie:

However, testing this has thrown up a couple of bugs in euporie:

• The xonsh pygments lexer is not shipped with pygments, which caused an error (fixed here: 4227b4d)
• The kernel fails to start if the xonsh kernel is selected at startup rather than if it is switched to from a python kernel. I'm not sure what's causing this, I'll have to look into it.

from euporie.

I've added:

• the section about Euporie to xontrib-jupyter
• the mention of Euporie to xonsh repo readme

Todo:

• When you push the next release I'll announce the Euporia to the community.

Thank you for your efforts to support xonsh!

from euporie.

I've made a new release v2.3.2 which has all the fixes mentioned above.

With the fixes to xontrib-jupyter-shell, xonsh now works really nicely in euporie 🏆

from euporie.

I've posted news:

1. to the xonsh channel on gitter:

2. to our new account on mastodon:

from euporie.

Wow! Looks awesome! Thanks! I will share this to the xonsh community.

from euporie.

@joouha feel free to add xonsh or/and xontrib topics to the repository settings.

from euporie.

Wow! Looks awesome! Thanks! I will share this to the xonsh community.

Thanks! It won't work out-of-the-box just yet, I still need to fix some bugs and make a new release, but I'll update here when everything works as expected.

from euporie.

Ok! I will wait the next release. Thanks!

from euporie.

Mentioned Euporie in xonsh 0.14 release.

@joouha if you have time please test xontrib-jupyter. I tried to run it with Euporie and sometimes when I run just ls in the cell I have no result in output.

from euporie.

You'll notice that xonsh commands implemented in Python return output, while there is no output from external commands.

This is because the xonsh kernel isn't capturing the stdout of subprocesses spawned by xonsh properly.

from euporie.

I've had a quick look, and it looks like xonsh transforms subproc-mode input lines into uncaptured subprocess calls, which get sent to stdout and are not captured by the kernel.

If you set the XONSH_CAPTURE_ALWAYS environment variable to True, it will work as expected.

I'll make a PR to set this be default in the xonsh kernel.

from euporie.

Thanks! XONSH_CAPTURE_ALWAYS is False by made decision and PR is not needed. We just need to add this to docs around jupyter xontrib.

from euporie.

It looks to me like the current default value of XONSH_CAPTURE_ALWAYS is False - it HAS to be True for xonsh kernel to capture subprocess output properly, so I think the PR is needed.

from euporie.

Ah, you mean PR into xontrib-jupyter. Yep, agree. Thanks!

from euporie.

Yes, I meant this one:

xonsh/xontrib-jupyter#21

:-)

from euporie.