News for hackers. Stuff that matters.

qacek

Re:JupyterLab is ready for users on Tuesday February 20, 2018 @08:38PM (#16426102)
Are there any plans for the JupyterLab and colab to unfork? Parts of colab seems nice but this feels like a google product that could get pulled at any moment
Re:JupyterLab is ready for users on Tuesday February 20, 2018 @02:57PM (#16423597)
I see, well you might get a better answer from a Jupyter dev. I use the autoreload extension to automagically pull in my lastest code [1]. It usually works. For your second question you can connect multiple frontends to the same kernel [2].

[1] https://ipython.readthedocs.io/en/stable/config/extensions/a...

[2] https://jupyter-notebook.readthedocs.io/en/stable/examples/N...

Re:JupyterLab is ready for users on Tuesday February 20, 2018 @01:48PM (#16422821)
Are you referring to editing text files or in notebooks?
Re:JupyterLab is ready for users on Tuesday February 20, 2018 @01:46PM (#16422790)
Re:Introducing Dash – Reactive Web Apps for Python on Wednesday June 21, 2017 @02:02PM (#14606333)
I suppose each framework has their own shortcomings compared to Shiny. I wonder what key features are missing from those frameworks that would make it a viable option for you?

I wish I could answer this myself but I am somewhat ashamed that I never used Shiny due to R.

Re:Lesser-Known Python Data Analysis Libraries on Tuesday April 19, 2016 @04:48PM (#11530263)
Thanks, I am happy to accept PRs that expose more functionality.
Re:Lesser-Known Python Data Analysis Libraries on Tuesday April 19, 2016 @02:32PM (#11529076)
I like plotly as well but I couldn't stand the python api nor cufflinks for that matter so I created my own wrapper. It's not fully featured but it handles 90% of the cases I want.

https://github.com/jwkvam/plotlywrapper