|
| 1 | +--- |
| 2 | +layout: page |
| 3 | +authors: ["Reticulate"] |
| 4 | +teaser: "Rethinking the Lesson Pipeline with reticulate" |
| 5 | +title: "Rethinking the Lesson Pipeline" |
| 6 | +date: 2018-05-15 |
| 7 | +time: "09:00:00" |
| 8 | +category: [ "Lesson Development"] |
| 9 | +--- |
| 10 | + |
| 11 | +If you had a look at [CarpentryCon](http://www.carpentrycon.org/)'s |
| 12 | +[program](http://www.carpentrycon.org/#prog), |
| 13 | +you might know that I will be facilitating two sessions: |
| 14 | +"Contributing on GitHub" on Wednesday, 30 May |
| 15 | +and |
| 16 | +"Bring and Build Your Own Lesson 'Carpentries-style'" on Friday, 1 June. |
| 17 | +During the process to organise both sessions, |
| 18 | +I have ben thinking a lot of what we could improve |
| 19 | +in the way that we write our lessons. |
| 20 | +One of the things that I know that annoys many of the maintainers |
| 21 | +is the fact that they need to copy and paste the output of each command. |
| 22 | +RStudio has been work in a new project called [reticulate](https://rstudio.github.io/reticulate/) |
| 23 | +that "enables easy interoperabilty between Python and R chunks" |
| 24 | +and in this process they have made it much easier to use Python from R Markdown. |
| 25 | + |
| 26 | +I created [one pull request to swcarpentry/lesson-example](https://github.com/swcarpentry/lesson-example/pull/202) |
| 27 | +with an concept idea of using `reticulate`. |
| 28 | +The pull request includes some screenshots |
| 29 | +of Bash and Python code chunks being processed by R Markdown. |
| 30 | +This is one discussion that all members of the community are welcome to participate in, |
| 31 | +so please leave a comment on the pull request |
| 32 | +or, even better, find me during CarpentryCon to talk about it, |
| 33 | +if you are at what promises to be a great conference. |
0 commit comments