Clarify setup instructions on python interfaces

[ha0ye]

How could the content be improved?

What I see as an issue:

The setup episode points to installing Anaconda, and mentions the iPython console, jupyter notebook, and Spider IDE. There is then a bit of instruction on the interface for Jupyter notebook and Spyder.

Then the first episode seems to point in the direction of using a CLI python interpreter.

Possible Solution:

Follow the example of the Software Carpentry python lesson and provide explicit options and instructions.

Further, specify in the first episode if it is expected that the whole lesson be taught using the python interpreter.

Which part of the content does your suggestion apply to?

https://datacarpentry.org/python-ecology-lesson/00-before-we-start.html

[jas58]

Today I was practicing install for tomorrow's workshop and noticed anaconda.com now implies one must register with an email to see the page with the download option. The directions may need an additional step (in the setup where we don't allow suggestions, hence why I'm writing an issue here):
Add after 1 and before 2
"You may "Skip registering" your email to reach the page with the installation button for your operating system."

[jas58]

Also, agree with Ha0ye that clarification for a novice instructor like myself on when to demo inside the black/text window and when to switch to the browser notebook would be great.

[katrinabrock]

I would suggest removing Anaconda as an option or at least put a heavy caveat. They now require a paid license based on the organization type/number of employees. This could be a barrier to some participants who are members large orgs, but don't themselves have the authority to buy a license. It's not just a matter of instructing participants on how to literally download and install. If a workshop participant is in a situation where they would need a business license based on Anaconda TOS, probably not a good idea to encourage them to download and install on an "individual practitioner" basis. If Anaconda is really the tool of choice/required for this workshop, that should be made clear when participants register for the workshop so they have time to buy a license or determine what, if any, exemption they qualify for. (Maybe this is already happening and I'm not aware?) I think it is probably easier to just design the tutorial based on tools that do not have this complexity.

[katrinabrock]

Looks like this has been thoroughly discussed on carpentries slack here: https://carpentries.slack.com/archives/C03LE48AY/p1720546103358779

[jas58]

Thanks, Katrina. I'll try to find the exact lines to edit.
The first paragraph of https://datacarpentry.github.io/python-ecology-lesson/00-before-we-start.html#knowing-your-way-around-anaconda ---should we remove that paragraph? Or use strike through text? Or at least move it to end of that section and not lead with it?
I'm making that PR now to instead say:
While Anaconda comes with a package manager called conda
used to install and update additional packages, since 2024 the terms of use are difficult for institutions, education, or individuals. Anaconda distribution of Python includes a lot of its popular packages, such as the IPython console, it may be wiser to install and run Jupyter Notebook or Spyder IDE directly, without Anaconda.
see PR #628

[jas58]

And
https://swcarpentry.github.io/python-novice-inflammation/#install-python
may need that whole section re-written, so I'll add a PR there and link to this discussion for them.
in https://github.com/swcarpentry/python-novice-inflammation/edit/main/learners/setup.md
I created this PR
swcarpentry/python-novice-inflammation#1105

[jas58]

Oops, probably duplicated myself at #629

[katrinabrock]

Sorry! Didn't mean to misrepresent myself. I'm not a maintainer, I'm just a guy with opinions. This needs input from maintainers.