An extremely fast Python linter and code formatter, written in Rust.| docs.astral.sh
Settings| docs.astral.sh
This PEP proposes adding the ability to mark a particular file download on a simple repository as “yanked”. Yanking a file allows authors to effectively delete a file, without breaking things for people who have pinned to exactly a specific version.| Python Enhancement Proposals (PEPs)
Commands You’ve already learned how to use the command-line interface to do some things. This chapter documents all the available commands. To get help from the command-line, simply call poetry to see the complete list of commands, then --help combined with any of those can give you more information. Global Options --verbose (-v|vv|vvv): Increase the verbosity of messages: “-v” for normal output, “-vv” for more verbose output and “-vvv” for debug. --help (-h) : Display help info...| python-poetry.org
Dependency specification Dependencies for a project can be specified in various forms, which depend on the type of the dependency and on the optional constraints that might be needed for it to be installed. Version constraints Caret requirements Caret requirements allow SemVer compatible updates to a specified version. An update is allowed if the new version number does not modify the left-most non-zero digit in the major, minor, patch grouping. For instance, if we previously ran poetry add r...| python-poetry.org
ENOSUCHBLOG| blog.yossarian.net
The pyproject.toml file In package mode, the only required fields are name and version (either in the project section or in the tool.poetry section). Other fields are optional. In non-package mode, the name and version fields are required if using the project section. Note Run poetry check to print warnings about deprecated fields. The project section The project section of the pyproject.toml file according to the specification of the PyPA. name The name of the package. Always required when t...| python-poetry.org
The pip team has released pip 24.1b1 which contains a lot of significant improvements and bug fixes. I’d like to highlight a major change in this blog post: the removal of support for “legacy” versions and dependency specification, or as I like to call it, nonsensical versions and dependencies. We’re releasing this as a beta to get feedback from the community on how this change affects their workflows. Nonsensical versions and dependencies For a bunch of historical reasons, pip has al...| pradyunsg.me
PEP 691 defined a JSON form for the “Simple Repository API”. This allowed clients to more easily query the data that was previously only available in HTML, as defined in PEP 503.| Python Enhancement Proposals (PEPs)
uv is an extremely fast Python package installer and resolver, designed as a drop-in alternative to pip and pip-tools.| astral.sh
Over the last few years, many open-source Python projects that I work on have switched to CalVer.| jacobtomlinson.dev
This PEP specifies the language used to describe dependencies for packages. It draws a border at the edge of describing a single dependency - the different sorts of dependencies and when they should be installed is a higher level problem. The intent is ...| Python Enhancement Proposals (PEPs)
This PEP specifies how to write a project’s core metadata in a pyproject.toml file for packaging-related tools to consume.| Python Enhancement Proposals (PEPs)
Every now and then, at work, I find myself discussing git worfklows, commit messages, branching, releasing, versioning, changelogs etc. Since my opinion has remained fairly consistent for the past few years, I found myself repeating the same points a lot, so I wrote it down. This page is the resulting compilation of my opinions on the software development lifecycle (SDLC), without workplace-specific tangeants. The article is broken down into ideas + recommendations, with recommendations in bold.| jiby.tech
Black 22.10.0 removes runtime support for Python 3.6, fixes a major fmt: off/on bug, and other QOL improvements.| ichard26.github.io