roadmap
release-please
| roadmap | release-please | |
|---|---|---|
| 4 | 47 | |
| 2 | 4,267 | |
| - | 5.9% | |
| 1.8 | 8.5 | |
| over 2 years ago | 8 days ago | |
| TypeScript | ||
| - | 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.
roadmap
-
Python Packaging, One Year Later: A Look Back at 2023 in Python Packaging
I wish Poetry were PEP-621 compliant though. [1]
Currently, it uses a proprietary configuration group (or "tool section", as they seem to call it in `pyproject.toml` speech).
[1]: https://github.com/python-poetry/roadmap/issues/3
-
How to improve Python packaging, or why 14 tools are at least 12 too many
https://github.com/python-poetry/roadmap/issues/3
-
What are people using to organize virtual environments these days?
Sorry for the late reply. I cannot recall the exact source, but I found this issue in the poetry repo: https://github.com/python-poetry/roadmap/issues/3. IIUC, they are trying to make poetry compliant with PEP621 but the PR was not merged yet? Will update the original comment to add this nuance.
-
How to create a Python package in 2022
I believe that Poetry does conform to PEP 518 (i.e. it specifies `[build-system]requires`), but not to the `dependencies` part of PEP 621 [1]. There are plans for this in the future though [2].
[1] https://peps.python.org/pep-0621/
[2] https://github.com/python-poetry/roadmap/issues/3
release-please
-
Git commit helper: add emojis to your commits
Using Conventional Commits ⭐ as a standard for your commit messages, makes Semantic Versioning 🔖 as easy as can be, with tools like Conventional Changelog 📄 Standard Version 🔖 and Semantic Release 📦🚀
-
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.
What are some alternatives?
tox-poetry-installer - A plugin for Tox that lets you install test environment dependencies from the Poetry lockfile
semantic-pull-requests - :robot: Let the robots take care of the semantic versioning
sigstore-python - A Sigstore client for Python
gitflow - Git extensions to provide high-level repository operations for Vincent Driessen's branching model.
publishing-python-packages - Examples and exercises for Publishing Python Packages from Manning Books 🐍 📦 ⬆️
cz-cli - The commitizen command line utility. #BlackLivesMatter
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.
commitizen - Create committing rules for projects :rocket: auto bump versions :arrow_up: and auto changelog generation :open_file_folder:
pigar - :coffee: A tool to generate requirements.txt for Python project, and more than that. (IT IS NOT A PACKAGE MANAGEMENT TOOL)
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