You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I appreciate your interest for improving PyJulia. But I'd like to minimize the interface related to python-jl as there would be better ways to support PyJulia in wider range of Python installations (see also #268 (comment)). I hope you are not discouraged because I'm closing this.
BTW, checkout https://github.com/tkf/IPython.jl if you want a "better" version python-jl -m IPython. I think it's strictly better than IPython for using PyJulia because you have access to both IPython and Julia REPL (plus some event loop coordination).
Thanks, appreciate the thoughtful response. You brought up good points about the Jupyter kernel, will reply in that issue, but here I really think you should reconsider. I totally agree python-jl should go away as soon as it can, but currently it does have to exist so why not just make things slightly more userfriendly where we can? Its not as if this is some API that will be hard to deprecate later, its just what people type to launch an interpreter.
I'm very close to implementing an "ultimate solution" #256. Basically, the blockers are dropping Julia 0.6 support (which in turn is blocked by PyJulia 0.3 release) and new PyCall release. Once this is implemented, the information related to ipython-jl would be harmful as it would misguide users. The reason why I said I'll not get rid of python-jl very soon was not because python-jl will still be a valid solution but because to keep backward compatibility for a while.
Due to the limited resource in development, we need to focus on good solutions. python-jl is not a good solution because it is impossible to make it right. There is no guarantee that the Python environment that python-jl is installed in and the Python environment active inside python-jl session are the same. This would be extremely confusing for people who are not familiar with how Python imports work.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Seemed a more seamless experience for Pythonistas.