Patrick Byers

I added the steps discussed in #244 to the documentation in a drop down section because these felt like optional steps and I saw this formatting used in another location...

Typo - Initial version code recommended is inconsistent (Major and Minor versus Major, Minor, and Patch?) - installable-code.md

5

During the tutorial, changing the initial version in the `project.toml` to `"0.1.0"` is recommended; then, in the following example, it is listed as only `"0.1"`. https://github.com/pyOpenSci/python-package-guide/blob/7b422d4256cdb89d40c8b2b19227e4a5d8078817/tutorials/installable-code.md?plain=1#L393C1-L400C28 I'm a fan of...

TODO - How to update your package name / prevent name overlap by adding your github to the package name

6

Glad to see this is a TODO: https://github.com/pyOpenSci/python-package-guide/blob/a9fc8c19b1b63113fea3b66bd06177c53be2aa5a/tutorials/publish-pypi.md?plain=1#L206C1-L213C4 I will document the steps I take here; if desired, I can make a PR with changes that walk a reader through...

Consider linking to information about environmnets/venv - get-to-know-hatch.md

1

The following tip feels like the first time this tutorial has mentioned environments and managing where/which environment(s) Python packages are installed into. https://github.com/pyOpenSci/python-package-guide/blob/7b422d4256cdb89d40c8b2b19227e4a5d8078817/tutorials/get-to-know-hatch.md?plain=1#L14C1-L18C38 Consider adding a link to internal or...

I came to recommend adding information about environments / virtual environments, but you already have a TODO documented in your markdown. https://github.com/pyOpenSci/python-package-guide/blob/7b422d4256cdb89d40c8b2b19227e4a5d8078817/tutorials/installable-code.md?plain=1#L502C1-L505C4 Once you decide what documentation you want to...