RStudio Clone for Python – Rodeo

December 17, 2015

(This article was first published on OUseful.Info, the blog... » Rstats, and kindly contributed to R-bloggers)

So have you been looking for something like RStudio, but for Python?

It’s been out for some time, but a recently updated release of Rodeo gives an increasingly workable RStudio-like environment for Python users.

The layout resembles the RStudio layout – file editor top left, interactive console bottom left, variable inspector  and history top right, charts, directory view and plugins bottom right. (For plugins, read: packages).


The preferences panel lets you set the initial working directory as well as the path the required python executable.

Code selected in the file editor can be run in the console. Charts can be generated using matplotlib and are displayed in the chart view area bottom right.

As with RStudio, you can write reproducible research documents that blend markdown and code and render the result as HTML or PDF.


As you might expect, charts can be embedded as outputs in the document too.

Whilst the first version of Rodeo was a flask app viewable via a browser, and installable via pip, the latest version is an electron app, like RStudio. I found the ability to run Rodeo directly in the browser really useful, but the RStudio folks appear to have found a way of running RStudio via a browser using their RStudio server, so I’m hoping there’ll also be an open source version of Rodeo server available too?

One thing I’m wondering is whether Rodeo is a front end that can run against other Jupyter kernels? I notice that there is already a branch on the Rodeo github repo called r-backend, for example…?

Another thing I haven’t really clarified for myself are the differences between authoring (and teaching/learning) using the “Rmd/knitr” RStudio/Rodeo style workflow, and authoring in Jupyter notebooks. Notebook extensions are available that can suppress cell output etc to provide some level of control over what get rendered from a notebook used as an authoring environment.  I guess what I’d like for Jupyter notebooks is a simple dropdown that lets me specify the equivalent of knitr text result options that control how code cells are rendered in an output document.

See also: IPython Markdown Opportunities in IPython Notebooks and RStudio and Notebooks, knitr and the Language-Markdown View Source Option….

To leave a comment for the author, please follow the link and comment on their blog: OUseful.Info, the blog... » Rstats. offers daily e-mail updates about R news and tutorials on topics such as: Data science, Big Data, R jobs, visualization (ggplot2, Boxplots, maps, animation), programming (RStudio, Sweave, LaTeX, SQL, Eclipse, git, hadoop, Web Scraping) statistics (regression, PCA, time series, trading) and more...

If you got this far, why not subscribe for updates from the site? Choose your flavor: e-mail, twitter, RSS, or facebook...

Comments are closed.


Never miss an update!
Subscribe to R-bloggers to receive
e-mails with the latest R posts.
(You will not see this message again.)

Click here to close (This popup will not appear again)