Announcing Poetry 1.7.0
The Poetry team is pleased to announce the immediate availability of Poetry 1.7.0.
If you have a previous version of Poetry installed via
getting Poetry 1.7.0 is as easy as:
$ pipx upgrade poetry
If you used the official installer, you can run:
$ poetry self update
Official support for Python 3.12 #
Even though Poetry 1.6 probably works well with Python 3.12, we did some fine-tuning to make the user experience more consistent:
Python 3.12 is the first Python version that does not implicitly includes
in newly created virtual environments. In order to align Poetry with other tools,
we now also do not implicitly include
setuptools in newly created Python 3.12
environments. In this context, we have also changed that
wheel is not implicitly
included anymore (for all Python versions). Further,
will now be removed when running
poetry install --sync if they are not required
by the project. If you rely on
please make it an explicit dependency in your
Further, some deprecation warnings were addressed and
Programming Language :: Python :: 3.12 classifier will be set automatically now
if Python 3.12 is in your project’s supported Python versions.
Improved handling of dependencies with extras during dependency resolution #
extra marker is quite special. Whereas other markers can only have one value for
a specific environment,
extra can have multiple values at the same time.
For example, a marker like
sys_platform == "win32" and sys_platform == "linux"
can never be satisfied because
sys_platform can only be either
(not both). By contrast, a marker like
extra == "a" and extra == "b"
can be satisfied if both extras are requested.
Poetry can now handle this peculiarity and ignore dependencies that are only relevant for inactive extras.
Fix longstanding race condition in
poetry install #
Intermittent failures of
poetry install with error messages like
Backend 'setuptools.build_meta:__legacy__' is not available. should now be resolved
by fixing a race condition when installing multiple source distributions with
overlapping build requirements in parallel.
Upcoming Changes #
poetry-plugin-export from the default installation #
Prior Poetry 1.2,
export had been a built-in command. With Poetry 1.2, the
command was outsourced into
poetry-plugin-export. To avoid a breaking change,
we decided to install
poetry-plugin-export per default. However, this resulted
in a cyclic dependency between
poetry-plugin-export, which causes
issues for some third-party tools and results in an increased maintenance effort
for the Poetry team.
Therefore, we are planning to not install
per default in a future version of Poetry.
To ensure that as many users as possible are informed about this upcoming change,
a warning, which can be deactivated, will be shown when running
In order to make your automation forward-compatible, just install
explicitly (even though it is already installed per default for now).
- Add official support for Python 3.12 (#7803, #8544).
- Print a future warning that
poetry-plugin-exportwill not be installed by default anymore (#8562).
poetry-installpre-commit hook (#8327).
- Print a warning when overwriting files from another package at installation (#8386).
- Print a warning if the current project cannot be installed (#8369).
- Report more details on build backend exceptions (#8464).
- Set Poetry as
user-agentfor all HTTP requests (#8394).
- Do not install
setuptoolsper default in Python 3.12 (#7803).
- Do not install
wheelper default (#7803).
poetry install --syncif they are not required by the project (#8600).
- Improve error message about PEP-517 support (#8463).
- Read the
descriptionfield when extracting metadata from
- Fix an issue where dependencies of inactive extras were locked and installed (#8399).
- Fix an issue where build requirements were not installed due to a race condition in the artifact cache (#8517).
- Fix an issue where packages included in the system site packages were installed even though
virtualenvs.options.system-site-packageswas set (#8359).
- Fix an issue where git dependencies' submodules with relative URLs were handled incorrectly (#8020).
- Fix an issue where a failed installation of build dependencies was not noticed directly (#8479).
- Fix an issue where
poetry shelldid not work completely with
- Fix an issue where a confusing error messages was displayed when running
poetry config pypi-token.pypiwithout a value (#8502).
- Fix an issue where a cryptic error message is printed if there is no metadata entry in the lockfile (#8523).
- Fix an issue with the encoding with special characters in the virtualenv’s path (#8565).
- Fix an issue where the connection pool size was not adjusted to the number of workers (#8559).
- Improve the wording regarding a project’s supported Python range (#8423).
pipxthe preferred (first mentioned) installation method (#8090).
- Add a warning about
poetry selfon Windows (#8090).
- Fix example for
poetry addwith a git dependency (#8438).
- Add information about auto-included files in wheels and sdist (#8555).
- Fix documentation of the
POETRY_REPOSITORIES_variables docs (#8492).
- Add support for creating packages dynamically in the build script (#629).
- Improve marker logic for
- Update list of supported licenses (#635, #646).
- Fix an issue where projects with extension modules were not installed in editable mode (#633).
- Fix an issue where the wrong or no
libfolder was added to the wheel (#634).