Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introducing the IPython notebook #10

Closed
tracykteal opened this issue Jun 9, 2015 · 16 comments
Closed

Introducing the IPython notebook #10

tracykteal opened this issue Jun 9, 2015 · 16 comments

Comments

@tracykteal
Copy link
Contributor

For the R lessons we have an 'Introducing RStudio' module. It would be nice to have an 'Introducing the IPython Notebook' in the Python lesson.

IPython Notebook itself is a great thing to teach for data analysis, so it seems very worthwhile to teach and use the IPython notebook in these lessons.

@tracykteal
Copy link
Contributor Author

Have these lessons been taught with IPython notebook or with command line Python?

@lwasser
Copy link
Member

lwasser commented Jun 9, 2015

Hey tracy -- we taught these lessons using the notebook. it's definitely convenient BUT its nice for folks to know basic shell to open it. Although with anaconda there is a gui icon that you can use to open it too but then you need to set the working directory.

@tracykteal
Copy link
Contributor Author

Thanks @lwasser. @cmacdonell is going to be teaching @FCTweedie Python NLTK lesson and was thinking about the best way to start, and whether or not to use the notebook. It's good to hear it worked well for you. He is teaching the command line first, I think, so that should help with being able to start anaconda.

Maybe we should include that setting of the working directory in an 'Introduction to IPython notebook'?

@tracykteal
Copy link
Contributor Author

@lwasser
Copy link
Member

lwasser commented Jun 9, 2015

hey tracy --
there is still a very old PR for you to merge but i added a section on setting the working directory here

https://github.com/lwasser/python-ecology/blob/gh-pages/01-starting-with-data.md

If they open the notebook in shell from the director where there data are, then they're good. otherwise they can check it and set it. i think it' sgood in general to check it because sometimes folks forget to open it from a meaningful directory in shell :)

we definitely did an informal "welcome to ipython notebook!". i think having something like that documented could be great.
l.

@tracykteal
Copy link
Contributor Author

Thanks I saw that update in your PR. PR looks good. I just had a couple comments. Sorry for the slow response on that. :(

@lwasser
Copy link
Member

lwasser commented Jun 16, 2015

Thanks @tracykteal ! please don't apologize! i completely understand busy schedules!!! :)

@iamc
Copy link

iamc commented May 10, 2016

I did write a ipython-quickstart notebook some time ago for an introduction to scientific Python and plan to use it for my next (and first :-) workshop as an instructor. I may adapt it for these lessons if you want.

https://github.com/iamc/PySS15-scientific-python-tutorial/blob/master/ipython-quickstart.ipynb

@qjcg
Copy link
Contributor

qjcg commented May 11, 2016

Hey @iamc, this looks great! It might be good to add some short challenges (ex: asking learners to create a notebook, run some cells, verify that the notebook has been saved on their system) Also, replacing references to the "IPython notebook" with "Jupyter notebook" would be a forward-looking approach, as the version shipping with anaconda prints the following warning message when ipython notebook is run:

$ ipython notebook
[TerminalIPythonApp] WARNING | Subcommand `ipython notebook` is deprecated and will be removed in future versions.
[TerminalIPythonApp] WARNING | You likely want to use `jupyter notebook` in the future

@iamc
Copy link

iamc commented May 11, 2016

Hi @qjcg. So if you are willing to accept something on this line I'll adapt it with your suggestions and also to the lessons template, this as our workshop gets closer and time permits :-)

@qjcg
Copy link
Contributor

qjcg commented May 14, 2016

Awesome, thanks @iamc, please do submit a PR with your adapted lesson when it's ready.

@iamc
Copy link

iamc commented May 16, 2016

OK, I'll do it.

@djinnome
Copy link
Contributor

djinnome commented Dec 4, 2016

Hi folks,

The markdown files in this tutorial can be automagically converted to Jupyter notebooks using notedown . Would folks be interested in a PR that consists of a script that downloads notedown and converts these lessons to Jupyter notebook?

@qjcg
Copy link
Contributor

qjcg commented Dec 10, 2016

Sure @djinnome, if you have a proof of concept script to submit, please do send along a PR!

@djinnome
Copy link
Contributor

djinnome commented Dec 18, 2016

Hi @qjcg,

The pull request is Port from R to python of Lesson 05 Data visualization with ggplot2.

In this PR, I converted the R ecology lesson from markdown to a Jupyter notebook (using notedown) that executes correctly using an R kernel, and then manually ported it to a Jupyter notebook that executes correctly using a python kernel. I then converted the python Jupyter notebook to markdown (using nbconvert) in order to comply with Data Carpentry standards.

ctb pushed a commit to ctb/python-ecology that referenced this issue Dec 30, 2016
@tracykteal
Copy link
Contributor Author

It looks like there's still not an 'introduction to the Jupyter notebook' section. It would be useful to have.

maxim-belkin pushed a commit that referenced this issue Mar 24, 2021
zkamvar pushed a commit that referenced this issue May 8, 2023
Fix gh-pages display of fenced code blocks. We'll need to add the other original contributors of this material to the YAML as well.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants