python-ecology-lesson icon indicating copy to clipboard operation
python-ecology-lesson copied to clipboard

Data Analysis and Visualization in Python for Ecologists

Results 96 python-ecology-lesson issues
Sort by recently updated
recently updated
newest added

The [Starting With Data lesson](https://github.com/datacarpentry/python-ecology-lesson/blob/gh-pages/_episodes/02-starting-with-data.md) refers to data types like characters and factors which are not in Python. I'm guessing this is a carryover from the R lessons. `A DataFrame...

I recently taught a demo of Episode 2: Short Introduction to Programming in Python https://datacarpentry.org/python-ecology-lesson/01-short-introduction-to-Python/index.html Under **Introduction to Python built-in data types**, comments are introduced but not yet explained: ```...

good first issue

In episode 3 (https://datacarpentry.org/python-ecology-lesson/03-index-slice-subset/index.html, actually listed as 4. in https://datacarpentry.org/python-ecology-lesson/ ), the distinction between `.iloc` method for accessing entries by position and `.loc` to access them by identifier is made,...

help wanted
good first issue
high priority

Instructions Thanks for contributing! :heart: If this contribution is for instructor training, please email the link to this contribution to [email protected] so we can record your progress. You've completed your...

Hi, I have made changes in Lesson: Data Analysis and Visualization for Ecologists: Episodes 05 and 09. This is for Carpentries Instructor Checkout. Thank you! Silvina

Comment & code refers to *rows* while text mistakenly refers to *columns* Fix to #479

The [Index, Slicing & Subsetting episode](https://datacarpentry.org/python-ecology-lesson/03-index-slice-subset/) has a typo in the *Copying Objects vs Referencing Objects in Python* section. The Python code snippet is ```python # Assign the value `0`...

Changes folder in the introductory suggested project layout from **scripts** to **code** Referenced in issue #471, the *Before we start* episode 0 suggests keeping Python code in a **scripts** folder....

type:bug

I ran into a hiccup teaching this lesson while trying to explain the utility of a `scripts` folder. Since python scripts are also modules that can be imported, you can...

- Make references more explicitly to `pandas` rather than "Python" - Add lots of `code` style formatting where appropriate - Replace references to `isnull()` with `isna()`. These methods are exactly...

type:enhancement