conda env discussion
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- documentation
Research direction
The issue names no file, test, or entry point. First locate the tutorial section containing the conda discussion, then clarify whether the requested change is to retain, move, or revise it. Done means the intended conda guidance and its placement are explicitly agreed upon.
Written by the indexing model from the issue text.
Description
It was really valuable to add the conda discussion at the end. I think the end is the place for it cuz it's a bit abstract, but def helpful for people
- Dominant language
- Jupyter Notebook
- Stars
- 78
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DOI-USGS/python-for-hydrology
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
DOI-USGS/python-for-hydrology#212 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
DOI-USGS/python-for-hydrology#210 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
DOI-USGS/python-for-hydrology#193 · 1 comment ·
All issues in DOI-USGS/python-for-hydrology
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·