python-blueprint VS cookiecutter-pypackage

I used https://github.com/johnthagen/python-blueprint to build https://github.com/DaveCoDev/not-again-ai. It uses poetry to manage dependencies, sets up automatic linting, testing, and type checking with nox and gets it running with GitHub Actions. It is continually being updated and stays up to date modern Python tooling (ruff, nox, poetry, etc). Not sure why the comments are being so discouraging, but regardless if you are looking to publish a polished library, its super helpful to have these things setup for you.

- cookiecutter-pypackage

Just a quick note - your link leads to the cookiecutter tool repo whereas OP needs a python templates like: https://github.com/audreyfeldroy/cookiecutter-pypackage

The base template is here: https://github.com/audreyfeldroy/cookiecutter-pypackage

I'm experiencing some trouble with running pytest and tox. With this project I mainly wanted to learn how to setup a good repository style and learn to publish my package. I used Cookiecutter PyPackage as template.

Take a look at the makefile in this python package cookie cutter template: https://github.com/audreyfeldroy/cookiecutter-pypackage. I’ve started using this for pretty much all my python projects because I like being able to run ‘make clean’ to clean up any pyc files or build artifacts that I don’t want to accidentally commit to version control.

For additional exploration... check out cookiecutter and cookiecutter-pypackage. Not so much a guide as much as a tool, but in short, cookiecutter lets you jumpstart new projects and populate directory structure with one command. Cookiecutter-pypackage is a template that does a pretty good job of following best practices. Though, it does a lot, so, prepare to be a little overwhelmed wondering why it includes so many files. But it may give you an idea of some things you may want to do when creating your own projects.