Python Package Template

This template is based on the Scientific Python Development Guide. The main differences with the template they provide is that this is an opinionated template, where I made certain decision I feel are optimal. Additional, this is setup for packages which have complex non-Python dependencies which can be installed with pip, but require conda. This is useful if your package will depends on packages such as GeoPandas, PyGMT, or Cartopy, as these all depend on code written in C or C+ which is easiest to install with conda.

If you just want to host some code but not publish it as a Python package, I have a simpler template for that.

The below steps will create a complete Python package with testing, a documentation website, and builds uploaded to both PyPI (pip) and Conda-Forge (conda) for each new version release in GitHub. While it is quite tedious to initially setup, once you finished the below steps, almost everything is automated. The documentation website is automatically generated for each new PR, and new package versions are automatically released to PyPI and Conda-Forge each time you manually create a GitHub release.

Packages which have used this template

• None yet 😔

Template Instructions

Steps: 1) Initiate your repository: - on this template's page, click the Use this template button to Create a new repository. - choose a project name - for simplicity, this name will be used for all of the follow: the folder name that holds this repository as well as the code folder under src/, the name of the python package on both PyPI and Conda-Forge, and the repository name on GitHub. Because of these constraints, the best choice is a lowercase word with no spaces or punctuation. While capitalization and punctuation may help readability, they greatly increase the hassle during various stages of the packaging. Ensure your chosen name is available on both PyPI and Conda-Forge. - choose if you want the repository in your personal account or in one of your organization's accounts. - add a 1 sentence description of the package. - choose public or private. This can be changed later, but to be published on PyPI or Conda-Forge, or for the documentation website to work, it needs to be public. - create the repository - update any repository settings, below are my recommended settings: - enable discussions - only allow squash merging (disable the other options) - always suggest updating pull request branches - automatically delete head branches - protect the main branch so any changes to it need to be made through a Pull Request. - go to the repository's Settings, Branches, Add branch ruleset. Name it "protectedmain", make the Enforecement status Active, include the Default branch as the target, and check the following Rules: Restrict deletion, Require a pull request before merging, only allow Squash as a merge method, and Block force pushes 2) Update this template: - clone your repository to your computer with git clone <url of the github repo>; if you create the repository on an organization's GitHub instead of your personal one, first fork the repository before you clone it. - change all instances of samplepackagename in this repository with your chosen name. (If use a program like VSCode use a search and replace function (i.e. ctrl+f)), there should be over 100 instances of samplepackagename. - this includes the folder name of src/samplepackagename/ - replace all instances of yourname with your name - your name can be "Maintainers of " if there are multiple people. - replace all instances of organizationname with your GitHub organization (or personal) account name, whichever is going to host the repository. - update pyproject.yml with a description (1 sentence) and keywords. - add a description of your project here in the README, in docs/index.md, and in .zenodo.json. - add your info (name, affiliate, ORCID) to AUTHORS.md and .zenodo.json - at this point, it might be good to make your initial commit to your repository with the following git commands: bash git checkout -b new-branch git add . git commit -m "initialize template with names" git push -u origin new-branch - in the GitHub repository, go to the Pull request tab and open a PR for your changes. Merge this into main. 3) Pull in your merged changes - how you do this depends if you pushed your changed directly to the repository, or through a fork of the repository: 1) PR submitted directly to repository: - fetch your recent changes: git fetch - checkout your main branch: git checkout main - OPTIONAL: delete your feature branch: git branch -d new-branch - pull in your changes: git pull 2) PR submitted through a fork: - fetch your recent changes: git fetch upstream - checkout your main branch: git checkout main - OPTIONAL: delete your feature branch: git branch -d new-branch - merge changes from upstream: git merge upstream/main - this syncs your local repository to the upstream one - push your changes to your upstream (forked) repository: git push origin main 4) Add your code - decide on a module name(s) - these need to be lowercase, should be short and while possible, shouldn't include underscores. - if your package is going to be small, a single module with the same name as the package is fine. If it's going to be more than a few hundred lines of code, it's best to separate your code into distinct modules which perform similar tasks. - for each module you want do the following: - create / rename the existing file: src/samplepackagename/module1.py - create / rename the test file: `tests/testmodule1.py - add a description of the module todocs/overview.md - replace all instances ofmodule1with your module's name. - add your code to your module.pyfiles. - you have two options for how users can import your code. 1)``python from samplepackagename import module1

        module1.function1()
        ```
        - this option is available by default for any functions you write, and is nice if you have several modules because it clearly shows where the code is coming from.
    2) ```python
        import samplepackagename

        samplepackagename.function1()
        ```
        - to allow `function1` to be imported as above, you need to manually add it to the list in `src/samplepackagename/_init_.py`. If you only have 1 module, this may be a better technique.
- add tests for your modules' test file in `tests/`.

5) Specify your dependencies - dependencies for your package should typically only be those that are directly used (imported) in your source code (or are explicitly needed but not import), but not the dependencies of your dependencies. If you use a package in your documentation, but not in the source code, include this as an optional dependency. If you have a portion of your code that some users may not utilize, such as visualization functions, the dependencies you require for that, such as matplotlib, can also be include as optional dependencies to reduces the constraints for users who don't require it. - core dependencies are specified in pyproject.toml under the [project] section with the format dependencies = ["pandas", "scipy>=1.0"]. - optional dependencies are specified in pyproject.toml under the [dependency-groups] section with the following format, for example for optional documentation dependencies: docs = ["sphinx>=7.0",]. - if you know your package has an issue with a specific version of a dependency, you can set a max or min version with "scipy>=1.0". - dependencies should almost never be pinned to specific versions, as this will cause many issues for anyone who wants to use your package in their own environments. - for standard scientific packages (i.e., pandas, xarray, and numpy), as well as the version of Python, it's recommended to set minimum support versions following the timeline of SPEC 0 guidelines. - this template also includes files and commands to create conda environments. These are used both in developing, and in GitHub automations. You need to manually ensure the dependencies listed in environment.yml match those in pyproject.toml. Include all optional dependencies in the environment.yml. If a dependency is only available via pip, and not conda, add it at the bottom to be installed via pip. 6) Create environment, style check, test, and commit your changes. - follow the instructions in CONTRIBUTING.md starting at section Setting up nox and stopping before Publish a new release. - these steps should result in a merged PR with your code. 7) Set up automated Zenodo releases (only for Public repositories) - if you haven't already, link your organization (or personal) GitHub account to Zenodo using Linked accounts under your Zenodo profile. - do to the GitHub menu on your Zenodo profile. - click the Sync button and then turn on the switch for your repository. - any future GitHub releases should now result in a new Zenodo release and DOI automatically. 8) Set up publishing on TestPyPI - before publishing to the real PyPI, we will publish to Test-PyPI to ensure everything works . - make an account on TestPyPI. - under 'Your Projects', and 'Publishing', 'Add a new pending publisher', fill out your info. - the project name and repository name should be what you chose for samplepackagename. - the owner should be what you used from organizationname. - Workflow name should be cd.yml - Environment name should be pypi - note that this doesn't reserve your package name until you make your first actual release! 9) Make a GitHub release - On the main GitHub page, on the right side click Create a new release. - click Select tag and type v0.0.1. - set a Release title: "Initial release" - click Publish release - this should automatically trigger a few things: 1) a DOI will be added to your Zenodo, add this DOI to docs/citing.md. 2) the GitHub action CD should be triggered, create a release of v0.0.1 to TestPyPI. - to test this worked correctly, run the below commands to create a new conda environment using the TestPiPI release, and run your codes tests. bash mamba create --name test_pypi python mamba activate test_pypi pip install -i https://test.pypi.org/simple/ samplepackagename nox -s test 10) Make a PyPI (pip) release - if the install and test above worked then we can change from TestPyPI to normal PyPI. - in .github/workflows/cd.yml comment out or delete the last line: repository-url: https://test.pypi.org/legacy/. Now any future reruns of this action will release to PyPI. - in this case, since the GitHub release has already been made, we need to manually trigger the CD workflow in GitHub. - At this link, click the Run workflow button. - This should build the package and release it to PyPI. 11) Set up publishing on Conda-Forge - create a conda-forge recipe and feedstock with the below instructions: - Create a new environment using : mamba create --name grayskull grayskull - Activate this new environment : conda activate MY_ENV - Generate the recipe : grayskull pypi --strict-conda-forge https://github.com/organizationname/samplepackagename - this should create a meta.yaml file, which is the recipe. - fork and clone the stage-recipes repository on conda-forge. - checkout a new branch : git checkout -b samplepackagename - create a new folder : staged-recipes/recipes/samplepackagename - copy your meta.yaml file into this folder, remove the meta.yaml from wherever it was generated. - commit and push your changes to your fork, and in the main repository open a PR. 13) Set up GitHub Pages to host the documentation website - this will only work for a public repository - On the GitHub repository, click the main button in the upper left - type "gh-pages" and create a new branch - go to your repositories settings -> Pages - for Source, choose "Deploy from a branch" - for Branch, choose "gh-pages" - for Select folder, choose "root" - optionally choose a custom URL and hit save - in each PR there should be a preview for the new site - for every push to main (from a PR), the site will be updated 14) Finalize - remove all the above instructions and raise any issues in this template's repository if you have any suggestion or found any errors in this template! - replace all instances of "zenodo_DOI" in this repository with your new Zenodo DOI. - if your Zenodo link is https://doi.org/10.5281/zenodo.15863068,, your DOI is just 15863068 - make sure to use the DOI from the Cite all versions? portion of your Zenodo page. - if you want, please submit a PR to this repository to add your package to this list at the top of this README to showcase it!

samplepackagename

Short description of your package.