I am desperately trying to get this to work with my pyenv-virtualenv anaconda installation, but I can't get it to work out.
I also tried setting the path the ~/.pyenv/shims/python, but that didn't work out either.
A native Python IDE built for data science
31–40 of 47 posts
Re: A native Python IDE built for data science
#32In the last year, my workflow for data science/AI has completely shifted to Jupyter notebooks. Is there any IDE that offers a similar experience?
Jupyter dev here. FYI, we're currently working on building a new Jupyter web interface that resembles a more classic IDE experience, which we are calling JupyterLab. A first version is progressively coming together, and is planned to have code editor and terminal components. We also plan to have a notebook component, like the current notebook, in a later version. Our in-progress work is spread across many repos currently (see the various jupyter/jupyter-js-* repos on github).
Re: A native Python IDE built for data science
#33Just curious, what qualifies it as Native?
I am curious about this as well. Taking a look at the source ( https://github.com/yhat/rodeo ) it appears to be in all python. I was under the (perhaps mistaken) impression that native referred to code which compiled to assembly.
[deleted]
Re: A native Python IDE built for data science
#34Just curious, what qualifies it as Native?
as in native desktop
Re: A native Python IDE built for data science
#35In the last year, my workflow for data science/AI has completely shifted to Jupyter notebooks. Is there any IDE that offers a similar experience?
There is Beaker notebooks which is similar to Jupyter. Haven't tried it but you can integrate multiple languages in one notebook. http://beakernotebook.com/
I really like the idea behind beaker, but last time I played with it, the main issue/concern occurs for me when using a somewhat large (uses most of machine RAM) dataset, since using it in another language creates an additional copy of the data in memory for the other language to use. This multiplies the memory used by the number of languages that need an instance of the dataset. If there could be shared memory for datasets somehow, it would be much more useful (if they've figured that out since I last used it, please tell me).
Re: A native Python IDE built for data science
#36honest question: what if your science isn't maths/physics/data? I'm a chemist and from what i can see there's @#$@# all out there in FOSS land.
Re: A native Python IDE built for data science
#37See also: Pycharm https://www.jetbrains.com/pycharm/
And also Pythons Tools for Visual Studio.
Re: A native Python IDE built for data science
#38Why should I use this over Spyder?
Re: A native Python IDE built for data science
#39honest question: what if your science isn't maths/physics/data? I'm a chemist and from what i can see there's @#$@# all out there in FOSS land.
Use R! https://cran.r-project.org/web/views/ChemPhys.html https://cran.r-project.org/web/views/Pharmacokinetics.html
I doubt anyone doing data analysis is unfamiliar with R, as it is the current standard. The push to use Python, or Julia, or a version of Lisp (hey, we had that in the 1990s -- us olds remember xlispstat) for data analysis is coming from the people who find R to be a rather unpleasant language. Which is a subjective opinion, obviously, but not an uncommon one.
Re: A native Python IDE built for data science
#40Earlier quoted context omitted.
I am curious about this as well. Taking a look at the source ( https://github.com/yhat/rodeo ) it appears to be in all python. I was under the (perhaps mistaken) impression that native referred to code which compiled to assembly.
When referring to tooling for a language, 'native' tends to mean it's written in that language.
I always thought native meant native to the platform.