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

Requirements - developing environment #4

Closed
ttimbers opened this issue Jan 19, 2016 · 9 comments
Closed

Requirements - developing environment #4

ttimbers opened this issue Jan 19, 2016 · 9 comments

Comments

@ttimbers
Copy link

What about using Rodeo instead of the Notebook or editing nano? I have heard great things, and it looks very similar to RStudio (which works quite well for teaching). One issue to be aware of is that installing Rodeo and having it work with the Anaconda Python distribution we ask learners to download requires editing the PATH. We don't want to ask learners to do this, so we need to come up with some sort of installer to smooth this out.

@ttimbers
Copy link
Author

Also, if we are using Rodeo (or something like that) we could skip the last section (Jupyter Notebook) and shave 35 min off of the lesson.

@lexnederbragt
Copy link
Contributor

The environment/editor question is a tough one, and I don't think there is an optimal solution. All of them have quite a bit of cognitive load (running a script file requires the shell, as Greg wrote, Jupyter notebook has (too) many functionalities that will confuse learners). Anaconda comes with sypder, which I have a tried a little bit and like - it puts small warning signs in the margin if there is a syntax error, for example. Rodeo may be a good alternative, but will take time to become comfortable - there are two windows for python commands, one of them is IPython, not python, etc. One advantage is that learners may have seen, or will see, Rstudio, making the Rodeo/Rstudio combo a recognisable duo of environments.

Do we know what instructors are using, especially those that do not use Jupyter? Worth asking them?

@gvwilson
Copy link
Contributor

gvwilson commented Jan 19, 2016 via email

@lexnederbragt
Copy link
Contributor

I don't remember when I installed it, but I have Rodeo 0.2.4 on MAC OS X Yosemity (10.10.5) and it works through Chrome.

@lexnederbragt
Copy link
Contributor

Here is another option: with python comes IDLE (on my mac /Users/username/anaconda/bin/idle). Starting IDLE gives a interactive python session (shell), with the possibility to open a separate window for a script, save the script and execute it in the shell. A bit clumsy, but it works for getting everyone started. Once learners are comfortable with it, they can switch to spyder (comes with Anaconda), textwrangler (MAC) or something similar?

@gvwilson
Copy link
Contributor

People have complained about IDLE's user interface ever since it was
created, and we can't ask Data Carpentry participants to run things from
the shell. And I just tried launching Spyder with Python 2.7 / Anaconda

  • it hangs on my Mac as soon as I try to edit a file, possibly because
    it can't import something called 'hashtable' which I can't be bothered
    to try to track down. Does TextWrangler support in-editor execution?

@lexnederbragt
Copy link
Contributor

Does TextWrangler support in-editor execution?

Yes - but I think it is MAC only...

@gvwilson
Copy link
Contributor

sigh Why can't everyone just use VMS? Now there was an operating
system...

@gvwilson
Copy link
Contributor

I spoke with @tracykteal and we decided that the Notebook was the best option (at least for version 1).

rgaiacs pushed a commit to rgaiacs/swc-python-novice-gapminder that referenced this issue May 6, 2017
Synchronizing with changes to template.
zkamvar pushed a commit that referenced this issue May 2, 2023
Adding string indexing and why not number indexing
zkamvar pushed a commit that referenced this issue May 2, 2023
The choose a type challenge has pretty ambiguous questions and answers. This PR aims to clarify some of them.

proposed answers are:
- for #2 I’ve specified units in days, forcing the choice of ‘floating point number’
- for #3 I’ve added that string or integer are fine depending on type of serial number
- removed #4 entirely because what is the age of a lab specimen? I’m sure 1000 labs have 1001 ways of measuring that
- for #5 (new #4), specified in the answer that float or integer are fine depending on units
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

3 participants