self-contained-runnable-python-package-template
release-please
Our great sponsors
| self-contained-runnable-python-package-template | release-please | |
|---|---|---|
| 3 | 46 | |
| 18 | 4,125 | |
| - | 7.6% | |
| 0.0 | 8.6 | |
| over 1 year ago | 6 days ago | |
| Python | TypeScript | |
| GNU General Public License v3.0 only | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
self-contained-runnable-python-package-template
-
Underappreciated Challenges with Python Packaging
The approach I prefer is to not mess with setuptools etc at all in the first place, and simply make a nice executable package.
e.g. https://github.com/tpapastylianou/self-contained-runnable-py...
-
How to create a Python package in 2022
The title should be: How to create a "Python DISTRIBUTION package".
The term "python package" means something entirely different (or at the very least is ambiguous in a pypi/distribution context).
To add to the confusion, creating a totally normal, runnable python package in a manner that makes it completely self-contained such that it can be "distributed" in a standalone manner, while still being a totally normal boring python package, is also totally possible (if not preferred, in my view).
Shameless plug: https://github.com/tpapastylianou/self-contained-runnable-py...
-
Show HN: Hatch 1.0.0 – Modern, extensible Python project management
Shameless plug: I use my own template, which organises things as runnable projects.
https://github.com/tpapastylianou/self-contained-runnable-py...
It serves my purposes very well (which is creating projects that represent standalone experiments).
Sharing in case someone else here finds it useful.
More recently I've modified this a bit to also generate nice html reports straight from the __main__.py file, independently of the underlying python code, and use this as lab books (where each lab book contains a single analysis and its report). I'll upload this template separately when I find the time.
release-please
-
How to write GIT commit messages
Conventional Commits
-
How to Improve Development Experience of your React Project
We've covered everything about writing well-formatted and structured code without worrying too much about it anymore. The only part we haven't explored yet is linting commit messages. Commitlint will help us here. It allows you to configure any rules you want for the commit message, but we're going to use the Conventional Commits specification, one of the most popular conventions you'll find.
- Release Please
-
TypeScript Boilerplate
Commit Management with Conventional Commits: The Conventional Commits methodology is adopted to maintain a clear and structured record of changes with the help of commitlint.
-
A Gitlab Review Bot Assistant
Validate if the commit titles adhere to the Conventional Commits Specification in Merge requests.
-
Ask HN: Should commit summaries describe the change, or the intent?
Check out https://www.conventionalcommits.org
-
Announcing release-plz v0.3.0
FYI there is already a popular tool that does just this with a very similar name: https://github.com/googleapis/release-please
-
A clean Git history with Git Rebase and Conventional Commits
The feature commit should have a clear defined message - Don't re-invent here - There exists a fairly used and accepted convention called Conventional Commits, so we are going to use that.
-
Add a semver tag to release and auto increment it based on last tag
Check out https://github.com/googleapis/release-please
What are some alternatives?
hatch - Modern, extensible Python project management
semantic-pull-requests - :robot: Let the robots take care of the semantic versioning
Nuitka - Nuitka is a Python compiler written in Python. It's fully compatible with Python 2.6, 2.7, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.10, and 3.11. You feed it your Python app, it does a lot of clever things, and spits out an executable or extension module.
gitflow - Git extensions to provide high-level repository operations for Vincent Driessen's branching model.
Poetry - Python packaging and dependency management made easy
cz-cli - The commitizen command line utility. #BlackLivesMatter
pip-audit - Audits Python environments, requirements files and dependency trees for known security vulnerabilities, and can automatically fix them
commitizen - Create committing rules for projects :rocket: auto bump versions :arrow_up: and auto changelog generation :open_file_folder:
tox-poetry-installer - A plugin for Tox that lets you install test environment dependencies from the Poetry lockfile
conventional-changelog - Generate changelogs and release notes from a project's commit messages and metadata.
semantic-release - :package::rocket: Fully automated version management and package publishing
semantic-pull-requests