modernpackage 0.0.4

Package configuration example using bleeding edge toolset.

modernpackage

This is a boilerplate with bleeding edge linters for a new python package, just run:

• git clone [e-mail]:albertas/modernpackage.git <your-package-name>
• cd <your-package-name>
• make init <your-package-name> - to start your modern package.

Development

Commonly used commands for package development:

• make check - run unit tests and linters.
• make fix - format code and fix detected fixable issues.
• make publish - publishes current package version to pypi.org.
• make compile - bump and freeze dependency versions in requirements*.txt files
• make sync - upgrade installed dependencies in Virtual Environment (executed after make compile)

Toolset

This package uses these cutting edge tools:

• ruff - for linting and code formatting
• mypy - for type checking
• pip-audit - for known vulnerability detection in dependencies
• deadcode - for unused code detection
• pytest - for collecting and running unit tests
• coverage - for code coverage by unit tests
• hatch - for publishing package to pypi.org
• uv - for Python virtual environment and dependency management
• pyproject.toml - configuration file for all tools
• Makefile - aliases for commonly used command line commands

Feature requests:

• make a cli command: this package should be installable. Ideally this flow should work:
  • pip install modernpackage
  • modernpackage mynewpackage
  • cd mynewpackage && make check && make publish
• Enable github and gitlab pipeline files to run make check in the pipeline.
• Add pre-commit hooks with all the tools enabled.
• codspeed.io could be considered for Continuous integration pipeline