Installation of non-standard packages

[cpsanchez]

Reminder to decide a standard way of instructing users to install non-standard packages in the tutorials.

[ttdu]

The format STScI follows is to create a folder with the same name as the notebook, then put the notebook and a "requirements.txt" file into that folder.

The "requirements.txt" file should look something like:
astropy >= 4.2.0
matplotlib >= 3.3.3
numpy >= 1.19.0

Here's our formatting guide for additional details.
https://github.com/spacetelescope/style-guides/blob/master/guides/jupyter-notebooks.md

[kelle]

I vaguely recall that we were not going to do a requirements.txt file. I will discuss with @eteq and/or Scott -- kelle (via iOS)

[kelle]

Relevant to #10 (gphoton)

[jrka]

Should we also link to the package's docs on how to install? Presuming the URL is stable enough.

[ttdu]

Should we also link to the package's docs on how to install? Presuming the URL is stable enough.

Generally, that's not necessary. If you think the package is particularly tricky to install, you can add the link. But if "pip install [package]" works, I wouldn't add it.