https://python-poetry.org/Recent content on Poetry - Python dependency management and packaging made easyHugoen-usSun, 18 Jan 2026 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-2.3.0/Sun, 18 Jan 2026 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-2.3.0/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>2.3.0</strong>.</p>https://python-poetry.org/blog/announcing-poetry-2.2.0/Sun, 14 Sep 2025 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-2.2.0/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>2.2.0</strong>.</p>https://python-poetry.org/blog/announcing-poetry-2.1.0/Sat, 15 Feb 2025 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-2.1.0/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>2.1.0</strong>.</p>https://python-poetry.org/blog/announcing-poetry-2.0.1/Sat, 11 Jan 2025 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-2.0.1/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>2.0.1</strong>.</p>https://python-poetry.org/blog/announcing-poetry-2.0.0/Sun, 05 Jan 2025 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-2.0.0/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>2.0.0</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.8.0/Sun, 25 Feb 2024 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.8.0/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.8.0</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.7.0/Fri, 03 Nov 2023 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.7.0/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.7.0</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.6.0/Sun, 20 Aug 2023 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.6.0/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.6.0</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.5.0/Fri, 19 May 2023 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.5.0/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.5.0</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.4.0/Mon, 27 Feb 2023 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.4.0/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.4.0</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.3.0/Fri, 09 Dec 2022 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.3.0/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.3.0</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.2.2/Mon, 10 Oct 2022 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.2.2/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.2.2</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.2.1/Fri, 16 Sep 2022 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.2.1/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.2.1</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.2.0/Wed, 31 Aug 2022 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.2.0/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.2.0</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.2.0rc2/Fri, 26 Aug 2022 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.2.0rc2/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.2.0rc2</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.2.0rc1/Tue, 23 Aug 2022 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.2.0rc1/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.2.0rc1</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.1.15/Mon, 22 Aug 2022 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.1.15/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.1.15</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.1.14/Fri, 08 Jul 2022 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.1.14/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.1.14</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.2.0b1/Thu, 17 Mar 2022 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.2.0b1/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.2.0b1</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.1.13/Thu, 10 Feb 2022 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.1.13/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.1.13</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.1.12/Sat, 27 Nov 2021 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.1.12/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.1.12</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.1.11/Mon, 04 Oct 2021 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.1.11/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.1.11</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.1.10/Tue, 21 Sep 2021 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.1.10/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.1.10</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.1.9/Sat, 18 Sep 2021 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.1.9/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.1.9</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.1.8/Thu, 19 Aug 2021 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.1.8/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.1.8</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.2.0a2/Sun, 01 Aug 2021 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.2.0a2/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.2.0a2</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.1.7/Fri, 25 Jun 2021 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.1.7/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.1.7</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.2.0a1/Fri, 21 May 2021 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.2.0a1/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.2.0a1</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.1.6/Wed, 14 Apr 2021 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.1.6/<p>The Poetry team is pleased to announce the immediate availability of Poetry <strong>1.1.6</strong>.</p>https://python-poetry.org/blog/announcing-poetry-1.1.5/Wed, 03 Mar 2021 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.1.5/<p>The Poetry team is pleased to announce the immediate availability of Poetry 1.1.5.</p>https://python-poetry.org/blog/announcing-poetry-1.1.4/Fri, 23 Oct 2020 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.1.4/<p>The Poetry team is pleased to announce the immediate availability of Poetry 1.1.4.</p>https://python-poetry.org/blog/announcing-poetry-1.1.3/Wed, 14 Oct 2020 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.1.3/<p>The Poetry team is pleased to announce the immediate availability of Poetry 1.1.3.</p>https://python-poetry.org/blog/announcing-poetry-1.1.2/Tue, 06 Oct 2020 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.1.2/<p>The Poetry team is pleased to announce the immediate availability of Poetry 1.1.2.</p>https://python-poetry.org/blog/announcing-poetry-1.1.1/Mon, 05 Oct 2020 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.1.1/<p>The Poetry team is pleased to announce the immediate availability of Poetry 1.1.1.</p>https://python-poetry.org/blog/announcing-poetry-1.1.0/Thu, 01 Oct 2020 00:00:00 +0000https://python-poetry.org/blog/announcing-poetry-1.1.0/<p>The Poetry team is pleased to announce the immediate availability of Poetry 1.1.0.</p>https://python-poetry.org/blog/announcing-poetry-1.0.10/Tue, 21 Jul 2020 10:12:35 +0000https://python-poetry.org/blog/announcing-poetry-1.0.10/<p>The Poetry team is pleased to announce the immediate availability of Poetry 1.0.10.</p>https://python-poetry.org/blog/announcing-poetry-1.0.9/Tue, 09 Jun 2020 10:12:35 +0000https://python-poetry.org/blog/announcing-poetry-1.0.9/<p>The Poetry team is pleased to announce the immediate availability of Poetry 1.0.9.</p>https://python-poetry.org/blog/announcing-poetry-1.0.8/Fri, 05 Jun 2020 12:12:35 +0000https://python-poetry.org/blog/announcing-poetry-1.0.8/<p>The Poetry team is pleased to announce the immediate availability of Poetry 1.0.8.</p>https://python-poetry.org/blog/announcing-poetry-1.0.7/Fri, 05 Jun 2020 11:12:35 +0000https://python-poetry.org/blog/announcing-poetry-1.0.7/<p>The Poetry team is pleased to announce the immediate availability of Poetry 1.0.7.</p>https://python-poetry.org/blog/announcing-poetry-1.0.6/Fri, 05 Jun 2020 10:12:35 +0000https://python-poetry.org/blog/announcing-poetry-1.0.6/<p>The Poetry team is pleased to announce the immediate availability of Poetry 1.0.6.</p>https://python-poetry.org/blog/announcing-poetry-1.0.5/Sat, 29 Feb 2020 10:12:35 +0000https://python-poetry.org/blog/announcing-poetry-1.0.5/<p>The Poetry team is pleased to announce the immediate availability of Poetry 1.0.5.</p>https://python-poetry.org/blog/announcing-poetry-1.0.4/Fri, 28 Feb 2020 10:12:35 +0000https://python-poetry.org/blog/announcing-poetry-1.0.4/<p>The Poetry team is pleased to announce the immediate availability of Poetry 1.0.4.</p>https://python-poetry.org/blog/announcing-poetry-1.0.3/Fri, 31 Jan 2020 10:12:35 +0000https://python-poetry.org/blog/announcing-poetry-1.0.3/<p>The Poetry team is pleased to announce the immediate availability of Poetry 1.0.3.</p>https://python-poetry.org/blog/announcing-poetry-1.0.2/Fri, 10 Jan 2020 11:12:35 +0000https://python-poetry.org/blog/announcing-poetry-1.0.2/<p>The Poetry team is pleased to announce the immediate availability of Poetry 1.0.2.</p>https://python-poetry.org/blog/announcing-poetry-1.0.1/Fri, 10 Jan 2020 10:12:35 +0000https://python-poetry.org/blog/announcing-poetry-1.0.1/<p>The Poetry team is pleased to announce the immediate availability of Poetry 1.0.1.</p>https://python-poetry.org/blog/announcing-poetry-1.0.0/Thu, 12 Dec 2019 10:12:35 +0000https://python-poetry.org/blog/announcing-poetry-1.0.0/<p>The Poetry team is pleased to announce the immediate availability of Poetry 1.0.0.</p>https://python-poetry.org/blog/poetry-0.12.17-is-out/Wed, 03 Jul 2019 10:12:35 +0000https://python-poetry.org/blog/poetry-0.12.17-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed dependency resolution with circular dependencies.</li> <li>Fixed encoding errors when reading files on Windows. (Thanks to <a href="https://github.com/vlcinsky">@vlcinsky</a>)</li> <li>Fixed unclear errors when executing commands in virtual environments. (Thanks to <a href="https://github.com/Imaclean74">@Imaclean74</a>)</li> <li>Fixed handling of <code>.venv</code> when it&rsquo;s not a directory. (Thanks to <a href="https://github.com/mpanarin">@mpanarin</a>)</li> </ul>https://python-poetry.org/blog/poetry-0.12.16-is-out/Mon, 13 May 2019 10:12:35 +0000https://python-poetry.org/blog/poetry-0.12.16-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed packages with no hashes retrieval for legacy repositories.</li> <li>Fixed multiple constraints for dev dependencies.</li> <li>Fixed dependency resolution failing on badly formed package versions instead of skipping.</li> <li>Fixed permissions of built wheels.</li> </ul>https://python-poetry.org/blog/poetry-0.12.15-is-out/Fri, 03 May 2019 10:12:35 +0000https://python-poetry.org/blog/poetry-0.12.15-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed an <code>AttributeError</code> in the editable builder.</li> <li>Fixed resolution of packages with only Python 3 wheels and sdist when resolving for legacy repositories.</li> <li>Fixed non-sha256 hashes retrieval for legacy repositories.</li> </ul>https://python-poetry.org/blog/poetry-0.12.14-is-out/Fri, 26 Apr 2019 11:12:35 +0000https://python-poetry.org/blog/poetry-0.12.14-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed root package installation for pure Python packages.</li> </ul>https://python-poetry.org/blog/poetry-0.12.13-is-out/Fri, 26 Apr 2019 10:12:35 +0000https://python-poetry.org/blog/poetry-0.12.13-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed root package installation with <code>pip&gt;=19.0</code>.</li> <li>Fixed packages not being removed after using the <code>remove</code> command.</li> </ul>https://python-poetry.org/blog/poetry-0.12.12-is-out/Thu, 11 Apr 2019 10:12:35 +0000https://python-poetry.org/blog/poetry-0.12.12-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fix lock idempotency.</li> <li>Fix markers evaluation for <code>python_version</code> with precision &lt; 3.</li> <li>Fix permissions of the <code>dist-info</code> files.</li> <li>Fix <code>prepare_metadata_for_build_wheel()</code> missing in the build backend.</li> <li>Fix metadata inconsistency between wheels and sdists.</li> <li>Fix parsing of <code>platform_release</code> markers.</li> <li>Fix metadata information when the project has git dependencies.</li> <li>Fix error reporting when publishing fails.</li> <li>Fix retrieval of <code>extras_require</code> in some <code>setup.py</code> files. (Thanks to <a href="https://github.com/asodeur">@asodeur</a>)</li> <li>Fix wheel compression when building. (Thanks to <a href="https://github.com/ccosby">@ccosby</a>)</li> <li>Improve retrieval of information for packages with two python specific wheels.</li> <li>Fix request authentication when credentials are included in URLs. (Thanks to <a href="https://github.com/connorbrinton">@connorbrinton</a>)</li> </ul>https://python-poetry.org/blog/poetry-0.12.11-is-out/Sun, 13 Jan 2019 10:12:35 +0000https://python-poetry.org/blog/poetry-0.12.11-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed the way packages information are retrieved for legacy repositories.</li> <li>Fixed an error when adding packages with invalid versions.</li> <li>Fixed an error when resolving directory dependencies with no sub dependencies.</li> <li>Fixed an error when locking packages with no description.</li> <li>Fixed path resolution for transitive file dependencies.</li> <li>Fixed multiple constraints handling for the root package.</li> <li>Fixed exclude functionality on case sensitive systems.</li> </ul>https://python-poetry.org/blog/poetry-0.12.10-is-out/Thu, 22 Nov 2018 10:12:35 +0000https://python-poetry.org/blog/poetry-0.12.10-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed <code>run</code> not executing scripts.</li> <li>Fixed environment detection.</li> <li>Fixed handling of authentication for legacy repositories.</li> </ul>https://python-poetry.org/blog/poetry-0.12.9-is-out/Mon, 19 Nov 2018 10:12:35 +0000https://python-poetry.org/blog/poetry-0.12.9-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed executables from outside the virtualenv not being accessible.</li> <li>Fixed a possible error when building distributions with the <code>exclude</code> option.</li> <li>Fixed the <code>run</code> command for namespaced packages.</li> <li>Fixed errors for virtualenvs with spaces in their path.</li> <li>Fixed prerelease versions being selected with the <code>add</code> command.</li> </ul>https://python-poetry.org/blog/poetry-0.12.8-is-out/Tue, 13 Nov 2018 10:12:35 +0000https://python-poetry.org/blog/poetry-0.12.8-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed permission errors when adding/removing git dependencies on Windows.</li> <li>Fixed <code>Pool</code> not raising an exception when no package could be found.</li> <li>Fixed reading <code>bz2</code> source distribution.</li> <li>Fixed handling of arbitrary equals in <code>InstalledRepository</code>.</li> </ul>https://python-poetry.org/blog/poetry-0.12.7-is-out/Thu, 08 Nov 2018 10:12:35 +0000https://python-poetry.org/blog/poetry-0.12.7-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed reading of some <code>setup.py</code> files.</li> <li>Fixed a <code>KeyError</code> when getting information for packages which require reading setup files.</li> <li>Fixed the building of wheels with C extensions and an <code>src</code> layout.</li> <li>Fixed extras being selected when resolving dependencies even when not required.</li> <li>Fixed performance issues when packaging projects if a lot of files were excluded.</li> <li>Fixed installation of files.</li> <li>Fixed extras not being retrieved for legacy repositories.</li> <li>Fixed invalid transitive constraints raising an error for legacy repositories.</li> </ul>https://python-poetry.org/blog/poetry-0.12.6-is-out/Mon, 05 Nov 2018 10:12:35 +0000https://python-poetry.org/blog/poetry-0.12.6-is-out/<p>Bugfix release.</p> <h2 id="changes">Changes</h2> <ul> <li>Poetry will now try to read, without executing, setup files (<code>setup.py</code> and/or <code>setup.cfg</code>) if the <code>egg_info</code> command fails when resolving dependencies.</li> </ul> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed installation of directory dependencies.</li> <li>Fixed handling of dependencies with a <code>not in</code> marker operator.</li> <li>Fixed support for VCS dependencies.</li> <li>Fixed the <code>exclude</code> property not being respected if no VCS was available.</li> </ul>https://python-poetry.org/blog/poetry-0.12.5-is-out/Fri, 26 Oct 2018 10:12:35 +0000https://python-poetry.org/blog/poetry-0.12.5-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed installation of Poetry git dependencies with a build system.</li> <li>Fixed possible errors when resolving dependencies for specific packages.</li> <li>Fixed handling of Python versions compatibility.</li> <li>Fixed the dependency resolver picking up unnecessary dependencies due to not using the <code>python_full_version</code> marker.</li> <li>Fixed the <code>Python-Requires</code> metadata being invalid for single Python versions.</li> </ul>https://python-poetry.org/blog/poetry-0.12.4-is-out/Sun, 21 Oct 2018 10:12:35 +0000https://python-poetry.org/blog/poetry-0.12.4-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed possible error on some combinations of markers.</li> <li>Fixed venv detection so that it only uses <code>VIRTUAL_ENV</code> to detect activated virtualenvs.</li> </ul>https://python-poetry.org/blog/poetry-0.12.3-is-out/Thu, 18 Oct 2018 10:12:35 +0000https://python-poetry.org/blog/poetry-0.12.3-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed the <code>--no-dev</code> option in <code>install</code> not working properly.</li> <li>Fixed prereleases being selected even if another constraint conflicted with them.</li> <li>Fixed an error when installing current package in development mode if the generated <code>setup.py</code> had special characters.</li> <li>Fixed an error in <code>install</code> for applications not following a known structure.</li> <li>Fixed an error when trying to retrieve the current environment.</li> <li>Fixed <code>debug:info</code> not showing the current project&rsquo;s virtualenv.</li> </ul>https://python-poetry.org/blog/poetry-0.12.2-is-out/Wed, 17 Oct 2018 12:12:35 +0000https://python-poetry.org/blog/poetry-0.12.2-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed an error when installing from private repositories.</li> <li>Fixed an error when trying to move the lock file on Python 2.7.</li> </ul>https://python-poetry.org/blog/poetry-0.12.1-is-out/Wed, 17 Oct 2018 11:12:35 +0000https://python-poetry.org/blog/poetry-0.12.1-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed an error when a license was not specified.</li> </ul>https://python-poetry.org/blog/poetry-0.12.0-is-out/Wed, 17 Oct 2018 10:12:35 +0000https://python-poetry.org/blog/poetry-0.12.0-is-out/<p>This new version brings a brand new official installer, dependency resolver improvements, virtualenv management and detection improvements and many more small improvements and bug fixes.</p> <aside class="note"> <p>There are some breaking changes in this release, especially in the way Poetry resolves dependencies, so before upgrading you should read the following release notes</p> </aside> <h2 id="new-features">New features</h2> <h3 id="brand-new-installer">Brand new installer</h3> <p>A lot of issues on the official <a href="https://github.com/python-poetry/poetry/issues">issue tracker</a> were related to the installation of Poetry: bugs, permission errors and overall confusion about the way Poetry should be installed.</p>https://python-poetry.org/blog/poetry-0.11.5-is-out/Tue, 04 Sep 2018 10:12:35 +0000https://python-poetry.org/blog/poetry-0.11.5-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed a recursion error with circular dependencies.</li> <li>Fixed the <code>config</code> command setting incorrect values for paths.</li> <li>Fixed an <code>OSError</code> on Python &gt;= 3.5 for <code>git</code> dependencies with recursive symlinks.</li> <li>Fixed the possible deletion of system paths by <code>cache:clear</code>.</li> <li>Fixed a performance issue when parsing the lock file by upgrading <code>tomlkit</code>.</li> </ul>https://python-poetry.org/blog/poetry-0.11.4-is-out/Mon, 30 Jul 2018 10:12:35 +0000https://python-poetry.org/blog/poetry-0.11.4-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed wrong wheel being selected when resolving dependencies.</li> <li>Fixed an error when publishing.</li> <li>Fixed an error when building wheels with the <code>packages</code> property set.</li> <li>Fixed single value display in <code>config</code> command.</li> </ul>https://python-poetry.org/blog/poetry-0.11.3-is-out/Thu, 26 Jul 2018 10:12:35 +0000https://python-poetry.org/blog/poetry-0.11.3-is-out/<p>Bugfix release.</p> <h2 id="changes">Changes</h2> <ul> <li>Poetry now only uses <a href="https://github.com/sdispater/tomlkit">TOML Kit</a> for TOML files manipulation.</li> <li>Improved dependency resolution debug information.</li> </ul> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed missing dependency information for some packages.</li> <li>Fixed handling of single versions when packaging.</li> <li>Fixed dependency information retrieval from <code>.zip</code> and <code>.bz2</code> archives.</li> <li>Fixed searching for and installing packages from private repositories with authentication. (Thanks to <a href="https://github.com/MarcDufresne">@MarcDufresne</a>)</li> <li>Fixed a potential error when checking the <code>pyproject.toml</code> validity. (Thanks to <a href="https://github.com/ojii">@ojii</a>)</li> <li>Fixed the lock file not tracking the <code>extras</code> information from <code>pyproject.toml</code>. (Thanks to <a href="https://github.com/cauebs">@cauebs</a>)</li> <li>Fixed missing trailing slash in the Simple API urls for private repositories. (Thanks to <a href="https://github.com/bradsbrown">@bradsbrown</a>)</li> </ul>https://python-poetry.org/blog/poetry-0.11.2-is-out/Tue, 03 Jul 2018 10:12:35 +0000https://python-poetry.org/blog/poetry-0.11.2-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed missing dependencies when resolving in some cases.</li> <li>Fixed path dependencies not working in <code>dev-dependencies</code>.</li> <li>Fixed license validation in <code>init</code>. (Thanks to <a href="https://github.com/cauebs">@cauebs</a>)</li> </ul>https://python-poetry.org/blog/poetry-0.11.1-is-out/Fri, 29 Jun 2018 10:12:35 +0000https://python-poetry.org/blog/poetry-0.11.1-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed an error when locking dependencies on Python 2.7.</li> </ul>https://python-poetry.org/blog/poetry-0.11.0-is-out/Thu, 28 Jun 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.11.0-is-out/<p>This version brings a new <code>shell</code> command, dependency resolver improvements and improves stability.</p> <h2 id="new-features">New Features</h2> <h3 id="new-shell-command">New <code>shell</code> command</h3> <p>The newly introduced <code>shell</code> command helps you in your development workflow by placing you in the proper project environment. This way you can omit the <code>poetry run</code> command.</p> <p>Note that this command is a usability improvement and, as such, is completely optional and any current workflow using the <code>poetry run</code> command will still work and is still the recommended way of interacting with a Poetry project.</p>https://python-poetry.org/blog/poetry-0.10.3-is-out/Mon, 04 Jun 2018 10:12:35 +0000https://python-poetry.org/blog/poetry-0.10.3-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed <code>self:update</code> command on Windows.</li> <li>Fixed <code>self:update</code> not picking up new versions.</li> <li>Fixed a <code>RuntimeError</code> on Python 3.7.</li> <li>Fixed bad version number being picked with private repositories.</li> <li>Fixed handling of duplicate dependencies with same constraint.</li> <li>Fixed installation from custom repositories.</li> <li>Fixed setting an explicit version in <code>version</code> command.</li> <li>Fixed parsing of wildcards version constraints.</li> </ul>https://python-poetry.org/blog/poetry-0.10.2-is-out/Thu, 31 May 2018 10:12:35 +0000https://python-poetry.org/blog/poetry-0.10.2-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed handling of <code>in</code> environment markers with commas.</li> <li>Fixed a <code>UnicodeDecodeError</code> when an error occurs in venv.</li> <li>Fixed Python requirements not properly set when resolving dependencies.</li> <li>Fixed terminal coloring being activated even if not supported.</li> <li>Fixed wrong executable being picked up on Windows in <code>poetry run</code>.</li> <li>Fixed error when listing distribution links for private repositories.</li> <li>Fixed handling of PEP 440 <code>~=</code> version constraint.</li> </ul>https://python-poetry.org/blog/poetry-0.10.1-is-out/Mon, 28 May 2018 10:12:35 +0000https://python-poetry.org/blog/poetry-0.10.1-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed packages not found for prerelease version constraints when resolving dependencies.</li> <li>Fixed <code>init</code> and <code>add</code> commands.</li> </ul>https://python-poetry.org/blog/poetry-0.10.0-is-out/Mon, 28 May 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.10.0-is-out/<p>This version brings a brand new dependency resolver which is more consistent, reliable and faster.</p> <h2 id="new-features">New Features</h2> <h3 id="brand-new-dependency-resolver">Brand new dependency resolver</h3> <p>The dependency resolver has been rewritten from scratch to make it more resilient and reliable.</p> <p>It solves conflicts in a faster and smarter way to be as exhaustive as possible.</p> <p>It also comes with much clearer error messages when no valid solution can be found. Here are some examples:</p>https://python-poetry.org/blog/poetry-0.9.1-is-out/Fri, 18 May 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.9.1-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed handling of package names with dots. (Thanks to <a href="https://github.com/bertjwregeer">bertjwregeer</a>)</li> <li>Fixed path dependencies being resolved from the current path instead of the <code>pyproject.toml</code> file. (Thanks to <a href="https://github.com/radix">radix</a>)</li> </ul>https://python-poetry.org/blog/poetry-0.9.0-is-out/Mon, 07 May 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.9.0-is-out/<p>This version brings huge improvements to the dependency resolution speed.</p> <h2 id="new-features">New Features</h2> <h3 id="huge-speed-improvements-in-the-dependency-resolution-process">Huge speed improvements in the dependency resolution process</h3> <p>In previous releases, the dependency resolution process could be extremely slow, especially for some packages like <code>boto3</code>, due to the way the resolver works.</p> <p>So, one of the focus of this release was to improve it so that the dependency resolution time could be deemed acceptable. And it seems it paid off.</p>https://python-poetry.org/blog/poetry-0.8.6-is-out/Mon, 30 Apr 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.8.6-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed config files not being created with the <code>config</code> command.</li> </ul>https://python-poetry.org/blog/poetry-0.8.5-is-out/Thu, 19 Apr 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.8.5-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed a bug in dependency resolution which led to installation errors.</li> <li>Fixed a bug where malformed sdists would lead to dependency resolution failing.</li> </ul>https://python-poetry.org/blog/poetry-0.8.4-is-out/Wed, 18 Apr 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.8.4-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed a bug where dependencies constraints in lock were too strict.</li> <li>Fixed unicode error in <code>search</code> command for Python 2.7.</li> <li>Fixed error with git dependencies.</li> </ul>https://python-poetry.org/blog/poetry-0.8.3-is-out/Mon, 16 Apr 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.8.3-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed platform verification which led to missing packages.</li> <li>Fixed duplicates in <code>pyproject.lock</code>.</li> </ul>https://python-poetry.org/blog/poetry-0.8.2-is-out/Sat, 14 Apr 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.8.2-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed <code>add</code> command picking up prereleases by default.</li> <li>Fixed dependendency resolution on Windows when unpacking distributions.</li> <li>Fixed dependency resolution with post releases.</li> <li>Fixed dependencies being installed even if not necessary for current system.</li> </ul>https://python-poetry.org/blog/poetry-0.8.0-is-out/Fri, 13 Apr 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.8.0-is-out/<p>This version brings some improvements and a bunch of bugfixes.</p> <h2 id="new-features">New Features</h2> <h3 id="support-for-python-27">Support for Python 2.7</h3> <p>After adding support for Python 3.4 and 3.5 in version 0.7.0, <code>poetry</code> now supports Python 2.7.</p> <p>The decision was made so that Python 2.7 projects can benefit from the advantages that <code>poetry</code> provides.</p> <h3 id="fallback-mechanism-for-missing-dependencies">Fallback mechanism for missing dependencies</h3> <p><code>poetry</code> uses the PyPI JSON API to retrieve package information.</p> <p>However, some packages (like <code>boto3</code> for example) have missing dependency information due to bad packaging/publishing which means that <code>poetry</code> won&rsquo;t be able to properly resolve dependencies.</p>https://python-poetry.org/blog/poetry-0.8.1-is-out/Fri, 13 Apr 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.8.1-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed resolution with bad (empty) releases.</li> <li>Fixed <code>version</code> for prereleases.</li> <li>Fixed <code>search</code> not working outside of a project.</li> <li>Fixed <code>self:update</code> not working outside of a project.</li> </ul>https://python-poetry.org/blog/poetry-0.7.0-is-out/Wed, 04 Apr 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.7.0-is-out/<p>This version brings some improvements and a bunch of bugfixes.</p> <h2 id="new-features">New Features</h2> <h3 id="support-for-python-34">Support for Python 3.4+</h3> <p>Previously, Poetry supported Python 3.6+ but after some consideration it was decided that it would support all Python 3 versions currently by the Python core team (see <a href="https://devguide.python.org/#status-of-python-branches)">https://devguide.python.org/#status-of-python-branches)</a>.</p> <p>So now, Poetry supports Python 3.4+.</p> <h3 id="new-standalone-installer">New standalone installer</h3> <p>Poetry now provides a custom installer that will install <code>poetry</code> isolated from the rest of your system by vendorizing its dependencies. This is the recommended way of installing <code>poetry</code>.</p>https://python-poetry.org/blog/poetry-0.6.5-is-out/Thu, 22 Mar 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.6.5-is-out/<p>Bugfix release.</p> <h2 id="fixed">Fixed</h2> <ul> <li>Fixed handling of extras in wheels metadata.</li> </ul>https://python-poetry.org/blog/poetry-0.6.4-is-out/Wed, 21 Mar 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.6.4-is-out/<p>Bugfix release.</p> <h2 id="new-features">New features</h2> <ul> <li>Added a <code>debug:info</code> command to get information about current environment.</li> </ul> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed Python version retrieval inside virtualenvs.</li> <li>Fixed optional dependencies being set as required in sdist.</li> <li>Fixed <code>--optional</code> option in the <code>add</code> command not being used.</li> </ul>https://python-poetry.org/blog/poetry-0.6.3-is-out/Tue, 20 Mar 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.6.3-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed built wheels not getting information from the virtualenv.</li> <li>Fixed building wheel with conditional extensions.</li> <li>Fixed missing files in built wheel with extensions.</li> <li>Fixed call to venv binaries on windows.</li> <li>Fixed subdependencies representation in lock file.</li> </ul>https://python-poetry.org/blog/poetry-0.6.2-is-out/Mon, 19 Mar 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.6.2-is-out/<p>Bugfix release.</p> <h2 id="changes">Changes</h2> <ul> <li>Changed how wildcard constraints are handled.</li> </ul> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed errors with pip 9.0.2.</li> </ul>https://python-poetry.org/blog/poetry-0.6.1-is-out/Sun, 18 Mar 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.6.1-is-out/<p>Bugfix release.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed wheel entry points being written on a single line.</li> <li>Fixed wheel metadata (Tag and Root-Is-Purelib).</li> </ul>https://python-poetry.org/blog/poetry-0.6.0-is-out/Fri, 16 Mar 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.6.0-is-out/<p>This version brings some improvements and a bunch of bugfixes.</p> <h2 id="new-features">New Features</h2> <h3 id="virtualenv-autogeneration">Virtualenv autogeneration</h3> <p>Now, whenever you install packages, Poetry, if not already inside a virtualenv, will create a virtualenv automatically, or use a previously create one, to always work isolated from the rest of your system.</p> <aside class="warning"><p> Since Poetry is 3.6+ only, it will create virtualenvs using the standard library `venv` module.</p> <p>So, if you want to work with a previous Python version in your project, you will need to create your own virtualenvs using, for instance, <a href="https://github.com/berdario/pew">pew</a>. </p>https://python-poetry.org/blog/poetry-0.5.0-is-out/Wed, 14 Mar 2018 09:12:35 +0000https://python-poetry.org/blog/poetry-0.5.0-is-out/<p>This version brings some improvements and a bunch of bugfixes.</p> <h2 id="changes">Changes</h2> <h3 id="hashes-check-when-installing">Hashes check when installing</h3> <p>Whenever you install packages with poetry, they will be verified against the hashes present in the <code>pyproject.lock</code> file to increase security.</p> <h2 id="fixes">Fixes</h2> <ul> <li>Fixed handling of post releases.</li> <li>Fixed python restricted dependencies not being checked against virtualenv version.</li> <li>Fixed python/platform constraint not being picked up for subdependencies.</li> <li>Fixed skipped packages appearing as installing.</li> <li>Fixed platform specification not being used when resolving dependencies.</li> </ul>https://python-poetry.org/docs/basic-usage/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/basic-usage/<h1 id="basic-usage">Basic usage</h1> <p>For the basic usage introduction we will be installing <code>pendulum</code>, a datetime library. If you have not yet installed Poetry, refer to the <a href="https://python-poetry.org/docs/" title="Introduction">Introduction</a> chapter.</p> <h2 id="project-setup">Project setup</h2> <p>First, let&rsquo;s create our new project, let&rsquo;s call it <code>poetry-demo</code>:</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">poetry new poetry-demo </span></span></code></pre></div><p>This will create the <code>poetry-demo</code> directory with the following content:</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">poetry-demo </span></span><span class="line"><span class="cl">├── pyproject.toml </span></span><span class="line"><span class="cl">├── README.md </span></span><span class="line"><span class="cl">├── src </span></span><span class="line"><span class="cl">│ └── poetry_demo </span></span><span class="line"><span class="cl">│ └── __init__.py </span></span><span class="line"><span class="cl">└── tests </span></span><span class="line"><span class="cl"> └── __init__.py </span></span></code></pre></div><p>The <code>pyproject.toml</code> file is what is the most important here. This will orchestrate your project and its dependencies. For now, it looks like this:</p>https://python-poetry.org/docs/1.8/basic-usage/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/1.8/basic-usage/<h1 id="basic-usage">Basic usage</h1> <p>For the basic usage introduction we will be installing <code>pendulum</code>, a datetime library. If you have not yet installed Poetry, refer to the <a href="https://python-poetry.org/docs/" title="Introduction">Introduction</a> chapter.</p> <h2 id="project-setup">Project setup</h2> <p>First, let&rsquo;s create our new project, let&rsquo;s call it <code>poetry-demo</code>:</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">poetry new poetry-demo </span></span></code></pre></div><p>This will create the <code>poetry-demo</code> directory with the following content:</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">poetry-demo </span></span><span class="line"><span class="cl">├── pyproject.toml </span></span><span class="line"><span class="cl">├── README.md </span></span><span class="line"><span class="cl">├── poetry_demo </span></span><span class="line"><span class="cl">│ └── __init__.py </span></span><span class="line"><span class="cl">└── tests </span></span><span class="line"><span class="cl"> └── __init__.py </span></span></code></pre></div><p>The <code>pyproject.toml</code> file is what is the most important here. This will orchestrate your project and its dependencies. For now, it looks like this:</p>https://python-poetry.org/docs/main/basic-usage/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/main/basic-usage/<h1 id="basic-usage">Basic usage</h1> <p>For the basic usage introduction we will be installing <code>pendulum</code>, a datetime library. If you have not yet installed Poetry, refer to the <a href="https://python-poetry.org/docs/" title="Introduction">Introduction</a> chapter.</p> <h2 id="project-setup">Project setup</h2> <p>First, let&rsquo;s create our new project, let&rsquo;s call it <code>poetry-demo</code>:</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">poetry new poetry-demo </span></span></code></pre></div><p>This will create the <code>poetry-demo</code> directory with the following content:</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">poetry-demo </span></span><span class="line"><span class="cl">├── pyproject.toml </span></span><span class="line"><span class="cl">├── README.md </span></span><span class="line"><span class="cl">├── src </span></span><span class="line"><span class="cl">│ └── poetry_demo </span></span><span class="line"><span class="cl">│ └── __init__.py </span></span><span class="line"><span class="cl">└── tests </span></span><span class="line"><span class="cl"> └── __init__.py </span></span></code></pre></div><p>The <code>pyproject.toml</code> file is what is the most important here. This will orchestrate your project and its dependencies. For now, it looks like this:</p>https://python-poetry.org/docs/building-extension-modules/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/building-extension-modules/<h1 id="building-extension-modules">Building Extension Modules</h1> <div class="admonition warning"> <div class="title">Warning</div> <div class="content"><p>While this feature has been around since almost the beginning of the Poetry project and has needed minimal changes, it is still considered unstable. You can participate in the discussions about stabilizing this feature <a href="https://github.com/python-poetry/poetry/issues/2740">here</a>.</p> <p>And as always, your contributions towards the goal of improving this feature are also welcome.</p> </div> </div> <p>Poetry allows a project developer to introduce support for, build and distribute native extensions within their project. In order to achieve this, at the highest level, the following steps are required.</p>https://python-poetry.org/docs/main/building-extension-modules/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/main/building-extension-modules/<h1 id="building-extension-modules">Building Extension Modules</h1> <div class="admonition warning"> <div class="title">Warning</div> <div class="content"><p>While this feature has been around since almost the beginning of the Poetry project and has needed minimal changes, it is still considered unstable. You can participate in the discussions about stabilizing this feature <a href="https://github.com/python-poetry/poetry/issues/2740">here</a>.</p> <p>And as always, your contributions towards the goal of improving this feature are also welcome.</p> </div> </div> <p>Poetry allows a project developer to introduce support for, build and distribute native extensions within their project. In order to achieve this, at the highest level, the following steps are required.</p>https://python-poetry.org/docs/cli/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/cli/<h1 id="commands">Commands</h1> <p>You&rsquo;ve already learned how to use the command-line interface to do some things. This chapter documents all the available commands.</p> <p>To get help from the command-line, simply call <code>poetry</code> to see the complete list of commands, then <code>--help</code> combined with any of those can give you more information.</p> <h2 id="global-options">Global Options</h2> <ul> <li><code>--verbose (-v|vv|vvv)</code>: Increase the verbosity of messages: &ldquo;-v&rdquo; for normal output, &ldquo;-vv&rdquo; for more verbose output and &ldquo;-vvv&rdquo; for debug.</li> </ul> <div class="admonition note"> <div class="title">Note</div> <div class="content"><p>You can also set the verbosity level using the <code>SHELL_VERBOSITY</code> environment variable. This is useful in CI/CD pipelines or scripts where you cannot easily modify command-line arguments.</p>https://python-poetry.org/docs/1.8/cli/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/1.8/cli/<h1 id="commands">Commands</h1> <p>You&rsquo;ve already learned how to use the command-line interface to do some things. This chapter documents all the available commands.</p> <p>To get help from the command-line, simply call <code>poetry</code> to see the complete list of commands, then <code>--help</code> combined with any of those can give you more information.</p> <h2 id="global-options">Global options</h2> <ul> <li><code>--verbose (-v|vv|vvv)</code>: Increase the verbosity of messages: &ldquo;-v&rdquo; for normal output, &ldquo;-vv&rdquo; for more verbose output and &ldquo;-vvv&rdquo; for debug.</li> <li><code>--help (-h)</code> : Display help information.</li> <li><code>--quiet (-q)</code> : Do not output any message.</li> <li><code>--ansi</code>: Force ANSI output.</li> <li><code>--no-ansi</code>: Disable ANSI output.</li> <li><code>--version (-V)</code>: Display this application version.</li> <li><code>--no-interaction (-n)</code>: Do not ask any interactive question.</li> <li><code>--no-plugins</code>: Disables plugins.</li> <li><code>--no-cache</code>: Disables Poetry source caches.</li> <li><code>--directory=DIRECTORY (-C)</code>: The working directory for the Poetry command (defaults to the current working directory).</li> </ul> <h2 id="new">new</h2> <p>This command will help you kickstart your new Python project by creating a directory structure suitable for most projects.</p>https://python-poetry.org/docs/main/cli/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/main/cli/<h1 id="commands">Commands</h1> <p>You&rsquo;ve already learned how to use the command-line interface to do some things. This chapter documents all the available commands.</p> <p>To get help from the command-line, simply call <code>poetry</code> to see the complete list of commands, then <code>--help</code> combined with any of those can give you more information.</p> <h2 id="global-options">Global Options</h2> <ul> <li><code>--verbose (-v|vv|vvv)</code>: Increase the verbosity of messages: &ldquo;-v&rdquo; for normal output, &ldquo;-vv&rdquo; for more verbose output and &ldquo;-vvv&rdquo; for debug.</li> </ul> <div class="admonition note"> <div class="title">Note</div> <div class="content"><p>You can also set the verbosity level using the <code>SHELL_VERBOSITY</code> environment variable. This is useful in CI/CD pipelines or scripts where you cannot easily modify command-line arguments.</p>https://python-poetry.org/docs/community/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/community/<h1 id="community">Community</h1> <h2 id="badge">Badge</h2> <p>For any projects using Poetry, you may add its official badge somewhere prominent like the README.</p> <p><a href="https://python-poetry.org/"><img src="https://img.shields.io/endpoint?url=https://python-poetry.org/badge/v0.json" alt="Poetry"></a></p> <p><strong>Markdown</strong></p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-md" data-lang="md"><span class="line"><span class="cl">[<span class="nt">![Poetry</span>](<span class="na">https://img.shields.io/endpoint?url=https://python-poetry.org/badge/v0.json</span>)](https://python-poetry.org/) </span></span></code></pre></div><p><strong>reStructuredText</strong></p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-rst" data-lang="rst"><span class="line"><span class="cl"><span class="p">..</span> <span class="ow">image</span><span class="p">::</span> https://img.shields.io/endpoint?url=https://python-poetry.org/badge/v0.json<span class="err"> </span></span></span><span class="line"><span class="cl"><span class="err"></span> <span class="nc">:alt:</span> <span class="nf">Poetry</span><span class="err"> </span></span></span><span class="line"><span class="cl"><span class="err"></span> <span class="nc">:target:</span> <span class="nf">https://python-poetry.org/</span><span class="err"> </span></span></span></code></pre></div>https://python-poetry.org/docs/1.8/community/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/1.8/community/<h1 id="community">Community</h1> <h2 id="badge">Badge</h2> <p>For any projects using Poetry, you may add its official badge somewhere prominent like the README.</p> <p><a href="https://python-poetry.org/"><img src="https://img.shields.io/endpoint?url=https://python-poetry.org/badge/v0.json" alt="Poetry"></a></p> <p><strong>Markdown</strong></p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-md" data-lang="md"><span class="line"><span class="cl">[<span class="nt">![Poetry</span>](<span class="na">https://img.shields.io/endpoint?url=https://python-poetry.org/badge/v0.json</span>)](https://python-poetry.org/) </span></span></code></pre></div><p><strong>reStructuredText</strong></p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-rst" data-lang="rst"><span class="line"><span class="cl"><span class="p">..</span> <span class="ow">image</span><span class="p">::</span> https://img.shields.io/endpoint?url=https://python-poetry.org/badge/v0.json<span class="err"> </span></span></span><span class="line"><span class="cl"><span class="err"></span> <span class="nc">:alt:</span> <span class="nf">Poetry</span><span class="err"> </span></span></span><span class="line"><span class="cl"><span class="err"></span> <span class="nc">:target:</span> <span class="nf">https://python-poetry.org/</span><span class="err"> </span></span></span></code></pre></div>https://python-poetry.org/docs/main/community/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/main/community/<h1 id="community">Community</h1> <h2 id="badge">Badge</h2> <p>For any projects using Poetry, you may add its official badge somewhere prominent like the README.</p> <p><a href="https://python-poetry.org/"><img src="https://img.shields.io/endpoint?url=https://python-poetry.org/badge/v0.json" alt="Poetry"></a></p> <p><strong>Markdown</strong></p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-md" data-lang="md"><span class="line"><span class="cl">[<span class="nt">![Poetry</span>](<span class="na">https://img.shields.io/endpoint?url=https://python-poetry.org/badge/v0.json</span>)](https://python-poetry.org/) </span></span></code></pre></div><p><strong>reStructuredText</strong></p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-rst" data-lang="rst"><span class="line"><span class="cl"><span class="p">..</span> <span class="ow">image</span><span class="p">::</span> https://img.shields.io/endpoint?url=https://python-poetry.org/badge/v0.json<span class="err"> </span></span></span><span class="line"><span class="cl"><span class="err"></span> <span class="nc">:alt:</span> <span class="nf">Poetry</span><span class="err"> </span></span></span><span class="line"><span class="cl"><span class="err"></span> <span class="nc">:target:</span> <span class="nf">https://python-poetry.org/</span><span class="err"> </span></span></span></code></pre></div>https://python-poetry.org/docs/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/configuration/<h1 id="configuration">Configuration</h1> <p>Poetry can be configured via the <code>config</code> command (<a href="https://python-poetry.org/docs/cli/#config" title="config command documentation">see more about its usage here</a>) or directly in the <code>config.toml</code> file that will be automatically created when you first run that command. This file can typically be found in one of the following directories:</p> <ul> <li>macOS: <code>~/Library/Application Support/pypoetry</code></li> <li>Windows: <code>%APPDATA%\pypoetry</code></li> </ul> <p>For Unix, we follow the XDG spec and support <code>$XDG_CONFIG_HOME</code>. That means, by default <code>~/.config/pypoetry</code>.</p> <h2 id="local-configuration">Local configuration</h2> <p>Poetry also provides the ability to have settings that are specific to a project by passing the <code>--local</code> option to the <code>config</code> command.</p>https://python-poetry.org/docs/1.8/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/1.8/configuration/<h1 id="configuration">Configuration</h1> <p>Poetry can be configured via the <code>config</code> command (<a href="https://python-poetry.org/docs/1.8/cli/#config" title="config command documentation">see more about its usage here</a>) or directly in the <code>config.toml</code> file that will be automatically created when you first run that command. This file can typically be found in one of the following directories:</p> <ul> <li>macOS: <code>~/Library/Application Support/pypoetry</code></li> <li>Windows: <code>%APPDATA%\pypoetry</code></li> </ul> <p>For Unix, we follow the XDG spec and support <code>$XDG_CONFIG_HOME</code>. That means, by default <code>~/.config/pypoetry</code>.</p> <h2 id="local-configuration">Local configuration</h2> <p>Poetry also provides the ability to have settings that are specific to a project by passing the <code>--local</code> option to the <code>config</code> command.</p>https://python-poetry.org/docs/main/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/main/configuration/<h1 id="configuration">Configuration</h1> <p>Poetry can be configured via the <code>config</code> command (<a href="https://python-poetry.org/docs/main/cli/#config" title="config command documentation">see more about its usage here</a>) or directly in the <code>config.toml</code> file that will be automatically created when you first run that command. This file can typically be found in one of the following directories:</p> <ul> <li>macOS: <code>~/Library/Application Support/pypoetry</code></li> <li>Windows: <code>%APPDATA%\pypoetry</code></li> </ul> <p>For Unix, we follow the XDG spec and support <code>$XDG_CONFIG_HOME</code>. That means, by default <code>~/.config/pypoetry</code>.</p> <h2 id="local-configuration">Local configuration</h2> <p>Poetry also provides the ability to have settings that are specific to a project by passing the <code>--local</code> option to the <code>config</code> command.</p>https://python-poetry.org/docs/contributing/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/contributing/<h1 id="contributing-to-poetry">Contributing to Poetry</h1> <p>First off, thanks for taking the time to contribute!</p> <p>The following is a set of guidelines for contributing to Poetry on GitHub. These are mostly guidelines, not rules. Use your best judgement, and feel free to propose changes to this document in a pull request.</p> <h2 id="how-to-contribute">How to contribute</h2> <h3 id="reporting-bugs">Reporting bugs</h3> <p>This section guides you through submitting a bug report for Poetry. Following these guidelines helps maintainers and the community understands your report, reproduces the behavior, and finds related reports.</p>https://python-poetry.org/docs/1.8/contributing/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/1.8/contributing/<h1 id="contributing-to-poetry">Contributing to Poetry</h1> <p>First off, thanks for taking the time to contribute!</p> <p>The following is a set of guidelines for contributing to Poetry on GitHub. These are mostly guidelines, not rules. Use your best judgement, and feel free to propose changes to this document in a pull request.</p> <h2 id="how-to-contribute">How to contribute</h2> <h3 id="reporting-bugs">Reporting bugs</h3> <p>This section guides you through submitting a bug report for Poetry. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.</p>https://python-poetry.org/docs/main/contributing/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/main/contributing/<h1 id="contributing-to-poetry">Contributing to Poetry</h1> <p>First off, thanks for taking the time to contribute!</p> <p>The following is a set of guidelines for contributing to Poetry on GitHub. These are mostly guidelines, not rules. Use your best judgement, and feel free to propose changes to this document in a pull request.</p> <h2 id="how-to-contribute">How to contribute</h2> <h3 id="reporting-bugs">Reporting bugs</h3> <p>This section guides you through submitting a bug report for Poetry. Following these guidelines helps maintainers and the community understands your report, reproduces the behavior, and finds related reports.</p>https://python-poetry.org/docs/dependency-specification/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/dependency-specification/<h1 id="dependency-specification">Dependency specification</h1> <p>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.</p> <h2 id="projectdependencies-and-toolpoetrydependencies"><code>project.dependencies</code> and <code>tool.poetry.dependencies</code></h2> <p>Prior Poetry 2.0, dependencies had to be declared in the <code>tool.poetry.dependencies</code> section of the <code>pyproject.toml</code> file.</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-toml" data-lang="toml"><span class="line"><span class="cl"><span class="p">[</span><span class="nx">tool</span><span class="p">.</span><span class="nx">poetry</span><span class="p">.</span><span class="nx">dependencies</span><span class="p">]</span> </span></span><span class="line"><span class="cl"><span class="nx">requests</span> <span class="p">=</span> <span class="s2">&#34;^2.13.0&#34;</span> </span></span></code></pre></div><p>With Poetry 2.0, you should consider using the <code>project.dependencies</code> section instead.</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-toml" data-lang="toml"><span class="line"><span class="cl"><span class="p">[</span><span class="nx">project</span><span class="p">]</span> </span></span><span class="line"><span class="cl"><span class="c"># ...</span> </span></span><span class="line"><span class="cl"><span class="nx">dependencies</span> <span class="p">=</span> <span class="p">[</span> </span></span><span class="line"><span class="cl"> <span class="s2">&#34;requests (&gt;=2.23.0,&lt;3.0.0)&#34;</span> </span></span><span class="line"><span class="cl"><span class="p">]</span> </span></span></code></pre></div><p>While dependencies in <code>tool.poetry.dependencies</code> are specified using toml tables, dependencies in <code>project.dependencies</code> are specified as strings according to <a href="https://peps.python.org/pep-0508/">PEP 508</a>.</p>https://python-poetry.org/docs/1.8/dependency-specification/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/1.8/dependency-specification/<h1 id="dependency-specification">Dependency specification</h1> <p>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.</p> <h2 id="version-constraints">Version constraints</h2> <h3 id="caret-requirements">Caret requirements</h3> <p><strong>Caret requirements</strong> allow <a href="https://semver.org/">SemVer</a> 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 <code>poetry add requests@^2.13.0</code> and wanted to update the library and ran <code>poetry update requests</code>, poetry would update us to version <code>2.14.0</code> if it was available, but would not update us to <code>3.0.0</code>. If instead we had specified the version string as <code>^0.1.13</code>, poetry would update to <code>0.1.14</code> but not <code>0.2.0</code>. <code>0.0.x</code> is not considered compatible with any other version.</p>https://python-poetry.org/docs/main/dependency-specification/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/main/dependency-specification/<h1 id="dependency-specification">Dependency specification</h1> <p>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.</p> <h2 id="projectdependencies-and-toolpoetrydependencies"><code>project.dependencies</code> and <code>tool.poetry.dependencies</code></h2> <p>Prior Poetry 2.0, dependencies had to be declared in the <code>tool.poetry.dependencies</code> section of the <code>pyproject.toml</code> file.</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-toml" data-lang="toml"><span class="line"><span class="cl"><span class="p">[</span><span class="nx">tool</span><span class="p">.</span><span class="nx">poetry</span><span class="p">.</span><span class="nx">dependencies</span><span class="p">]</span> </span></span><span class="line"><span class="cl"><span class="nx">requests</span> <span class="p">=</span> <span class="s2">&#34;^2.13.0&#34;</span> </span></span></code></pre></div><p>With Poetry 2.0, you should consider using the <code>project.dependencies</code> section instead.</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-toml" data-lang="toml"><span class="line"><span class="cl"><span class="p">[</span><span class="nx">project</span><span class="p">]</span> </span></span><span class="line"><span class="cl"><span class="c"># ...</span> </span></span><span class="line"><span class="cl"><span class="nx">dependencies</span> <span class="p">=</span> <span class="p">[</span> </span></span><span class="line"><span class="cl"> <span class="s2">&#34;requests (&gt;=2.23.0,&lt;3.0.0)&#34;</span> </span></span><span class="line"><span class="cl"><span class="p">]</span> </span></span></code></pre></div><p>While dependencies in <code>tool.poetry.dependencies</code> are specified using toml tables, dependencies in <code>project.dependencies</code> are specified as strings according to <a href="https://peps.python.org/pep-0508/">PEP 508</a>.</p>https://python-poetry.org/docs/faq/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/faq/<h1 id="faq">FAQ</h1> <h3 id="why-is-the-dependency-resolution-process-slow">Why is the dependency resolution process slow?</h3> <p>While the dependency resolver at the heart of Poetry is highly optimized and should be fast enough for most cases, with certain sets of dependencies, it can take time to find a valid solution.</p> <p>This is due to the fact that not all libraries on PyPI have properly declared their metadata and, as such, they are not available via the PyPI JSON API. At this point, Poetry has no choice but to download the packages and inspect them to get the necessary information. This is an expensive operation, both in bandwidth and time, which is why it seems this is a long process.</p>https://python-poetry.org/docs/1.8/faq/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/1.8/faq/<h1 id="faq">FAQ</h1> <h3 id="why-is-the-dependency-resolution-process-slow">Why is the dependency resolution process slow?</h3> <p>While the dependency resolver at the heart of Poetry is highly optimized and should be fast enough for most cases, with certain sets of dependencies it can take time to find a valid solution.</p> <p>This is due to the fact that not all libraries on PyPI have properly declared their metadata and, as such, they are not available via the PyPI JSON API. At this point, Poetry has no choice but to download the packages and inspect them to get the necessary information. This is an expensive operation, both in bandwidth and time, which is why it seems this is a long process.</p>https://python-poetry.org/docs/main/faq/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/main/faq/<h1 id="faq">FAQ</h1> <h3 id="why-is-the-dependency-resolution-process-slow">Why is the dependency resolution process slow?</h3> <p>While the dependency resolver at the heart of Poetry is highly optimized and should be fast enough for most cases, with certain sets of dependencies, it can take time to find a valid solution.</p> <p>This is due to the fact that not all libraries on PyPI have properly declared their metadata and, as such, they are not available via the PyPI JSON API. At this point, Poetry has no choice but to download the packages and inspect them to get the necessary information. This is an expensive operation, both in bandwidth and time, which is why it seems this is a long process.</p>https://python-poetry.org/history/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/history/<h2 id="234---2026-04-12"><a href="https://github.com/python-poetry/poetry/releases/tag/2.3.4">2.3.4</a> - 2026-04-12</h2> <h3 id="fixed">Fixed</h3> <ul> <li>Fix a performance regression in the wheel installer that was introduced in Poetry 2.3.3 (<a href="https://github.com/python-poetry/poetry/pull/10821">#10821</a>).</li> <li>Fix a path traversal vulnerability in sdist extraction on Python 3.10.0-3.10.12 and 3.11.0-3.11.4 that could allow malicious tarball files to write files outside the target directory (<a href="https://github.com/python-poetry/poetry/pull/10837">#10837</a>).</li> </ul> <h2 id="233---2026-03-29"><a href="https://github.com/python-poetry/poetry/releases/tag/2.3.3">2.3.3</a> - 2026-03-29</h2> <h3 id="fixed-1">Fixed</h3> <ul> <li><strong>Fix a path traversal vulnerability in the wheel installer that could allow malicious wheel files to write files outside the intended installation directory</strong> (<a href="https://github.com/python-poetry/poetry/pull/10792">#10792</a>).</li> <li>Fix an issue where <code>git</code> dependencies from annotated tags could not be updated (<a href="https://github.com/python-poetry/poetry/pull/10719">#10719</a>).</li> <li>Fix an issue where empty <code>VIRTUAL_ENV</code> or <code>CONDA_PREFIX</code> environment variables (e.g., after <code>conda deactivate</code>) would cause Poetry to incorrectly detect an active virtualenv (<a href="https://github.com/python-poetry/poetry/pull/10784">#10784</a>).</li> <li>Fix an issue where an incomprehensible error message was printed when <code>.venv</code> was a file instead of a directory (<a href="https://github.com/python-poetry/poetry/pull/10777">#10777</a>).</li> <li>Fix an issue where HTTP Basic Authentication credentials could be corrupted during request preparation, causing authentication failures with long tokens (<a href="https://github.com/python-poetry/poetry/pull/10748">#10748</a>).</li> <li>Fix an issue where <code>poetry publish --no-interaction --build</code> requested user interaction (<a href="https://github.com/python-poetry/poetry/pull/10769">#10769</a>).</li> <li>Fix an issue where <code>poetry init</code> and <code>poetry new</code> created a deprecated <code>project.license</code> format (<a href="https://github.com/python-poetry/poetry/pull/10787">#10787</a>).</li> </ul> <h3 id="docs">Docs</h3> <ul> <li>Clarify the differences between <code>poetry install</code> and <code>poetry update</code> (<a href="https://github.com/python-poetry/poetry/pull/10713">#10713</a>).</li> <li>Clarify the section of fields in the <code>pyproject.toml</code> examples (<a href="https://github.com/python-poetry/poetry/pull/10753">#10753</a>).</li> <li>Add a note about the different installation location when Python from the Microsoft Store is used (<a href="https://github.com/python-poetry/poetry/pull/10759">#10759</a>).</li> <li>Fix the system requirements for Poetry (<a href="https://github.com/python-poetry/poetry/pull/10739">#10739</a>).</li> <li>Fix the <code>poetry cache clear</code> example (<a href="https://github.com/python-poetry/poetry/pull/10749">#10749</a>).</li> <li>Fix the link to <code>pipx</code> installation instructions (<a href="https://github.com/python-poetry/poetry/pull/10783">#10783</a>).</li> </ul> <h3 id="poetry-core-232httpsgithubcompython-poetrypoetry-corereleasestag232">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/2.3.2"><code>2.3.2</code></a>)</h3> <ul> <li>Fix an issue where <code>platform_release</code> could not be parsed on Debian Trixie (<a href="https://github.com/python-poetry/poetry-core/pull/930">#930</a>).</li> <li>Fix an issue where using <code>project.readme.text</code> in the <code>pyproject.toml</code> file resulted in broken metadata (<a href="https://github.com/python-poetry/poetry-core/pull/914">#914</a>).</li> <li>Fix an issue where dependency groups were considered equal when their resolved dependencies were equal, even if the groups themselves were not (<a href="https://github.com/python-poetry/poetry-core/pull/919">#919</a>).</li> <li>Fix an issue where removing a dependency from a group that included another group resulted in other dependencies being added to the included group (<a href="https://github.com/python-poetry/poetry-core/pull/922">#922</a>).</li> <li>Fix an issue where PEP 735 <code>include-group</code> entries were lost when <code>[tool.poetry.group]</code> also defined <code>include-groups</code> for the same group (<a href="https://github.com/python-poetry/poetry-core/pull/924">#924</a>).</li> <li>Fix an issue where the union of <code>&lt;value&gt; not in &lt;marker&gt;</code> constraints was wrongly treated as always satisfied (<a href="https://github.com/python-poetry/poetry-core/pull/925">#925</a>).</li> <li>Fix an issue where a post release with a local version identifier was wrongly allowed by a <code>&gt;</code> version constraint (<a href="https://github.com/python-poetry/poetry-core/pull/921">#921</a>).</li> <li>Fix an issue where a version with the local version identifier <code>0</code> was treated as equal to the corresponding public version (<a href="https://github.com/python-poetry/poetry-core/pull/920">#920</a>).</li> <li>Fix an issue where a <code>!= &lt;version&gt;</code> constraint wrongly disallowed pre releases and post releases of the specified version (<a href="https://github.com/python-poetry/poetry-core/pull/929">#929</a>).</li> <li>Fix an issue where <code>in</code> and <code>not in</code> constraints were wrongly not allowed by specific compound constraints (<a href="https://github.com/python-poetry/poetry-core/pull/927">#927</a>).</li> </ul> <h2 id="232---2026-02-01"><a href="https://github.com/python-poetry/poetry/releases/tag/2.3.2">2.3.2</a> - 2026-02-01</h2> <h3 id="changed">Changed</h3> <ul> <li>Allow <code>dulwich&gt;=1.0</code> (<a href="https://github.com/python-poetry/poetry/pull/10701">#10701</a>).</li> </ul> <h3 id="poetry-core-231httpsgithubcompython-poetrypoetry-corereleasestag231">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/2.3.1"><code>2.3.1</code></a>)</h3> <ul> <li>Fix an issue where <code>platform_release</code> could not be parsed on Windows Server (<a href="https://github.com/python-poetry/poetry-core/pull/911">#911</a>).</li> </ul> <h2 id="231---2026-01-20"><a href="https://github.com/python-poetry/poetry/releases/tag/2.3.1">2.3.1</a> - 2026-01-20</h2> <h3 id="fixed-2">Fixed</h3> <ul> <li>Fix an issue where cached information about each package was always considered outdated (<a href="https://github.com/python-poetry/poetry/pull/10699">#10699</a>).</li> </ul> <h3 id="docs-1">Docs</h3> <ul> <li>Document SHELL_VERBOSITY environment variable (<a href="https://github.com/python-poetry/poetry/pull/10678">#10678</a>).</li> </ul> <h2 id="230---2026-01-18"><a href="https://github.com/python-poetry/poetry/releases/tag/2.3.0">2.3.0</a> - 2026-01-18</h2> <h3 id="added">Added</h3> <ul> <li><strong>Add support for exporting <code>pylock.toml</code> files with <code>poetry-plugin-export</code></strong> (<a href="https://github.com/python-poetry/poetry/pull/10677">#10677</a>).</li> <li>Add support for specifying build constraints for dependencies (<a href="https://github.com/python-poetry/poetry/pull/10388">#10388</a>).</li> <li>Add support for publishing artifacts whose version is determined dynamically by the build-backend (<a href="https://github.com/python-poetry/poetry/pull/10644">#10644</a>).</li> <li>Add support for editable project plugins (<a href="https://github.com/python-poetry/poetry/pull/10661">#10661</a>).</li> <li>Check <code>requires-poetry</code> before any other validation (<a href="https://github.com/python-poetry/poetry/pull/10593">#10593</a>).</li> <li>Validate the content of <code>project.readme</code> when running <code>poetry check</code> (<a href="https://github.com/python-poetry/poetry/pull/10604">#10604</a>).</li> <li>Add the option to clear all caches by making the cache name in <code>poetry cache clear</code> optional (<a href="https://github.com/python-poetry/poetry/pull/10627">#10627</a>).</li> <li>Automatically update the cache for packages where the locked files differ from cached files (<a href="https://github.com/python-poetry/poetry/pull/10657">#10657</a>).</li> <li>Suggest to clear the cache if running a command with <code>--no-cache</code> solves an issue (<a href="https://github.com/python-poetry/poetry/pull/10585">#10585</a>).</li> <li>Propose <code>poetry init</code> when trying <code>poetry new</code> for an existing directory (<a href="https://github.com/python-poetry/poetry/pull/10563">#10563</a>).</li> <li>Add support for <code>poetry publish --skip-existing</code> for new Nexus OSS versions (<a href="https://github.com/python-poetry/poetry/pull/10603">#10603</a>).</li> <li>Show Poetry&rsquo;s own Python&rsquo;s path in <code>poetry debug info</code> (<a href="https://github.com/python-poetry/poetry/pull/10588">#10588</a>).</li> </ul> <h3 id="changed-1">Changed</h3> <ul> <li><strong>Drop support for Python 3.9</strong> (<a href="https://github.com/python-poetry/poetry/pull/10634">#10634</a>).</li> <li><strong>Change the default of <code>installer.re-resolve</code> from <code>true</code> to <code>false</code></strong> (<a href="https://github.com/python-poetry/poetry/pull/10622">#10622</a>).</li> <li><strong>PEP 735 dependency groups are considered in the lock file hash</strong> (<a href="https://github.com/python-poetry/poetry/pull/10621">#10621</a>).</li> <li>Deprecate <code>poetry.utils._compat.metadata</code>, which is sometimes used in plugins, in favor of <code>importlib.metadata</code> (<a href="https://github.com/python-poetry/poetry/pull/10634">#10634</a>).</li> <li>Improve managing free-threaded Python versions with <code>poetry python</code> (<a href="https://github.com/python-poetry/poetry/pull/10606">#10606</a>).</li> <li>Prefer JSON API to HTML API in legacy repositories (<a href="https://github.com/python-poetry/poetry/pull/10672">#10672</a>).</li> <li>When running <code>poetry init</code>, only add the readme field in the <code>pyproject.toml</code> if the readme file exists (<a href="https://github.com/python-poetry/poetry/pull/10679">#10679</a>).</li> <li>Raise an error if no hash can be determined for any distribution link of a package (<a href="https://github.com/python-poetry/poetry/pull/10673">#10673</a>).</li> <li>Require <code>dulwich&gt;=0.25.0</code> (<a href="https://github.com/python-poetry/poetry/pull/10674">#10674</a>).</li> </ul> <h3 id="fixed-3">Fixed</h3> <ul> <li>Fix an issue where <code>poetry remove</code> did not work for PEP 735 dependency groups with <code>include-group</code> items (<a href="https://github.com/python-poetry/poetry/pull/10587">#10587</a>).</li> <li>Fix an issue where <code>poetry remove</code> caused dangling <code>include-group</code> references in PEP 735 dependency groups (<a href="https://github.com/python-poetry/poetry/pull/10590">#10590</a>).</li> <li>Fix an issue where <code>poetry add</code> did not work for PEP 735 dependency groups with <code>include-group</code> items (<a href="https://github.com/python-poetry/poetry/pull/10636">#10636</a>).</li> <li>Fix an issue where PEP 735 dependency groups were not considered in the lock file hash (<a href="https://github.com/python-poetry/poetry/pull/10621">#10621</a>).</li> <li>Fix an issue where wrong markers were locked for a dependency that was required by several groups with different markers (<a href="https://github.com/python-poetry/poetry/pull/10613">#10613</a>).</li> <li>Fix an issue where non-deterministic markers were created in a method used by <code>poetry-plugin-export</code> (<a href="https://github.com/python-poetry/poetry/pull/10667">#10667</a>).</li> <li>Fix an issue where wrong wheels were chosen for installation in free-threaded Python environments if Poetry itself was not installed with free-threaded Python (<a href="https://github.com/python-poetry/poetry/pull/10614">#10614</a>).</li> <li>Fix an issue where <code>poetry publish</code> used the metadata of the project instead of the metadata of the build artifact (<a href="https://github.com/python-poetry/poetry/pull/10624">#10624</a>).</li> <li>Fix an issue where <code>poetry env use</code> just used another Python version instead of failing when the requested version was not supported by the project (<a href="https://github.com/python-poetry/poetry/pull/10685">#10685</a>).</li> <li>Fix an issue where <code>poetry env activate</code> returned the wrong command for <code>dash</code> (<a href="https://github.com/python-poetry/poetry/pull/10696">#10696</a>).</li> <li>Fix an issue where <code>data-dir</code> and <code>python.installation-dir</code> could not be set (<a href="https://github.com/python-poetry/poetry/pull/10595">#10595</a>).</li> <li>Fix an issue where Python and pip executables were not correctly detected on Windows (<a href="https://github.com/python-poetry/poetry/pull/10645">#10645</a>).</li> <li>Fix an issue where invalid template variables in <code>virtualenvs.prompt</code> caused an incomprehensible error message (<a href="https://github.com/python-poetry/poetry/pull/10648">#10648</a>).</li> </ul> <h3 id="docs-2">Docs</h3> <ul> <li>Add a warning about <code>~/.netrc</code> for Poetry credential configuration (<a href="https://github.com/python-poetry/poetry/pull/10630">#10630</a>).</li> <li>Clarify that the local configuration takes precedence over the global configuration (<a href="https://github.com/python-poetry/poetry/pull/10676">#10676</a>).</li> <li>Add an explanation in which cases <code>packages</code> are automatically detected (<a href="https://github.com/python-poetry/poetry/pull/10680">#10680</a>).</li> </ul> <h3 id="poetry-core-230httpsgithubcompython-poetrypoetry-corereleasestag230">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/2.3.0"><code>2.3.0</code></a>)</h3> <ul> <li>Normalize versions (<a href="https://github.com/python-poetry/poetry-core/pull/893">#893</a>).</li> <li>Fix an issue where unsatisfiable requirements did not raise an error (<a href="https://github.com/python-poetry/poetry-core/pull/891">#891</a>).</li> <li>Fix an issue where the implicit main group did not exist if it was explicitly declared as not having any dependencies (<a href="https://github.com/python-poetry/poetry-core/pull/892">#892</a>).</li> <li>Fix an issue where <code>python_full_version</code> markers with pre-release versions were parsed incorrectly (<a href="https://github.com/python-poetry/poetry-core/pull/893">#893</a>).</li> </ul> <h2 id="221---2025-09-21"><a href="https://github.com/python-poetry/poetry/releases/tag/2.2.1">2.2.1</a> - 2025-09-21</h2> <h3 id="fixed-4">Fixed</h3> <ul> <li>Fix an issue where <code>poetry self show</code> failed with a message about an invalid output format (<a href="https://github.com/python-poetry/poetry/pull/10560">#10560</a>).</li> </ul> <h3 id="docs-3">Docs</h3> <ul> <li>Remove outdated statements about dependency groups (<a href="https://github.com/python-poetry/poetry/pull/10561">#10561</a>).</li> </ul> <h3 id="poetry-core-221httpsgithubcompython-poetrypoetry-corereleasestag221">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/2.2.1"><code>2.2.1</code></a>)</h3> <ul> <li>Fix an issue where it was not possible to declare a PEP 735 dependency group as optional (<a href="https://github.com/python-poetry/poetry-core/pull/888">#888</a>).</li> </ul> <h2 id="220---2025-09-14"><a href="https://github.com/python-poetry/poetry/releases/tag/2.2.0">2.2.0</a> - 2025-09-14</h2> <h3 id="added-1">Added</h3> <ul> <li><strong>Add support for nesting dependency groups</strong> (<a href="https://github.com/python-poetry/poetry/pull/10166">#10166</a>).</li> <li><strong>Add support for PEP 735 dependency groups</strong> (<a href="https://github.com/python-poetry/poetry/pull/10130">#10130</a>).</li> <li><strong>Add support for PEP 639 license clarity</strong> (<a href="https://github.com/python-poetry/poetry/pull/10413">#10413</a>).</li> <li>Add a <code>--format</code> option to <code>poetry show</code> to alternatively output json format (<a href="https://github.com/python-poetry/poetry/pull/10487">#10487</a>).</li> <li>Add official support for Python 3.14 (<a href="https://github.com/python-poetry/poetry/pull/10514">#10514</a>).</li> </ul> <h3 id="changed-2">Changed</h3> <ul> <li><strong>Normalize dependency group names</strong> (<a href="https://github.com/python-poetry/poetry/pull/10387">#10387</a>).</li> <li>Change <code>installer.no-binary</code> and <code>installer.only-binary</code> so that explicit package names will take precedence over <code>:all:</code> (<a href="https://github.com/python-poetry/poetry/pull/10278">#10278</a>).</li> <li>Improve log output during <code>poetry install</code> when a wheel is built from source (<a href="https://github.com/python-poetry/poetry/pull/10404">#10404</a>).</li> <li>Improve error message in case a file lock could not be acquired while cloning a git repository (<a href="https://github.com/python-poetry/poetry/pull/10535">#10535</a>).</li> <li>Require <code>dulwich&gt;=0.24.0</code> (<a href="https://github.com/python-poetry/poetry/pull/10492">#10492</a>).</li> <li>Allow <code>virtualenv&gt;=20.33</code> again (<a href="https://github.com/python-poetry/poetry/pull/10506">#10506</a>).</li> <li>Allow <code>findpython&gt;=0.7</code> (<a href="https://github.com/python-poetry/poetry/pull/10510">#10510</a>).</li> <li>Allow <code>importlib-metadata&gt;=8.7</code> (<a href="https://github.com/python-poetry/poetry/pull/10511">#10511</a>).</li> </ul> <h3 id="fixed-5">Fixed</h3> <ul> <li>Fix an issue where <code>poetry new</code> did not create the project structure in an existing empty directory (<a href="https://github.com/python-poetry/poetry/pull/10431">#10431</a>).</li> <li>Fix an issue where a dependency that was required for a specific Python version was not installed into an environment of a pre-release Python version (<a href="https://github.com/python-poetry/poetry/pull/10516">#10516</a>).</li> </ul> <h3 id="poetry-core-220httpsgithubcompython-poetrypoetry-corereleasestag220">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/2.2.0"><code>2.2.0</code></a>)</h3> <ul> <li>Deprecate table values and values that are not valid SPDX expressions for <code>[project.license]</code> (<a href="https://github.com/python-poetry/poetry-core/pull/870">#870</a>).</li> <li>Fix an issue where explicitly included files that are in <code>.gitignore</code> were not included in the distribution (<a href="https://github.com/python-poetry/poetry-core/pull/874">#874</a>).</li> <li>Fix an issue where marker operations could result in invalid markers (<a href="https://github.com/python-poetry/poetry-core/pull/875">#875</a>).</li> </ul> <h2 id="214---2025-08-05"><a href="https://github.com/python-poetry/poetry/releases/tag/2.1.4">2.1.4</a> - 2025-08-05</h2> <h3 id="changed-3">Changed</h3> <ul> <li>Require <code>virtualenv&lt;20.33</code> to work around an issue where Poetry uses the wrong Python version (<a href="https://github.com/python-poetry/poetry/pull/10491">#10491</a>).</li> <li>Improve the error messages for the validation of the <code>pyproject.toml</code> file (<a href="https://github.com/python-poetry/poetry/pull/10471">#10471</a>).</li> </ul> <h3 id="fixed-6">Fixed</h3> <ul> <li>Fix an issue where project plugins were installed even though <code>poetry install</code> was called with <code>--no-plugins</code> (<a href="https://github.com/python-poetry/poetry/pull/10405">#10405</a>).</li> <li>Fix an issue where dependency resolution failed for self-referential extras with duplicate dependencies (<a href="https://github.com/python-poetry/poetry/pull/10488">#10488</a>).</li> </ul> <h3 id="docs-4">Docs</h3> <ul> <li>Clarify how to include files that were automatically excluded via VCS ignore settings (<a href="https://github.com/python-poetry/poetry/pull/10442">#10442</a>).</li> <li>Clarify the behavior of <code>poetry add</code> if no version constraint is explicitly specified (<a href="https://github.com/python-poetry/poetry/pull/10445">#10445</a>).</li> </ul> <h2 id="213---2025-05-04"><a href="https://github.com/python-poetry/poetry/releases/tag/2.1.3">2.1.3</a> - 2025-05-04</h2> <h3 id="changed-4">Changed</h3> <ul> <li>Require <code>importlib-metadata&lt;8.7</code> for Python 3.9 because of a breaking change in importlib-metadata 8.7 (<a href="https://github.com/python-poetry/poetry/pull/10374">#10374</a>).</li> </ul> <h3 id="fixed-7">Fixed</h3> <ul> <li>Fix an issue where re-locking failed for incomplete multiple-constraints dependencies with explicit sources (<a href="https://github.com/python-poetry/poetry/pull/10324">#10324</a>).</li> <li>Fix an issue where the <code>--directory</code> option did not work if a plugin, which accesses the poetry instance during its activation, was installed (<a href="https://github.com/python-poetry/poetry/pull/10352">#10352</a>).</li> <li>Fix an issue where <code>poetry env activate -v</code> printed additional information to stdout instead of stderr so that the output could not be used as designed (<a href="https://github.com/python-poetry/poetry/pull/10353">#10353</a>).</li> <li>Fix an issue where the original error was not printed if building a git dependency failed (<a href="https://github.com/python-poetry/poetry/pull/10366">#10366</a>).</li> <li>Fix an issue where wheels for the wrong platform were installed in rare cases. (<a href="https://github.com/python-poetry/poetry/pull/10361">#10361</a>).</li> </ul> <h3 id="poetry-core-213httpsgithubcompython-poetrypoetry-corereleasestag213">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/2.1.3"><code>2.1.3</code></a>)</h3> <ul> <li>Fix an issue where the union of specific inverse or partially inverse markers was not simplified (<a href="https://github.com/python-poetry/poetry-core/pull/858">#858</a>).</li> <li>Fix an issue where optional dependencies defined in the <code>project</code> section were treated as non-optional when a source was defined for them in the <code>tool.poetry</code> section (<a href="https://github.com/python-poetry/poetry-core/pull/857">#857</a>).</li> <li>Fix an issue where markers with <code>===</code> were not parsed correctly (<a href="https://github.com/python-poetry/poetry-core/pull/860">#860</a>).</li> <li>Fix an issue where local versions with upper case letters caused an error (<a href="https://github.com/python-poetry/poetry-core/pull/859">#859</a>).</li> <li>Fix an issue where <code>extra</code> markers with a value starting with &ldquo;in&rdquo; were not validated correctly (<a href="https://github.com/python-poetry/poetry-core/pull/862">#862</a>).</li> </ul> <h2 id="212---2025-03-29"><a href="https://github.com/python-poetry/poetry/releases/tag/2.1.2">2.1.2</a> - 2025-03-29</h2> <h3 id="changed-5">Changed</h3> <ul> <li>Improve performance of locking dependencies (<a href="https://github.com/python-poetry/poetry/pull/10275">#10275</a>).</li> </ul> <h3 id="fixed-8">Fixed</h3> <ul> <li>Fix an issue where markers were not locked correctly (<a href="https://github.com/python-poetry/poetry/pull/10240">#10240</a>).</li> <li>Fix an issue where the result of <code>poetry lock</code> was not deterministic (<a href="https://github.com/python-poetry/poetry/pull/10276">#10276</a>).</li> <li>Fix an issue where <code>poetry env activate</code> returned the wrong command for <code>tcsh</code> (<a href="https://github.com/python-poetry/poetry/pull/10243">#10243</a>).</li> <li>Fix an issue where <code>poetry env activate</code> returned the wrong command for <code>pwsh</code> on Linux (<a href="https://github.com/python-poetry/poetry/pull/10256">#10256</a>).</li> </ul> <h3 id="docs-5">Docs</h3> <ul> <li>Update basic usage section to reflect new default layout (<a href="https://github.com/python-poetry/poetry/pull/10203">#10203</a>).</li> </ul> <h3 id="poetry-core-212httpsgithubcompython-poetrypoetry-corereleasestag212">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/2.1.2"><code>2.1.2</code></a>)</h3> <ul> <li>Improve performance of marker operations (<a href="https://github.com/python-poetry/poetry-core/pull/851">#851</a>).</li> <li>Fix an issue where incorrect markers were calculated when removing parts covered by the project&rsquo;s Python constraint (<a href="https://github.com/python-poetry/poetry-core/pull/841">#841</a>, <a href="https://github.com/python-poetry/poetry-core/pull/846">#846</a>).</li> <li>Fix an issue where <code>extra</code> markers were not simplified (<a href="https://github.com/python-poetry/poetry-core/pull/842">#842</a>, <a href="https://github.com/python-poetry/poetry-core/pull/845">#845</a>, <a href="https://github.com/python-poetry/poetry-core/pull/847">#847</a>).</li> <li>Fix an issue where the intersection and union of markers was not deterministic (<a href="https://github.com/python-poetry/poetry-core/pull/843">#843</a>).</li> <li>Fix an issue where the intersection of <code>python_version</code> markers was not recognized as empty (<a href="https://github.com/python-poetry/poetry-core/pull/849">#849</a>).</li> <li>Fix an issue where <code>python_version</code> markers were not simplified (<a href="https://github.com/python-poetry/poetry-core/pull/848">#848</a>, <a href="https://github.com/python-poetry/poetry-core/pull/851">#851</a>).</li> <li>Fix an issue where Python constraints on a package were converted into invalid markers (<a href="https://github.com/python-poetry/poetry-core/pull/853">#853</a>).</li> </ul> <h2 id="211---2025-02-16"><a href="https://github.com/python-poetry/poetry/releases/tag/2.1.1">2.1.1</a> - 2025-02-16</h2> <h3 id="fixed-9">Fixed</h3> <ul> <li>Fix an issue where <code>poetry env use python</code> does not choose the Python from the PATH (<a href="https://github.com/python-poetry/poetry/pull/10187">#10187</a>).</li> </ul> <h3 id="poetry-core-211httpsgithubcompython-poetrypoetry-corereleasestag211">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/2.1.1"><code>2.1.1</code></a>)</h3> <ul> <li>Fix an issue where simplifying a <code>python_version</code> marker resulted in an invalid marker (<a href="https://github.com/python-poetry/poetry-core/pull/838">#838</a>).</li> </ul> <h2 id="210---2025-02-15"><a href="https://github.com/python-poetry/poetry/releases/tag/2.1.0">2.1.0</a> - 2025-02-15</h2> <h3 id="added-2">Added</h3> <ul> <li><strong>Make <code>build</code> command build-system agnostic</strong> (<a href="https://github.com/python-poetry/poetry/pull/10059">#10059</a>, <a href="https://github.com/python-poetry/poetry/pull/10092">#10092</a>).</li> <li>Add a <code>--config-settings</code> option to <code>poetry build</code> (<a href="https://github.com/python-poetry/poetry/pull/10059">#10059</a>).</li> <li>Add support for defining <code>config-settings</code> when building dependencies (<a href="https://github.com/python-poetry/poetry/pull/10129">#10129</a>).</li> <li><strong>Add (experimental) commands to manage Python installations</strong> (<a href="https://github.com/python-poetry/poetry/pull/10112">#10112</a>).</li> <li>Use <code>findpython</code> to find the Python interpreters (<a href="https://github.com/python-poetry/poetry/pull/10097">#10097</a>).</li> <li>Add a <code>--no-truncate</code> option to <code>poetry show</code> (<a href="https://github.com/python-poetry/poetry/pull/9580">#9580</a>).</li> <li>Re-add support for passwords with empty usernames (<a href="https://github.com/python-poetry/poetry/pull/10088">#10088</a>).</li> <li>Add better error messages (<a href="https://github.com/python-poetry/poetry/pull/10053">#10053</a>, <a href="https://github.com/python-poetry/poetry/pull/10065">#10065</a>, <a href="https://github.com/python-poetry/poetry/pull/10126">#10126</a>, <a href="https://github.com/python-poetry/poetry/pull/10127">#10127</a>, <a href="https://github.com/python-poetry/poetry/pull/10132">#10132</a>).</li> </ul> <h3 id="changed-6">Changed</h3> <ul> <li><strong><code>poetry new</code> defaults to &ldquo;src&rdquo; layout by default</strong> (<a href="https://github.com/python-poetry/poetry/pull/10135">#10135</a>).</li> <li>Improve performance of locking dependencies (<a href="https://github.com/python-poetry/poetry/pull/10111">#10111</a>, <a href="https://github.com/python-poetry/poetry/pull/10114">#10114</a>, <a href="https://github.com/python-poetry/poetry/pull/10138">#10138</a>, <a href="https://github.com/python-poetry/poetry/pull/10146">#10146</a>).</li> <li>Deprecate adding sources without specifying <code>--priority</code> (<a href="https://github.com/python-poetry/poetry/pull/10134">#10134</a>).</li> </ul> <h3 id="fixed-10">Fixed</h3> <ul> <li>Fix an issue where global options were not handled correctly when positioned after command options (<a href="https://github.com/python-poetry/poetry/pull/10021">#10021</a>, <a href="https://github.com/python-poetry/poetry/pull/10067">#10067</a>, <a href="https://github.com/python-poetry/poetry/pull/10128">#10128</a>).</li> <li>Fix an issue where building a dependency from source failed because of a conflict between build-system dependencies that were not required for the target environment (<a href="https://github.com/python-poetry/poetry/pull/10048">#10048</a>).</li> <li>Fix an issue where <code>poetry init</code> was not able to find a package on PyPI while adding dependencies interactively (<a href="https://github.com/python-poetry/poetry/pull/10055">#10055</a>).</li> <li>Fix an issue where the <code>@latest</code> descriptor was incorrectly passed to the core requirement parser (<a href="https://github.com/python-poetry/poetry/pull/10069">#10069</a>).</li> <li>Fix an issue where Boolean environment variables set to <code>True</code> (in contrast to <code>true</code>) were interpreted as <code>false</code> (<a href="https://github.com/python-poetry/poetry/pull/10080">#10080</a>).</li> <li>Fix an issue where <code>poetry env activate</code> reported a misleading error message (<a href="https://github.com/python-poetry/poetry/pull/10087">#10087</a>).</li> <li>Fix an issue where adding an optional dependency with <code>poetry add --optional</code> would not correctly update the lock file (<a href="https://github.com/python-poetry/poetry/pull/10076">#10076</a>).</li> <li>Fix an issue where <code>pip</code> was not installed/updated before other dependencies resulting in a race condition (<a href="https://github.com/python-poetry/poetry/pull/10102">#10102</a>).</li> <li>Fix an issue where Poetry freezes when multiple threads attempt to unlock the <code>keyring</code> simultaneously (<a href="https://github.com/python-poetry/poetry/pull/10062">#10062</a>).</li> <li>Fix an issue where markers with extras were not locked correctly (<a href="https://github.com/python-poetry/poetry/pull/10119">#10119</a>).</li> <li>Fix an issue where self-referential extras were not resolved correctly (<a href="https://github.com/python-poetry/poetry/pull/10106">#10106</a>).</li> <li>Fix an issue where Poetry could not be run from a <code>zipapp</code> (<a href="https://github.com/python-poetry/poetry/pull/10074">#10074</a>).</li> <li>Fix an issue where installation failed with a permission error when using the system environment as a user without write access to system site packages (<a href="https://github.com/python-poetry/poetry/pull/9014">#9014</a>).</li> <li>Fix an issue where a version of a dependency that is not compatible with the project&rsquo;s python constraint was locked. (<a href="https://github.com/python-poetry/poetry/pull/10141">#10141</a>).</li> <li>Fix an issue where Poetry wrongly reported that the current project&rsquo;s supported Python range is not compatible with some of the required packages Python requirement (<a href="https://github.com/python-poetry/poetry/pull/10157">#10157</a>).</li> <li>Fix an issue where the requested extras of a dependency were ignored if the same dependency (with same extras) was specified in multiple groups (<a href="https://github.com/python-poetry/poetry/pull/10158">#10158</a>).</li> </ul> <h3 id="docs-6">Docs</h3> <ul> <li>Sort commands by name in the CLI reference (<a href="https://github.com/python-poetry/poetry/pull/10035">#10035</a>).</li> <li>Add missing documentation for <code>env</code> commands (<a href="https://github.com/python-poetry/poetry/pull/10027">#10027</a>).</li> <li>Clarify that the <code>name</code> and <code>version</code> fields are always required if the <code>project</code> section is specified (<a href="https://github.com/python-poetry/poetry/pull/10033">#10033</a>).</li> <li>Add a note about restarting the shell for tab completion changes to take effect (<a href="https://github.com/python-poetry/poetry/pull/10070">#10070</a>).</li> <li>Fix the example for <code>project.gui-scripts</code> <a href="https://github.com/python-poetry/poetry/pull/10121">#10121</a>.</li> <li>Explain how to include files as scripts in the project configuration (<a href="https://github.com/python-poetry/poetry/pull/9572">#9572</a>, <a href="https://github.com/python-poetry/poetry/pull/10133">#10133</a>).</li> <li>Add additional information on specifying required python versions (<a href="https://github.com/python-poetry/poetry/pull/10104">#10104</a>).</li> </ul> <h3 id="poetry-core-210httpsgithubcompython-poetrypoetry-corereleasestag210">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/2.1.0"><code>2.1.0</code></a>)</h3> <ul> <li>Fix an issue where inclusive ordering with post releases was inconsistent with PEP 440 (<a href="https://github.com/python-poetry/poetry-core/pull/379">#379</a>).</li> <li>Fix an issue where invalid URI tokens in PEP 508 requirement strings were silently discarded (<a href="https://github.com/python-poetry/poetry-core/pull/817">#817</a>).</li> <li>Fix an issue where wrong markers were calculated when removing parts covered by the project&rsquo;s python constraint (<a href="https://github.com/python-poetry/poetry-core/pull/824">#824</a>).</li> <li>Fix an issue where optional dependencies that are not part of an extra were included in the wheel metadata (<a href="https://github.com/python-poetry/poetry-core/pull/830">#830</a>).</li> <li>Fix an issue where the <code>__pycache__</code> directory and <code>*.pyc</code> files were included in sdists and wheels (<a href="https://github.com/python-poetry/poetry-core/pull/835">#835</a>).</li> </ul> <h2 id="201---2025-01-11"><a href="https://github.com/python-poetry/poetry/releases/tag/2.0.1">2.0.1</a> - 2025-01-11</h2> <h3 id="added-3">Added</h3> <ul> <li>Add support for <code>poetry search</code> in legacy sources (<a href="https://github.com/python-poetry/poetry/pull/9949">#9949</a>).</li> <li>Add a message in the <code>poetry source show</code> output when PyPI is implicitly enabled (<a href="https://github.com/python-poetry/poetry/pull/9974">#9974</a>).</li> </ul> <h3 id="changed-7">Changed</h3> <ul> <li>Improve performance for merging markers from overrides at the end of dependency resolution (<a href="https://github.com/python-poetry/poetry/pull/10018">#10018</a>).</li> </ul> <h3 id="fixed-11">Fixed</h3> <ul> <li>Fix an issue where <code>poetry sync</code> did not remove packages that were not requested (<a href="https://github.com/python-poetry/poetry/pull/9946">#9946</a>).</li> <li>Fix an issue where <code>poetry check</code> failed even though there were just warnings and add a <code>--strict</code> option to fail on warnings (<a href="https://github.com/python-poetry/poetry/pull/9983">#9983</a>).</li> <li>Fix an issue where <code>poetry update</code>, <code>poetry add</code> and <code>poetry remove</code> with <code>--only</code> uninstalled packages from other groups (<a href="https://github.com/python-poetry/poetry/pull/10014">#10014</a>).</li> <li>Fix an issue where <code>poetry update</code>, <code>poetry add</code> and <code>poetry remove</code> uninstalled all extra packages (<a href="https://github.com/python-poetry/poetry/pull/10016">#10016</a>).</li> <li>Fix an issue where <code>poetry self update</code> did not recognize Poetry&rsquo;s own environment (<a href="https://github.com/python-poetry/poetry/pull/9995">#9995</a>).</li> <li>Fix an issue where read-only system site-packages were not considered when loading an environment with system site-packages (<a href="https://github.com/python-poetry/poetry/pull/9942">#9942</a>).</li> <li>Fix an issue where an error message in <code>poetry install</code> started with <code>Warning:</code> instead of <code>Error:</code> (<a href="https://github.com/python-poetry/poetry/pull/9945">#9945</a>).</li> <li>Fix an issue where <code>Command.set_poetry</code>, which is used by plugins, was removed (<a href="https://github.com/python-poetry/poetry/pull/9981">#9981</a>).</li> <li>Fix an issue where the help text of <code>poetry build --clean</code> showed a malformed short option instead of the description (<a href="https://github.com/python-poetry/poetry/pull/9994">#9994</a>).</li> </ul> <h3 id="docs-7">Docs</h3> <ul> <li>Add a FAQ entry for the migration from Poetry-specific fields to the <code>project</code> section (<a href="https://github.com/python-poetry/poetry/pull/9996">#9996</a>).</li> <li>Fix examples for <code>project.readme</code> and <code>project.urls</code> (<a href="https://github.com/python-poetry/poetry/pull/9948">#9948</a>).</li> <li>Add a warning that package sources are a Poetry-specific feature that is not included in core metadata (<a href="https://github.com/python-poetry/poetry/pull/9935">#9935</a>).</li> <li>Replace <code>poetry install --sync</code> with <code>poetry sync</code> in the section about synchronizing dependencies (<a href="https://github.com/python-poetry/poetry/pull/9944">#9944</a>).</li> <li>Replace <code>poetry shell</code> with <code>poetry env activate</code> in the basic usage section (<a href="https://github.com/python-poetry/poetry/pull/9963">#9963</a>).</li> <li>Mention that <code>project.name</code> is always required when the <code>project</code> section is used (<a href="https://github.com/python-poetry/poetry/pull/9989">#9989</a>).</li> <li>Fix the constraint of <code>poetry-plugin-export</code> in the section about <code>poetry export</code> (<a href="https://github.com/python-poetry/poetry/pull/9954">#9954</a>).</li> </ul> <h3 id="poetry-core-201httpsgithubcompython-poetrypoetry-corereleasestag201">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/2.0.1"><code>2.0.1</code></a>)</h3> <ul> <li>Replace the deprecated core metadata field <code>Home-page</code> with <code>Project-URL: Homepage</code> (<a href="https://github.com/python-poetry/poetry-core/pull/807">#807</a>).</li> <li>Fix an issue where includes from <code>tool.poetry.packages</code> without a specified <code>format</code> were not initialized with the default value resulting in a <code>KeyError</code> (<a href="https://github.com/python-poetry/poetry-core/pull/805">#805</a>).</li> <li>Fix an issue where some <code>project.urls</code> entries were not processed correctly resulting in a <code>KeyError</code> (<a href="https://github.com/python-poetry/poetry-core/pull/807">#807</a>).</li> <li>Fix an issue where dynamic <code>project.dependencies</code> via <code>tool.poetry.dependencies</code> were ignored if <code>project.optional-dependencies</code> were defined (<a href="https://github.com/python-poetry/poetry-core/pull/811">#811</a>).</li> </ul> <h2 id="200---2025-01-05"><a href="https://github.com/python-poetry/poetry/releases/tag/2.0.0">2.0.0</a> - 2025-01-05</h2> <h3 id="added-4">Added</h3> <ul> <li><strong>Add support for the <code>project</code> section in the <code>pyproject.toml</code> file according to PEP 621</strong> (<a href="https://github.com/python-poetry/poetry/pull/9135">#9135</a>, <a href="https://github.com/python-poetry/poetry/pull/9917">#9917</a>).</li> <li><strong>Add support for defining Poetry plugins that are required by the project and automatically installed if not present</strong> (<a href="https://github.com/python-poetry/poetry/pull/9547">#9547</a>).</li> <li><strong>Lock resulting markers and groups and add a <code>installer.re-resolve</code> option (default: <code>true</code>) to allow installation without re-resolving</strong> (<a href="https://github.com/python-poetry/poetry/pull/9427">#9427</a>).</li> <li>Add a <code>--local-version</code> option to <code>poetry build</code> (<a href="https://github.com/python-poetry/poetry/pull/9064">#9064</a>).</li> <li>Add a <code>--clean</code> option to <code>poetry build</code> (<a href="https://github.com/python-poetry/poetry/pull/9067">#9067</a>).</li> <li>Add FIPS support for <code>poetry publish</code> (<a href="https://github.com/python-poetry/poetry/pull/9101">#9101</a>).</li> <li>Add the option to use <code>poetry new</code> interactively and configure more fields (<a href="https://github.com/python-poetry/poetry/pull/9101">#9101</a>).</li> <li>Add a config option <code>installer.only-binary</code> to enforce the use of binary distribution formats (<a href="https://github.com/python-poetry/poetry/pull/9150">#9150</a>).</li> <li>Add backend support for legacy repository search (<a href="https://github.com/python-poetry/poetry/pull/9132">#9132</a>).</li> <li>Add support to resume downloads from connection resets (<a href="https://github.com/python-poetry/poetry/pull/9422">#9422</a>).</li> <li>Add the option to define a constraint for the required Poetry version to manage the project (<a href="https://github.com/python-poetry/poetry/pull/9547">#9547</a>).</li> <li>Add an <code>--all-groups</code> option to <code>poetry install</code> (<a href="https://github.com/python-poetry/poetry/pull/9744">#9744</a>).</li> <li>Add an <code>poetry env activate</code> command as replacement of <code>poetry shell</code> (<a href="https://github.com/python-poetry/poetry/pull/9763">#9763</a>).</li> <li>Add a <code>--markers</code> option to <code>poetry add</code> to add a dependency with markers (<a href="https://github.com/python-poetry/poetry/pull/9814">#9814</a>).</li> <li>Add a <code>--migrate</code> option to <code>poetry config</code> to migrate outdated configs (<a href="https://github.com/python-poetry/poetry/pull/9830">#9830</a>).</li> <li>Add a <code>--project</code> option to search the <code>pyproject.toml</code> file in another directory without switching the directory (<a href="https://github.com/python-poetry/poetry/pull/9831">#9831</a>).</li> <li>Add support for shortened hashes to define git dependencies (<a href="https://github.com/python-poetry/poetry/pull/9748">#9748</a>).</li> <li>Add partial support for conflicting extras (<a href="https://github.com/python-poetry/poetry/pull/9553">#9553</a>).</li> <li>Add a <code>poetry sync</code> command as replacement of <code>poetry install --sync</code> (<a href="https://github.com/python-poetry/poetry/pull/9801">#9801</a>).</li> </ul> <h3 id="changed-8">Changed</h3> <ul> <li><strong>Change the default behavior of <code>poetry lock</code> to <code>--no-update</code> and introduce a <code>--regenerate</code> option for the old default behavior</strong> (<a href="https://github.com/python-poetry/poetry/pull/9327">#9327</a>).</li> <li><strong>Remove the dependency on <code>poetry-plugin-export</code> so that <code>poetry export</code> is not included per default</strong> (<a href="https://github.com/python-poetry/poetry/pull/5980">#5980</a>).</li> <li><strong>Outsource <code>poetry shell</code> into <code>poetry-plugin-shell</code></strong> (<a href="https://github.com/python-poetry/poetry/pull/9763">#9763</a>).</li> <li><strong>Change the interface of <code>poetry add --optional</code> to require an extra the optional dependency is added to</strong> (<a href="https://github.com/python-poetry/poetry/pull/9135">#9135</a>).</li> <li><strong>Actually switch the directory when using <code>--directory</code>/<code>-C</code></strong> (<a href="https://github.com/python-poetry/poetry/pull/9831">#9831</a>).</li> <li><strong>Drop support for Python 3.8</strong> (<a href="https://github.com/python-poetry/poetry/pull/9692">#9692</a>).</li> <li>Rename <code>experimental.system-git-client</code> to <code>experimental.system-git</code> (<a href="https://github.com/python-poetry/poetry/pull/9787">#9787</a>, <a href="https://github.com/python-poetry/poetry/pull/9795">#9795</a>).</li> <li>Replace <code>virtualenvs.prefer-active-python</code> by the inverse setting <code>virtualenvs.use-poetry-python</code> and prefer the active Python by default (<a href="https://github.com/python-poetry/poetry/pull/9786">#9786</a>).</li> <li>Deprecate several fields in the <code>tool.poetry</code> section in favor of the respective fields in the <code>project</code> section in the <code>pyproject.toml</code> file (<a href="https://github.com/python-poetry/poetry/pull/9135">#9135</a>).</li> <li>Deprecate <code>poetry install --sync</code> in favor of <code>poetry sync</code> (<a href="https://github.com/python-poetry/poetry/pull/9801">#9801</a>).</li> <li>Upgrade the warning if the current project cannot be installed to an error (<a href="https://github.com/python-poetry/poetry/pull/9333">#9333</a>).</li> <li>Remove special handling for <code>platformdirs 2.0</code> macOS config directory (<a href="https://github.com/python-poetry/poetry/pull/8916">#8916</a>).</li> <li>Tweak PEP 517 builds (<a href="https://github.com/python-poetry/poetry/pull/9094">#9094</a>).</li> <li>Use Poetry instead of pip to manage dependencies in isolated build environments (<a href="https://github.com/python-poetry/poetry/pull/9168">#9168</a>, <a href="https://github.com/python-poetry/poetry/pull/9227">#9227</a>).</li> <li>Trust empty <code>Requires-Dist</code> with modern metadata (<a href="https://github.com/python-poetry/poetry/pull/9078">#9078</a>).</li> <li>Do PEP 517 builds instead of parsing <code>setup.py</code> to determine dependencies (<a href="https://github.com/python-poetry/poetry/pull/9099">#9099</a>).</li> <li>Drop support for reading lock files prior version 1.0 (created with Poetry prior 1.1) (<a href="https://github.com/python-poetry/poetry/pull/9345">#9345</a>).</li> <li>Default to <code>&gt;=</code> instead of <code>^</code> for the Python requirement when initializing a new project (<a href="https://github.com/python-poetry/poetry/pull/9558">#9558</a>).</li> <li>Limit <code>build-system</code> to the current major version of <code>poetry-core</code> when initializing a new project (<a href="https://github.com/python-poetry/poetry/pull/9812">#9812</a>).</li> <li>Remove pip-based installation, i.e. <code>installer.modern-installation = false</code> (<a href="https://github.com/python-poetry/poetry/pull/9392">#9392</a>).</li> <li>Remove <code>virtualenvs.options.no-setuptools</code> config option and never include <code>setuptools</code> per default (<a href="https://github.com/python-poetry/poetry/pull/9331">#9331</a>).</li> <li>Rename exceptions to have an <code>Error</code> suffix (<a href="https://github.com/python-poetry/poetry/pull/9705">#9705</a>).</li> <li>Remove deprecated CLI options and methods and revoke the deprecation of <code>--dev</code> (<a href="https://github.com/python-poetry/poetry/pull/9732">#9732</a>).</li> <li>Ignore installed packages during dependency resolution (<a href="https://github.com/python-poetry/poetry/pull/9851">#9851</a>).</li> <li>Improve the error message on upload failure (<a href="https://github.com/python-poetry/poetry/pull/9701">#9701</a>).</li> <li>Improve the error message if the current project cannot be installed to include another root cause (<a href="https://github.com/python-poetry/poetry/pull/9651">#9651</a>).</li> <li>Improve the output of <code>poetry show &lt;package&gt;</code> (<a href="https://github.com/python-poetry/poetry/pull/9750">#9750</a>).</li> <li>Improve the error message for build errors (<a href="https://github.com/python-poetry/poetry/pull/9870">#9870</a>).</li> <li>Improve the error message when trying to remove a package from a project without any dependencies (<a href="https://github.com/python-poetry/poetry/pull/9918">#9918</a>).</li> <li>Drop the direct dependency on <code>crashtest</code> (<a href="https://github.com/python-poetry/poetry/pull/9108">#9108</a>).</li> <li>Require <code>keyring&gt;=23.3.1</code> (<a href="https://github.com/python-poetry/poetry/pull/9167">#9167</a>).</li> <li>Require <code>build&gt;=1.2.1</code> (<a href="https://github.com/python-poetry/poetry/pull/9283">#9283</a>).</li> <li>Require <code>dulwich&gt;=0.22.6</code> (<a href="https://github.com/python-poetry/poetry/pull/9748">#9748</a>).</li> </ul> <h3 id="fixed-12">Fixed</h3> <ul> <li>Fix an issue where git dependencies with extras could only be cloned if a branch was specified explicitly (<a href="https://github.com/python-poetry/poetry/pull/7028">#7028</a>).</li> <li>Fix an issue where <code>poetry env remove</code> failed if <code>virtualenvs.in-project</code> was set to <code>true</code> (<a href="https://github.com/python-poetry/poetry/pull/9118">#9118</a>).</li> <li>Fix an issue where locking packages with a digit at the end of the name and non-standard sdist names failed (<a href="https://github.com/python-poetry/poetry/pull/9189">#9189</a>).</li> <li>Fix an issue where credentials where not passed when trying to download an URL dependency (<a href="https://github.com/python-poetry/poetry/pull/9202">#9202</a>).</li> <li>Fix an issue where using uncommon group names with <code>poetry add</code> resulted in a broken <code>pyproject.toml</code> (<a href="https://github.com/python-poetry/poetry/pull/9277">#9277</a>).</li> <li>Fix an issue where an inconsistent entry regarding the patch version of Python was kept in <code>envs.toml</code> (<a href="https://github.com/python-poetry/poetry/pull/9286">#9286</a>).</li> <li>Fix an issue where relative paths were not resolved properly when using <code>poetry build --directory</code> (<a href="https://github.com/python-poetry/poetry/pull/9433">#9433</a>).</li> <li>Fix an issue where unrequested extras were not uninstalled when running <code>poetry install</code> without an existing lock file (<a href="https://github.com/python-poetry/poetry/pull/9345">#9345</a>).</li> <li>Fix an issue where the <code>poetry-check</code> pre-commit hook did not trigger if only <code>poetry.lock</code> has changed (<a href="https://github.com/python-poetry/poetry/pull/9504">#9504</a>).</li> <li>Fix an issue where files (rather than directories) could not be added as single page source (<a href="https://github.com/python-poetry/poetry/pull/9166">#9166</a>).</li> <li>Fix an issue where invalid constraints were generated when adding a package with a local version specifier (<a href="https://github.com/python-poetry/poetry/pull/9603">#9603</a>).</li> <li>Fix several encoding warnings (<a href="https://github.com/python-poetry/poetry/pull/8893">#8893</a>).</li> <li>Fix an issue where <code>virtualenvs.prefer-active-python</code> was not respected (<a href="https://github.com/python-poetry/poetry/pull/9278">#9278</a>).</li> <li>Fix an issue where the line endings of the lock file were changed (<a href="https://github.com/python-poetry/poetry/pull/9468">#9468</a>).</li> <li>Fix an issue where installing multiple dependencies from the same git repository failed sporadically due to a race condition (<a href="https://github.com/python-poetry/poetry/pull/9658">#9658</a>).</li> <li>Fix an issue where installing multiple dependencies from forked monorepos failed sporadically due to a race condition (<a href="https://github.com/python-poetry/poetry/pull/9723">#9723</a>).</li> <li>Fix an issue where an extra package was not installed if it is required by multiple extras (<a href="https://github.com/python-poetry/poetry/pull/9700">#9700</a>).</li> <li>Fix an issue where a <code>direct_url.json</code> with vcs URLs not compliant with PEP 610 was written (<a href="https://github.com/python-poetry/poetry/pull/9007">#9007</a>).</li> <li>Fix an issue where other files than wheels were recognized as wheels (<a href="https://github.com/python-poetry/poetry/pull/9770">#9770</a>).</li> <li>Fix an issue where <code>installer.max-workers</code> was ignored for the implicit PyPI source (<a href="https://github.com/python-poetry/poetry/pull/9815">#9815</a>).</li> <li>Fix an issue where local settings (from <code>poetry.toml</code>) were ignored for the implicit PyPI source (<a href="https://github.com/python-poetry/poetry/pull/9816">#9816</a>).</li> <li>Fix an issue where different <code>dulwich</code> versions resulted in different hashes for a git dependency from a tag (<a href="https://github.com/python-poetry/poetry/pull/9849">#9849</a>).</li> <li>Fix an issue where installing a yanked package with no dependencies failed with an <code>IndexError</code> (<a href="https://github.com/python-poetry/poetry/pull/9505">#9505</a>).</li> <li>Fix an issue where a package could not be added from a source that required an empty password (<a href="https://github.com/python-poetry/poetry/pull/9850">#9850</a>).</li> <li>Fix an issue where setting <code>allow-prereleases = false</code> still allowed pre-releases if no other solution was found (<a href="https://github.com/python-poetry/poetry/pull/9798">#9798</a>).</li> <li>Fix an issue where the wrong environment was used for checking if an installed package is from system site packages (<a href="https://github.com/python-poetry/poetry/pull/9861">#9861</a>).</li> <li>Fix an issue where build errors from builds to retrieve metadata information were hidden (<a href="https://github.com/python-poetry/poetry/pull/9870">#9870</a>).</li> <li>Fix an issue where <code>poetry check</code> falsely reported that an invalid source &ldquo;pypi&rdquo; is referenced in dependencies (<a href="https://github.com/python-poetry/poetry/pull/9475">#9475</a>).</li> <li>Fix an issue where <code>poetry install --sync</code> tried to uninstall system site packages if the virtual environment was created with <code>virtualenvs.options.system-site-packages = true</code> (<a href="https://github.com/python-poetry/poetry/pull/9863">#9863</a>).</li> <li>Fix an issue where HTTP streaming requests were not closed properly when not completely consumed (<a href="https://github.com/python-poetry/poetry/pull/9899">#9899</a>).</li> </ul> <h3 id="docs-8">Docs</h3> <ul> <li>Add information about getting test coverage in the contribution guide (<a href="https://github.com/python-poetry/poetry/pull/9726">#9726</a>).</li> <li>Mention <code>pre-commit-update</code> as an alternative to <code>pre-commit autoupdate</code> (<a href="https://github.com/python-poetry/poetry/pull/9716">#9716</a>).</li> <li>Improve the explanation of <code>exclude</code> and <code>include</code> (<a href="https://github.com/python-poetry/poetry/pull/9734">#9734</a>).</li> <li>Add information about compatible release requirements, i.e. <code>~=</code> (<a href="https://github.com/python-poetry/poetry/pull/9783">#9783</a>).</li> <li>Add documentation for using a build script to build extension modules (<a href="https://github.com/python-poetry/poetry/pull/9864">#9864</a>).</li> </ul> <h3 id="poetry-core-200httpsgithubcompython-poetrypoetry-corereleasestag200">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/2.0.0"><code>2.0.0</code></a>)</h3> <ul> <li>Add support for non PEP440 compliant version in the <code>platform_release</code> marker (<a href="https://github.com/python-poetry/poetry-core/pull/722">#722</a>).</li> <li>Add support for string comparisons with <code>in</code> / <code>not in</code> in generic constraints (<a href="https://github.com/python-poetry/poetry-core/pull/722">#722</a>).</li> <li>Add support for script files that are generated by a build script (<a href="https://github.com/python-poetry/poetry-core/pull/710">#710</a>).</li> <li>Add support for <code>SOURCE_DATE_EPOCH</code> when building packages (<a href="https://github.com/python-poetry/poetry-core/pull/766">#766</a>, <a href="https://github.com/python-poetry/poetry-core/pull/781">#781</a>).</li> <li>Create <code>METADATA</code> files with version 2.3 instead of 2.2 (<a href="https://github.com/python-poetry/poetry-core/pull/707">#707</a>).</li> <li>Remove support for <code>x</code> in version constraints (<a href="https://github.com/python-poetry/poetry-core/pull/770">#770</a>).</li> <li>Remove support for scripts with extras (<a href="https://github.com/python-poetry/poetry-core/pull/708">#708</a>).</li> <li>Remove deprecated features and interfaces (<a href="https://github.com/python-poetry/poetry-core/pull/702">#702</a>, <a href="https://github.com/python-poetry/poetry-core/pull/769">#769</a>).</li> <li>Deprecate <code>tool.poetry.dev-dependencies</code> in favor of <code>tool.poetry.group.dev.dependencies</code> (<a href="https://github.com/python-poetry/poetry-core/pull/754">#754</a>).</li> <li>Fix an issue where the <code>platlib</code> directory of the wrong Python was used (<a href="https://github.com/python-poetry/poetry-core/pull/726">#726</a>).</li> <li>Fix an issue where building a wheel in a nested output directory results in an error (<a href="https://github.com/python-poetry/poetry-core/pull/762">#762</a>).</li> <li>Fix an issue where <code>+</code> was not allowed in git URL paths (<a href="https://github.com/python-poetry/poetry-core/pull/765">#765</a>).</li> <li>Fix an issue where the temporary directory was not cleaned up on error (<a href="https://github.com/python-poetry/poetry-core/pull/775">#775</a>).</li> <li>Fix an issue where the regular expression for author names was too restrictive (<a href="https://github.com/python-poetry/poetry-core/pull/517">#517</a>).</li> <li>Fix an issue where basic auth http(s) credentials could not be parsed (<a href="https://github.com/python-poetry/poetry-core/pull/791">#791</a>).</li> </ul> <h2 id="185---2024-12-06"><a href="https://github.com/python-poetry/poetry/releases/tag/1.8.5">1.8.5</a> - 2024-12-06</h2> <h3 id="changed-9">Changed</h3> <ul> <li>Require <code>pkginfo&gt;=1.12</code> to fix an issue with an unknown metadata version 2.4 (<a href="https://github.com/python-poetry/poetry/pull/9888">#9888</a>).</li> <li>Do not fail if the unknown metadata version is only a minor version update (<a href="https://github.com/python-poetry/poetry/pull/9888">#9888</a>).</li> </ul> <h2 id="184---2024-10-14"><a href="https://github.com/python-poetry/poetry/releases/tag/1.8.4">1.8.4</a> - 2024-10-14</h2> <h3 id="added-5">Added</h3> <ul> <li><strong>Add official support for Python 3.13</strong> (<a href="https://github.com/python-poetry/poetry/pull/9523">#9523</a>).</li> </ul> <h3 id="changed-10">Changed</h3> <ul> <li>Require <code>virtualenv&gt;=20.26.6</code> to mitigate potential command injection when running <code>poetry shell</code> in untrusted projects (<a href="https://github.com/python-poetry/poetry/pull/9757">#9757</a>).</li> </ul> <h3 id="poetry-core-191httpsgithubcompython-poetrypoetry-corereleasestag191">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/1.9.1"><code>1.9.1</code></a>)</h3> <ul> <li>Add <code>3.13</code> to the list of available Python versions (<a href="https://github.com/python-poetry/poetry-core/pull/747">#747</a>).</li> </ul> <h2 id="183---2024-05-08"><a href="https://github.com/python-poetry/poetry/releases/tag/1.8.3">1.8.3</a> - 2024-05-08</h2> <h3 id="added-6">Added</h3> <ul> <li>Add support for untagged CPython builds with versions ending with a <code>+</code> (<a href="https://github.com/python-poetry/poetry/pull/9207">#9207</a>).</li> </ul> <h3 id="changed-11">Changed</h3> <ul> <li>Require <code>pkginfo&gt;=1.10</code> to ensure support for packages with metadata version 2.3 (<a href="https://github.com/python-poetry/poetry/pull/9130">#9130</a>).</li> <li>Improve locking on FIPS systems (<a href="https://github.com/python-poetry/poetry/pull/9152">#9152</a>).</li> </ul> <h3 id="fixed-13">Fixed</h3> <ul> <li>Fix an issue where unrecognized package metadata versions silently resulted in empty dependencies (<a href="https://github.com/python-poetry/poetry/pull/9203">#9203</a>, <a href="https://github.com/python-poetry/poetry/pull/9226">#9226</a>).</li> <li>Fix an issue where trailing slashes in git URLs where not handled correctly (<a href="https://github.com/python-poetry/poetry/pull/9205">#9205</a>).</li> <li>Fix an issue where <code>poetry self</code> commands printed a warning that the current project cannot be installed (<a href="https://github.com/python-poetry/poetry/pull/9302">#9302</a>).</li> <li>Fix an issue where <code>poetry install</code> sporadically failed with a <code>KeyError</code> due to a race condition (<a href="https://github.com/python-poetry/poetry/pull/9335">#9335</a>).</li> </ul> <h3 id="docs-9">Docs</h3> <ul> <li>Fix incorrect information about <code>poetry shell</code> (<a href="https://github.com/python-poetry/poetry/pull/9060">#9060</a>).</li> <li>Add a git subdirectory example to <code>poetry add</code> (<a href="https://github.com/python-poetry/poetry/pull/9080">#9080</a>).</li> <li>Mention interactive credential configuration (<a href="https://github.com/python-poetry/poetry/pull/9074">#9074</a>).</li> <li>Add notes for optional advanced installation steps (<a href="https://github.com/python-poetry/poetry/pull/9098">#9098</a>).</li> <li>Add reference to configuration credentials in documentation of poetry <code>publish</code> (<a href="https://github.com/python-poetry/poetry/pull/9110">#9110</a>).</li> <li>Improve documentation for configuring credentials via environment variables (<a href="https://github.com/python-poetry/poetry/pull/9121">#9121</a>).</li> <li>Remove misleading wording around virtual environments (<a href="https://github.com/python-poetry/poetry/pull/9213">#9213</a>).</li> <li>Remove outdated advice regarding seeding keyring backends (<a href="https://github.com/python-poetry/poetry/pull/9164">#9164</a>).</li> <li>Add a <code>pyproject.toml</code> example for a dependency with multiple extras (<a href="https://github.com/python-poetry/poetry/pull/9138">#9138</a>).</li> <li>Clarify help of <code>poetry add</code> (<a href="https://github.com/python-poetry/poetry/pull/9230">#9230</a>).</li> <li>Add a note how to configure credentials for TestPyPI for <code>poetry publish</code> (<a href="https://github.com/python-poetry/poetry/pull/9255">#9255</a>).</li> <li>Fix information about the <code>--readme</code> option in <code>poetry new</code> (<a href="https://github.com/python-poetry/poetry/pull/9260">#9260</a>).</li> <li>Clarify what is special about the Python constraint in <code>dependencies</code> (<a href="https://github.com/python-poetry/poetry/pull/9256">#9256</a>).</li> <li>Update how to uninstall plugins via <code>pipx</code> (<a href="https://github.com/python-poetry/poetry/pull/9320">#9320</a>).</li> </ul> <h2 id="182---2024-03-02"><a href="https://github.com/python-poetry/poetry/releases/tag/1.8.2">1.8.2</a> - 2024-03-02</h2> <h3 id="fixed-14">Fixed</h3> <ul> <li>Harden <code>lazy-wheel</code> error handling if the index server is behaving badly in an unexpected way (<a href="https://github.com/python-poetry/poetry/pull/9051">#9051</a>).</li> <li>Improve <code>lazy-wheel</code> error handling if the index server does not handle HTTP range requests correctly (<a href="https://github.com/python-poetry/poetry/pull/9082">#9082</a>).</li> <li>Improve <code>lazy-wheel</code> error handling if the index server pretends to support HTTP range requests but does not respect them (<a href="https://github.com/python-poetry/poetry/pull/9084">#9084</a>).</li> <li>Improve <code>lazy-wheel</code> to allow redirects for HEAD requests (<a href="https://github.com/python-poetry/poetry/pull/9087">#9087</a>).</li> <li>Improve debug logging for <code>lazy-wheel</code> errors (<a href="https://github.com/python-poetry/poetry/pull/9059">#9059</a>).</li> <li>Fix an issue where the hash of a metadata file could not be calculated correctly due to an encoding issue (<a href="https://github.com/python-poetry/poetry/pull/9049">#9049</a>).</li> <li>Fix an issue where <code>poetry add</code> failed in non-package mode if no project name was set (<a href="https://github.com/python-poetry/poetry/pull/9046">#9046</a>).</li> <li>Fix an issue where a hint to non-package mode was not compliant with the final name of the setting (<a href="https://github.com/python-poetry/poetry/pull/9073">#9073</a>).</li> </ul> <h2 id="181---2024-02-26"><a href="https://github.com/python-poetry/poetry/releases/tag/1.8.1">1.8.1</a> - 2024-02-26</h2> <h3 id="fixed-15">Fixed</h3> <ul> <li>Update the minimum required version of <code>packaging</code> (<a href="https://github.com/python-poetry/poetry/pull/9031">#9031</a>).</li> <li>Handle unexpected responses from servers that do not support HTTP range requests with negative offsets more robust (<a href="https://github.com/python-poetry/poetry/pull/9030">#9030</a>).</li> </ul> <h3 id="docs-10">Docs</h3> <ul> <li>Rename <code>master</code> branch to <code>main</code> (<a href="https://github.com/python-poetry/poetry/pull/9022">#9022</a>).</li> </ul> <h2 id="180---2024-02-25"><a href="https://github.com/python-poetry/poetry/releases/tag/1.8.0">1.8.0</a> - 2024-02-25</h2> <h3 id="added-7">Added</h3> <ul> <li><strong>Add a <code>non-package</code> mode for use cases where Poetry is only used for dependency management</strong> (<a href="https://github.com/python-poetry/poetry/pull/8650">#8650</a>).</li> <li><strong>Add support for PEP 658 to fetch metadata without having to download wheels</strong> (<a href="https://github.com/python-poetry/poetry/pull/5509">#5509</a>).</li> <li><strong>Add a <code>lazy-wheel</code> config option (default: <code>true</code>) to reduce wheel downloads during dependency resolution</strong> (<a href="https://github.com/python-poetry/poetry/pull/8815">#8815</a>, <a href="https://github.com/python-poetry/poetry/pull/8941">#8941</a>).</li> <li>Improve performance of dependency resolution by using shallow copies instead of deep copies (<a href="https://github.com/python-poetry/poetry/pull/8671">#8671</a>).</li> <li><code>poetry check</code> validates that no unknown sources are referenced in dependencies (<a href="https://github.com/python-poetry/poetry/pull/8709">#8709</a>).</li> <li>Add archive validation during installation for further hash algorithms (<a href="https://github.com/python-poetry/poetry/pull/8851">#8851</a>).</li> <li>Add a <code>to</code> key in <code>tool.poetry.packages</code> to allow custom subpackage names (<a href="https://github.com/python-poetry/poetry/pull/8791">#8791</a>).</li> <li>Add a config option to disable <code>keyring</code> (<a href="https://github.com/python-poetry/poetry/pull/8910">#8910</a>).</li> <li>Add a <code>--sync</code> option to <code>poetry update</code> (<a href="https://github.com/python-poetry/poetry/pull/8931">#8931</a>).</li> <li>Add an <code>--output</code> option to <code>poetry build</code> (<a href="https://github.com/python-poetry/poetry/pull/8828">#8828</a>).</li> <li>Add a <code>--dist-dir</code> option to <code>poetry publish</code> (<a href="https://github.com/python-poetry/poetry/pull/8828">#8828</a>).</li> </ul> <h3 id="changed-12">Changed</h3> <ul> <li><strong>The implicit PyPI source is disabled if at least one primary source is configured</strong> (<a href="https://github.com/python-poetry/poetry/pull/8771">#8771</a>).</li> <li><strong>Deprecate source priority <code>default</code></strong> (<a href="https://github.com/python-poetry/poetry/pull/8771">#8771</a>).</li> <li><strong>Upgrade the warning about an inconsistent lockfile to an error</strong> (<a href="https://github.com/python-poetry/poetry/pull/8737">#8737</a>).</li> <li>Deprecate setting <code>installer.modern-installation</code> to <code>false</code> (<a href="https://github.com/python-poetry/poetry/pull/8988">#8988</a>).</li> <li>Drop support for <code>pip&lt;19</code> (<a href="https://github.com/python-poetry/poetry/pull/8894">#8894</a>).</li> <li>Require <code>requests-toolbelt&gt;=1</code> (<a href="https://github.com/python-poetry/poetry/pull/8680">#8680</a>).</li> <li>Allow <code>platformdirs</code> 4.x (<a href="https://github.com/python-poetry/poetry/pull/8668">#8668</a>).</li> <li>Allow and require <code>xattr</code> 1.x on macOS (<a href="https://github.com/python-poetry/poetry/pull/8801">#8801</a>).</li> <li>Improve venv shell activation in <code>fish</code> (<a href="https://github.com/python-poetry/poetry/pull/8804">#8804</a>).</li> <li>Rename <code>system</code> to <code>base</code> in output of <code>poetry env info</code> (<a href="https://github.com/python-poetry/poetry/pull/8832">#8832</a>).</li> <li>Use pretty name in output of <code>poetry version</code> (<a href="https://github.com/python-poetry/poetry/pull/8849">#8849</a>).</li> <li>Improve error handling for invalid entries in <code>tool.poetry.scripts</code> (<a href="https://github.com/python-poetry/poetry/pull/8898">#8898</a>).</li> <li>Improve verbose output for dependencies with extras during dependency resolution (<a href="https://github.com/python-poetry/poetry/pull/8834">#8834</a>).</li> <li>Improve message about an outdated lockfile (<a href="https://github.com/python-poetry/poetry/pull/8962">#8962</a>).</li> </ul> <h3 id="fixed-16">Fixed</h3> <ul> <li>Fix an issue where <code>poetry shell</code> failed when Python has been installed with MSYS2 (<a href="https://github.com/python-poetry/poetry/pull/8644">#8644</a>).</li> <li>Fix an issue where Poetry commands failed in a terminal with a non-UTF-8 encoding (<a href="https://github.com/python-poetry/poetry/pull/8608">#8608</a>).</li> <li>Fix an issue where a missing project name caused an incomprehensible error message (<a href="https://github.com/python-poetry/poetry/pull/8691">#8691</a>).</li> <li>Fix an issue where Poetry failed to install an <code>sdist</code> path dependency (<a href="https://github.com/python-poetry/poetry/pull/8682">#8682</a>).</li> <li>Fix an issue where <code>poetry install</code> failed because an unused extra was not available (<a href="https://github.com/python-poetry/poetry/pull/8548">#8548</a>).</li> <li>Fix an issue where <code>poetry install --sync</code> did not remove an unrequested extra (<a href="https://github.com/python-poetry/poetry/pull/8621">#8621</a>).</li> <li>Fix an issue where <code>poetry init</code> did not allow specific characters in the author field (<a href="https://github.com/python-poetry/poetry/pull/8779">#8779</a>).</li> <li>Fix an issue where Poetry could not download <code>sdists</code> from misconfigured servers (<a href="https://github.com/python-poetry/poetry/pull/8701">#8701</a>).</li> <li>Fix an issue where metadata of sdists that call CLI tools of their build requirements could not be determined (<a href="https://github.com/python-poetry/poetry/pull/8827">#8827</a>).</li> <li>Fix an issue where Poetry failed to use the currently activated environment (<a href="https://github.com/python-poetry/poetry/pull/8831">#8831</a>).</li> <li>Fix an issue where <code>poetry shell</code> failed in <code>zsh</code> if a space was in the venv path (<a href="https://github.com/python-poetry/poetry/pull/7245">#7245</a>).</li> <li>Fix an issue where scripts with extras could not be installed (<a href="https://github.com/python-poetry/poetry/pull/8900">#8900</a>).</li> <li>Fix an issue where explicit sources where not propagated correctly (<a href="https://github.com/python-poetry/poetry/pull/8835">#8835</a>).</li> <li>Fix an issue where debug prints where swallowed when using a build script (<a href="https://github.com/python-poetry/poetry/pull/8760">#8760</a>).</li> <li>Fix an issue where explicit sources of locked dependencies where not propagated correctly (<a href="https://github.com/python-poetry/poetry/pull/8948">#8948</a>).</li> <li>Fix an issue where Poetry&rsquo;s own environment was falsely identified as system environment (<a href="https://github.com/python-poetry/poetry/pull/8970">#8970</a>).</li> <li>Fix an issue where dependencies from a <code>setup.py</code> were ignored silently (<a href="https://github.com/python-poetry/poetry/pull/9000">#9000</a>).</li> <li>Fix an issue where environment variables for <code>virtualenv.options</code> were ignored (<a href="https://github.com/python-poetry/poetry/pull/9015">#9015</a>).</li> <li>Fix an issue where <code>virtualenvs.options.no-pip</code> and <code>virtualenvs.options.no-setuptools</code> were not normalized (<a href="https://github.com/python-poetry/poetry/pull/9015">#9015</a>).</li> </ul> <h3 id="docs-11">Docs</h3> <ul> <li>Replace deprecated <code>--no-dev</code> with <code>--without dev</code> in the FAQ (<a href="https://github.com/python-poetry/poetry/pull/8659">#8659</a>).</li> <li>Recommend <code>poetry-check</code> instead of the deprecated <code>poetry-lock</code> pre-commit hook (<a href="https://github.com/python-poetry/poetry/pull/8675">#8675</a>).</li> <li>Clarify the names of the environment variables to provide credentials for repositories (<a href="https://github.com/python-poetry/poetry/pull/8782">#8782</a>).</li> <li>Add note how to install several version of Poetry in parallel (<a href="https://github.com/python-poetry/poetry/pull/8814">#8814</a>).</li> <li>Improve description of <code>poetry show --why</code> (<a href="https://github.com/python-poetry/poetry/pull/8817">#8817</a>).</li> <li>Improve documentation of <code>poetry update</code> (<a href="https://github.com/python-poetry/poetry/pull/8706">#8706</a>).</li> <li>Add a warning about passing variables that may start with a hyphen via command line (<a href="https://github.com/python-poetry/poetry/pull/8850">#8850</a>).</li> <li>Mention that the virtual environment in which Poetry itself is installed should not be activated (<a href="https://github.com/python-poetry/poetry/pull/8833">#8833</a>).</li> <li>Add note about <code>poetry run</code> and externally managed environments (<a href="https://github.com/python-poetry/poetry/pull/8748">#8748</a>).</li> <li>Update FAQ entry about <code>tox</code> for <code>tox</code> 4.x (<a href="https://github.com/python-poetry/poetry/pull/8658">#8658</a>).</li> <li>Fix documentation for default <code>format</code> option for <code>include</code> and <code>exclude</code> value (<a href="https://github.com/python-poetry/poetry/pull/8852">#8852</a>).</li> <li>Add note about <code>tox</code> and configured credentials (<a href="https://github.com/python-poetry/poetry/pull/8888">#8888</a>).</li> <li>Add note and link how to install <code>pipx</code> (<a href="https://github.com/python-poetry/poetry/pull/8878">#8878</a>).</li> <li>Fix examples for <code>poetry add</code> with git dependencies over ssh (<a href="https://github.com/python-poetry/poetry/pull/8911">#8911</a>).</li> <li>Remove reference to deprecated scripts extras feature (<a href="https://github.com/python-poetry/poetry/pull/8903">#8903</a>).</li> <li>Change examples to prefer <code>--only main</code> instead of <code>--without dev</code> (<a href="https://github.com/python-poetry/poetry/pull/8921">#8921</a>).</li> <li>Mention that the <code>develop</code> attribute is a Poetry-specific feature and not propagated to other tools (<a href="https://github.com/python-poetry/poetry/pull/8971">#8971</a>).</li> <li>Fix examples for adding supplemental and secondary sources (<a href="https://github.com/python-poetry/poetry/pull/8953">#8953</a>).</li> <li>Add PyTorch example for explicit sources (<a href="https://github.com/python-poetry/poetry/pull/9006">#9006</a>).</li> </ul> <h3 id="poetry-core-190httpsgithubcompython-poetrypoetry-corereleasestag190">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/1.9.0"><code>1.9.0</code></a>)</h3> <ul> <li><strong>Deprecate scripts that depend on extras</strong> (<a href="https://github.com/python-poetry/poetry-core/pull/690">#690</a>).</li> <li>Add support for path dependencies that do not define a build system (<a href="https://github.com/python-poetry/poetry-core/pull/675">#675</a>).</li> <li>Update list of supported licenses (<a href="https://github.com/python-poetry/poetry-core/pull/659">#659</a>, <a href="https://github.com/python-poetry/poetry-core/pull/669">#669</a>, <a href="https://github.com/python-poetry/poetry-core/pull/678">#678</a>, <a href="https://github.com/python-poetry/poetry-core/pull/694">#694</a>).</li> <li>Rework list of files included in build artifacts (<a href="https://github.com/python-poetry/poetry-core/pull/666">#666</a>).</li> <li>Fix an issue where insignificant errors were printed if the working directory is not inside a git repository (<a href="https://github.com/python-poetry/poetry-core/pull/684">#684</a>).</li> <li>Fix an issue where the project&rsquo;s directory was not recognized as git repository on Windows due to an encoding issue (<a href="https://github.com/python-poetry/poetry-core/pull/685">#685</a>).</li> </ul> <h2 id="171---2023-11-16"><a href="https://github.com/python-poetry/poetry/releases/tag/1.7.1">1.7.1</a> - 2023-11-16</h2> <h3 id="fixed-17">Fixed</h3> <ul> <li>Fix an issue where sdists that call CLI tools of their build requirements could not be installed (<a href="https://github.com/python-poetry/poetry/pull/8630">#8630</a>).</li> <li>Fix an issue where sdists with symlinks could not be installed due to a broken tarfile datafilter (<a href="https://github.com/python-poetry/poetry/pull/8649">#8649</a>).</li> <li>Fix an issue where <code>poetry init</code> failed when trying to add dependencies (<a href="https://github.com/python-poetry/poetry/pull/8655">#8655</a>).</li> <li>Fix an issue where <code>poetry install</code> failed if <code>virtualenvs.create</code> was set to <code>false</code> (<a href="https://github.com/python-poetry/poetry/pull/8672">#8672</a>).</li> </ul> <h2 id="170---2023-11-03"><a href="https://github.com/python-poetry/poetry/releases/tag/1.7.0">1.7.0</a> - 2023-11-03</h2> <h3 id="added-8">Added</h3> <ul> <li><strong>Add official support for Python 3.12</strong> (<a href="https://github.com/python-poetry/poetry/pull/7803">#7803</a>, <a href="https://github.com/python-poetry/poetry/pull/8544">#8544</a>).</li> <li><strong>Print a future warning that <code>poetry-plugin-export</code> will not be installed by default anymore</strong> (<a href="https://github.com/python-poetry/poetry/pull/8562">#8562</a>).</li> <li>Add <code>poetry-install</code> pre-commit hook (<a href="https://github.com/python-poetry/poetry/pull/8327">#8327</a>).</li> <li>Add <code>--next-phase</code> option to <code>poetry version</code> (<a href="https://github.com/python-poetry/poetry/pull/8089">#8089</a>).</li> <li>Print a warning when overwriting files from another package at installation (<a href="https://github.com/python-poetry/poetry/pull/8386">#8386</a>).</li> <li>Print a warning if the current project cannot be installed (<a href="https://github.com/python-poetry/poetry/pull/8369">#8369</a>).</li> <li>Report more details on build backend exceptions (<a href="https://github.com/python-poetry/poetry/pull/8464">#8464</a>).</li> </ul> <h3 id="changed-13">Changed</h3> <ul> <li>Set Poetry as <code>user-agent</code> for all HTTP requests (<a href="https://github.com/python-poetry/poetry/pull/8394">#8394</a>).</li> <li>Do not install <code>setuptools</code> per default in Python 3.12 (<a href="https://github.com/python-poetry/poetry/pull/7803">#7803</a>).</li> <li>Do not install <code>wheel</code> per default (<a href="https://github.com/python-poetry/poetry/pull/7803">#7803</a>).</li> <li>Remove <code>setuptools</code> and <code>wheel</code> when running <code>poetry install --sync</code> if they are not required by the project (<a href="https://github.com/python-poetry/poetry/pull/8600">#8600</a>).</li> <li>Improve error message about PEP-517 support (<a href="https://github.com/python-poetry/poetry/pull/8463">#8463</a>).</li> <li>Improve <code>keyring</code> handling (<a href="https://github.com/python-poetry/poetry/pull/8227">#8227</a>).</li> <li>Read the <code>description</code> field when extracting metadata from <code>setup.py</code> files (<a href="https://github.com/python-poetry/poetry/pull/8545">#8545</a>).</li> </ul> <h3 id="fixed-18">Fixed</h3> <ul> <li><strong>Fix an issue where dependencies of inactive extras were locked and installed</strong> (<a href="https://github.com/python-poetry/poetry/pull/8399">#8399</a>).</li> <li><strong>Fix an issue where build requirements were not installed due to a race condition in the artifact cache</strong> (<a href="https://github.com/python-poetry/poetry/pull/8517">#8517</a>).</li> <li>Fix an issue where packages included in the system site packages were installed even though <code>virtualenvs.options.system-site-packages</code> was set (<a href="https://github.com/python-poetry/poetry/pull/8359">#8359</a>).</li> <li>Fix an issue where git dependencies&rsquo; submodules with relative URLs were handled incorrectly (<a href="https://github.com/python-poetry/poetry/pull/8020">#8020</a>).</li> <li>Fix an issue where a failed installation of build dependencies was not noticed directly (<a href="https://github.com/python-poetry/poetry/pull/8479">#8479</a>).</li> <li>Fix an issue where <code>poetry shell</code> did not work completely with <code>nushell</code> (<a href="https://github.com/python-poetry/poetry/pull/8478">#8478</a>).</li> <li>Fix an issue where a confusing error messages was displayed when running <code>poetry config pypi-token.pypi</code> without a value (<a href="https://github.com/python-poetry/poetry/pull/8502">#8502</a>).</li> <li>Fix an issue where a cryptic error message is printed if there is no metadata entry in the lockfile (<a href="https://github.com/python-poetry/poetry/pull/8523">#8523</a>).</li> <li>Fix an issue with the encoding with special characters in the virtualenv&rsquo;s path (<a href="https://github.com/python-poetry/poetry/pull/8565">#8565</a>).</li> <li>Fix an issue where the connection pool size was not adjusted to the number of workers (<a href="https://github.com/python-poetry/poetry/pull/8559">#8559</a>).</li> </ul> <h3 id="docs-12">Docs</h3> <ul> <li>Improve the wording regarding a project&rsquo;s supported Python range (<a href="https://github.com/python-poetry/poetry/pull/8423">#8423</a>).</li> <li>Make <code>pipx</code> the preferred (first mentioned) installation method (<a href="https://github.com/python-poetry/poetry/pull/8090">#8090</a>).</li> <li>Add a warning about <code>poetry self</code> on Windows (<a href="https://github.com/python-poetry/poetry/pull/8090">#8090</a>).</li> <li>Fix example for <code>poetry add</code> with a git dependency (<a href="https://github.com/python-poetry/poetry/pull/8438">#8438</a>).</li> <li>Add information about auto-included files in wheels and sdist (<a href="https://github.com/python-poetry/poetry/pull/8555">#8555</a>).</li> <li>Fix documentation of the <code>POETRY_REPOSITORIES_</code> variables docs (<a href="https://github.com/python-poetry/poetry/pull/8492">#8492</a>).</li> <li>Add <code>CITATION.cff</code> file (<a href="https://github.com/python-poetry/poetry/pull/8510">#8510</a>).</li> </ul> <h3 id="poetry-core-181httpsgithubcompython-poetrypoetry-corereleasestag181">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/1.8.1"><code>1.8.1</code></a>)</h3> <ul> <li>Add support for creating packages dynamically in the build script (<a href="https://github.com/python-poetry/poetry-core/pull/629">#629</a>).</li> <li>Improve marker logic for <code>extra</code> markers (<a href="https://github.com/python-poetry/poetry-core/pull/636">#636</a>).</li> <li>Update list of supported licenses (<a href="https://github.com/python-poetry/poetry-core/pull/635">#635</a>, <a href="https://github.com/python-poetry/poetry-core/pull/646">#646</a>).</li> <li>Fix an issue where projects with extension modules were not installed in editable mode (<a href="https://github.com/python-poetry/poetry-core/pull/633">#633</a>).</li> <li>Fix an issue where the wrong or no <code>lib</code> folder was added to the wheel (<a href="https://github.com/python-poetry/poetry-core/pull/634">#634</a>).</li> </ul> <h3 id="poetry-plugin-export-160httpsgithubcompython-poetrypoetry-plugin-exportreleasestag160">poetry-plugin-export (<a href="https://github.com/python-poetry/poetry-plugin-export/releases/tag/1.6.0"><code>^1.6.0</code></a>)</h3> <ul> <li>Add an <code>--all-extras</code> option (<a href="https://github.com/python-poetry/poetry-plugin-export/pull/241">#241</a>).</li> <li>Fix an issue where git dependencies are exported with the branch name instead of the resolved commit hash (<a href="https://github.com/python-poetry/poetry-plugin-export/pull/213">#213</a>).</li> </ul> <h2 id="161---2023-08-21"><a href="https://github.com/python-poetry/poetry/releases/tag/1.6.1">1.6.1</a> - 2023-08-21</h2> <h3 id="fixed-19">Fixed</h3> <ul> <li>Update the minimum required version of <code>requests</code> (<a href="https://github.com/python-poetry/poetry/pull/8336">#8336</a>).</li> </ul> <h2 id="160---2023-08-20"><a href="https://github.com/python-poetry/poetry/releases/tag/1.6.0">1.6.0</a> - 2023-08-20</h2> <h3 id="added-9">Added</h3> <ul> <li><strong>Add support for repositories that do not provide a supported hash algorithm</strong> (<a href="https://github.com/python-poetry/poetry/pull/8118">#8118</a>).</li> <li><strong>Add full support for duplicate dependencies with overlapping markers</strong> (<a href="https://github.com/python-poetry/poetry/pull/7257">#7257</a>).</li> <li><strong>Improve performance of <code>poetry lock</code> for certain edge cases</strong> (<a href="https://github.com/python-poetry/poetry/pull/8256">#8256</a>).</li> <li>Improve performance of <code>poetry install</code> (<a href="https://github.com/python-poetry/poetry/pull/8031">#8031</a>).</li> <li><code>poetry check</code> validates that specified <code>readme</code> files do exist (<a href="https://github.com/python-poetry/poetry/pull/7444">#7444</a>).</li> <li>Add a downgrading note when updating to an older version (<a href="https://github.com/python-poetry/poetry/pull/8176">#8176</a>).</li> <li>Add support for <code>vox</code> in the <code>xonsh</code> shell (<a href="https://github.com/python-poetry/poetry/pull/8203">#8203</a>).</li> <li>Add support for <code>pre-commit</code> hooks for projects where the pyproject.toml file is located in a subfolder (<a href="https://github.com/python-poetry/poetry/pull/8204">#8204</a>).</li> <li>Add support for the <code>git+http://</code> scheme (<a href="https://github.com/python-poetry/poetry/pull/6619">#6619</a>).</li> </ul> <h3 id="changed-14">Changed</h3> <ul> <li><strong>Drop support for Python 3.7</strong> (<a href="https://github.com/python-poetry/poetry/pull/7674">#7674</a>).</li> <li>Move <code>poetry lock --check</code> to <code>poetry check --lock</code> and deprecate the former (<a href="https://github.com/python-poetry/poetry/pull/8015">#8015</a>).</li> <li>Change future warning that PyPI will only be disabled automatically if there are no primary sources (<a href="https://github.com/python-poetry/poetry/pull/8151">#8151</a>).</li> </ul> <h3 id="fixed-20">Fixed</h3> <ul> <li>Fix an issue where <code>build-system.requires</code> were not respected for projects with build scripts (<a href="https://github.com/python-poetry/poetry/pull/7975">#7975</a>).</li> <li>Fix an issue where the encoding was not handled correctly when calling a subprocess (<a href="https://github.com/python-poetry/poetry/pull/8060">#8060</a>).</li> <li>Fix an issue where <code>poetry show --top-level</code> did not show top level dependencies with extras (<a href="https://github.com/python-poetry/poetry/pull/8076">#8076</a>).</li> <li>Fix an issue where <code>poetry init</code> handled projects with <code>src</code> layout incorrectly (<a href="https://github.com/python-poetry/poetry/pull/8218">#8218</a>).</li> <li>Fix an issue where Poetry wrote <code>.pth</code> files with the wrong encoding (<a href="https://github.com/python-poetry/poetry/pull/8041">#8041</a>).</li> <li>Fix an issue where <code>poetry install</code> did not respect the source if the same version of a package has been locked from different sources (<a href="https://github.com/python-poetry/poetry/pull/8304">#8304</a>).</li> </ul> <h3 id="docs-13">Docs</h3> <ul> <li>Document <strong>official Poetry badge</strong> (<a href="https://github.com/python-poetry/poetry/pull/8066">#8066</a>).</li> <li>Update configuration folder path for macOS (<a href="https://github.com/python-poetry/poetry/pull/8062">#8062</a>).</li> <li>Add a warning about pip ignoring lock files (<a href="https://github.com/python-poetry/poetry/pull/8117">#8117</a>).</li> <li>Clarify the use of the <code>virtualenvs.in-project</code> setting. (<a href="https://github.com/python-poetry/poetry/pull/8126">#8126</a>).</li> <li>Change <code>pre-commit</code> YAML style to be consistent with pre-commit&rsquo;s own examples (<a href="https://github.com/python-poetry/poetry/pull/8146">#8146</a>).</li> <li>Fix command for listing installed plugins (<a href="https://github.com/python-poetry/poetry/pull/8200">#8200</a>).</li> <li>Mention the <code>nox-poetry</code> package (<a href="https://github.com/python-poetry/poetry/pull/8173">#8173</a>).</li> <li>Add an example with a PyPI source in the pyproject.toml file (<a href="https://github.com/python-poetry/poetry/pull/8171">#8171</a>).</li> <li>Use <code>reference</code> instead of deprecated <code>callable</code> in the scripts example (<a href="https://github.com/python-poetry/poetry/pull/8211">#8211</a>).</li> </ul> <h3 id="poetry-core-170httpsgithubcompython-poetrypoetry-corereleasestag170">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/1.7.0"><code>1.7.0</code></a>)</h3> <ul> <li>Improve performance of marker handling (<a href="https://github.com/python-poetry/poetry-core/pull/609">#609</a>).</li> <li>Allow <code>|</code> as a value separator in markers with the operators <code>in</code> and <code>not in</code> (<a href="https://github.com/python-poetry/poetry-core/pull/608">#608</a>).</li> <li>Put pretty name (instead of normalized name) in metadata (<a href="https://github.com/python-poetry/poetry-core/pull/620">#620</a>).</li> <li>Update list of supported licenses (<a href="https://github.com/python-poetry/poetry-core/pull/623">#623</a>).</li> <li>Fix an issue where PEP 508 dependency specifications with names starting with a digit could not be parsed (<a href="https://github.com/python-poetry/poetry-core/pull/607">#607</a>).</li> <li>Fix an issue where Poetry considered an unrelated <code>.gitignore</code> file resulting in an empty wheel (<a href="https://github.com/python-poetry/poetry-core/pull/611">#611</a>).</li> </ul> <h3 id="poetry-plugin-export-150httpsgithubcompython-poetrypoetry-plugin-exportreleasestag150">poetry-plugin-export (<a href="https://github.com/python-poetry/poetry-plugin-export/releases/tag/1.5.0"><code>^1.5.0</code></a>)</h3> <ul> <li>Fix an issue where markers for dependencies required by an extra were not generated correctly (<a href="https://github.com/python-poetry/poetry-plugin-export/pull/209">#209</a>).</li> </ul> <h2 id="151---2023-05-29"><a href="https://github.com/python-poetry/poetry/releases/tag/1.5.1">1.5.1</a> - 2023-05-29</h2> <h3 id="added-10">Added</h3> <ul> <li>Improve dependency resolution performance in cases with a lot of backtracking (<a href="https://github.com/python-poetry/poetry/pull/7950">#7950</a>).</li> </ul> <h3 id="changed-15">Changed</h3> <ul> <li>Disable wheel content validation during installation (<a href="https://github.com/python-poetry/poetry/pull/7987">#7987</a>).</li> </ul> <h3 id="fixed-21">Fixed</h3> <ul> <li>Fix an issue where partially downloaded wheels were cached (<a href="https://github.com/python-poetry/poetry/pull/7968">#7968</a>).</li> <li>Fix an issue where <code>poetry run</code> did no longer execute relative-path scripts (<a href="https://github.com/python-poetry/poetry/pull/7963">#7963</a>).</li> <li>Fix an issue where dependencies were not installed in <code>in-project</code> environments (<a href="https://github.com/python-poetry/poetry/pull/7977">#7977</a>).</li> <li>Fix an issue where no solution was found for a transitive dependency on a pre-release of a package (<a href="https://github.com/python-poetry/poetry/pull/7978">#7978</a>).</li> <li>Fix an issue where cached repository packages were incorrectly parsed, leading to its dependencies being ignored (<a href="https://github.com/python-poetry/poetry/pull/7995">#7995</a>).</li> <li>Fix an issue where an explicit source was ignored so that a direct origin dependency was used instead (<a href="https://github.com/python-poetry/poetry/pull/7973">#7973</a>).</li> <li>Fix an issue where the installation of big wheels consumed a lot of memory (<a href="https://github.com/python-poetry/poetry/pull/7987">#7987</a>).</li> </ul> <h3 id="docs-14">Docs</h3> <ul> <li>Add information about multiple constraints dependencies with direct origin and version dependencies (<a href="https://github.com/python-poetry/poetry/pull/7973">#7973</a>).</li> </ul> <h3 id="poetry-core-161httpsgithubcompython-poetrypoetry-corereleasestag161">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/1.6.1"><code>1.6.1</code></a>)</h3> <ul> <li>Fix an endless recursion in marker handling (<a href="https://github.com/python-poetry/poetry-core/pull/593">#593</a>).</li> <li>Fix an issue where the wheel tag was not built correctly under certain circumstances (<a href="https://github.com/python-poetry/poetry-core/pull/591">#591</a>).</li> </ul> <h3 id="poetry-plugin-export-140httpsgithubcompython-poetrypoetry-plugin-exportreleasestag140">poetry-plugin-export (<a href="https://github.com/python-poetry/poetry-plugin-export/releases/tag/1.4.0"><code>^1.4.0</code></a>)</h3> <ul> <li>Fix an issue where <code>--extra-index-url</code> and <code>--trusted-host</code> was not generated for sources with priority <code>explicit</code> (<a href="https://github.com/python-poetry/poetry-plugin-export/pull/205">#205</a>).</li> </ul> <h2 id="150---2023-05-19"><a href="https://github.com/python-poetry/poetry/releases/tag/1.5.0">1.5.0</a> - 2023-05-19</h2> <h3 id="added-11">Added</h3> <ul> <li><strong>Introduce the new source priorities <code>explicit</code> and <code>supplemental</code></strong> (<a href="https://github.com/python-poetry/poetry/pull/7658">#7658</a>, <a href="https://github.com/python-poetry/poetry/pull/6879">#6879</a>).</li> <li><strong>Introduce the option to configure the priority of the implicit PyPI source</strong> (<a href="https://github.com/python-poetry/poetry/pull/7801">#7801</a>).</li> <li>Add handling for corrupt cache files (<a href="https://github.com/python-poetry/poetry/pull/7453">#7453</a>).</li> <li>Improve caching of URL and git dependencies (<a href="https://github.com/python-poetry/poetry/pull/7693">#7693</a>, <a href="https://github.com/python-poetry/poetry/pull/7473">#7473</a>).</li> <li>Add option to skip installing directory dependencies (<a href="https://github.com/python-poetry/poetry/pull/6845">#6845</a>, <a href="https://github.com/python-poetry/poetry/pull/7923">#7923</a>).</li> <li>Add <code>--executable</code> option to <code>poetry env info</code> (<a href="https://github.com/python-poetry/poetry/pull/7547">#7547</a>).</li> <li>Add <code>--top-level</code> option to <code>poetry show</code> (<a href="https://github.com/python-poetry/poetry/pull/7415">#7415</a>).</li> <li>Add <code>--lock</code> option to <code>poetry remove</code> (<a href="https://github.com/python-poetry/poetry/pull/7917">#7917</a>).</li> <li>Add experimental <code>POETRY_REQUESTS_TIMEOUT</code> option (<a href="https://github.com/python-poetry/poetry/pull/7081">#7081</a>).</li> <li>Improve performance of wheel inspection by avoiding unnecessary file copy operations (<a href="https://github.com/python-poetry/poetry/pull/7916">#7916</a>).</li> </ul> <h3 id="changed-16">Changed</h3> <ul> <li><strong>Remove the old deprecated installer and the corresponding setting <code>experimental.new-installer</code></strong> (<a href="https://github.com/python-poetry/poetry/pull/7356">#7356</a>).</li> <li><strong>Introduce <code>priority</code> key for sources and deprecate flags <code>default</code> and <code>secondary</code></strong> (<a href="https://github.com/python-poetry/poetry/pull/7658">#7658</a>).</li> <li>Deprecate <code>poetry run &lt;entry point&gt;</code> if the entry point was not previously installed via <code>poetry install</code> (<a href="https://github.com/python-poetry/poetry/pull/7606">#7606</a>).</li> <li>Only write the lock file if the installation succeeds (<a href="https://github.com/python-poetry/poetry/pull/7498">#7498</a>).</li> <li>Do not write the unused package category into the lock file (<a href="https://github.com/python-poetry/poetry/pull/7637">#7637</a>).</li> </ul> <h3 id="fixed-22">Fixed</h3> <ul> <li>Fix an issue where Poetry&rsquo;s internal pyproject.toml continually grows larger with empty lines (<a href="https://github.com/python-poetry/poetry/pull/7705">#7705</a>).</li> <li>Fix an issue where Poetry crashes due to corrupt cache files (<a href="https://github.com/python-poetry/poetry/pull/7453">#7453</a>).</li> <li>Fix an issue where the <code>Retry-After</code> in HTTP responses was not respected and retries were handled inconsistently (<a href="https://github.com/python-poetry/poetry/pull/7072">#7072</a>).</li> <li>Fix an issue where Poetry silently ignored invalid groups (<a href="https://github.com/python-poetry/poetry/pull/7529">#7529</a>).</li> <li>Fix an issue where Poetry does not find a compatible Python version if not given explicitly (<a href="https://github.com/python-poetry/poetry/pull/7771">#7771</a>).</li> <li>Fix an issue where the <code>direct_url.json</code> of an editable install from a git dependency was invalid (<a href="https://github.com/python-poetry/poetry/pull/7473">#7473</a>).</li> <li>Fix an issue where error messages from build backends were not decoded correctly (<a href="https://github.com/python-poetry/poetry/pull/7781">#7781</a>).</li> <li>Fix an infinite loop when adding certain dependencies (<a href="https://github.com/python-poetry/poetry/pull/7405">#7405</a>).</li> <li>Fix an issue where pre-commit hooks skip pyproject.toml files in subdirectories (<a href="https://github.com/python-poetry/poetry/pull/7239">#7239</a>).</li> <li>Fix an issue where pre-commit hooks do not use the expected Python version (<a href="https://github.com/python-poetry/poetry/pull/6989">#6989</a>).</li> <li>Fix an issue where an unclear error message is printed if the project name is the same as one of its dependencies (<a href="https://github.com/python-poetry/poetry/pull/7757">#7757</a>).</li> <li>Fix an issue where <code>poetry install</code> returns a zero exit status even though the build script failed (<a href="https://github.com/python-poetry/poetry/pull/7812">#7812</a>).</li> <li>Fix an issue where an existing <code>.venv</code> was not used if <code>in-project</code> was not set (<a href="https://github.com/python-poetry/poetry/pull/7792">#7792</a>).</li> <li>Fix an issue where multiple extras passed to <code>poetry add</code> were not parsed correctly (<a href="https://github.com/python-poetry/poetry/pull/7836">#7836</a>).</li> <li>Fix an issue where <code>poetry shell</code> did not send a newline to <code>fish</code> (<a href="https://github.com/python-poetry/poetry/pull/7884">#7884</a>).</li> <li>Fix an issue where <code>poetry update --lock</code> printed operations that were not executed (<a href="https://github.com/python-poetry/poetry/pull/7915">#7915</a>).</li> <li>Fix an issue where <code>poetry add --lock</code> did perform a full update of all dependencies (<a href="https://github.com/python-poetry/poetry/pull/7920">#7920</a>).</li> <li>Fix an issue where <code>poetry shell</code> did not work with <code>nushell</code> (<a href="https://github.com/python-poetry/poetry/pull/7919">#7919</a>).</li> <li>Fix an issue where subprocess calls failed on Python 3.7 (<a href="https://github.com/python-poetry/poetry/pull/7932">#7932</a>).</li> <li>Fix an issue where keyring was called even though the password was stored in an environment variable (<a href="https://github.com/python-poetry/poetry/pull/7928">#7928</a>).</li> </ul> <h3 id="docs-15">Docs</h3> <ul> <li>Add information about what to use instead of <code>--dev</code> (<a href="https://github.com/python-poetry/poetry/pull/7647">#7647</a>).</li> <li>Promote semantic versioning less aggressively (<a href="https://github.com/python-poetry/poetry/pull/7517">#7517</a>).</li> <li>Explain Poetry&rsquo;s own versioning scheme in the FAQ (<a href="https://github.com/python-poetry/poetry/pull/7517">#7517</a>).</li> <li>Update documentation for configuration with environment variables (<a href="https://github.com/python-poetry/poetry/pull/6711">#6711</a>).</li> <li>Add details how to disable the virtualenv prompt (<a href="https://github.com/python-poetry/poetry/pull/7874">#7874</a>).</li> <li>Improve documentation on whether to commit <code>poetry.lock</code> (<a href="https://github.com/python-poetry/poetry/pull/7506">#7506</a>).</li> <li>Improve documentation of <code>virtualenv.create</code> (<a href="https://github.com/python-poetry/poetry/pull/7608">#7608</a>).</li> </ul> <h3 id="poetry-core-160httpsgithubcompython-poetrypoetry-corereleasestag160">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/1.6.0"><code>1.6.0</code></a>)</h3> <ul> <li>Improve error message for invalid markers (<a href="https://github.com/python-poetry/poetry-core/pull/569">#569</a>).</li> <li>Increase robustness when deleting temporary directories on Windows (<a href="https://github.com/python-poetry/poetry-core/pull/460">#460</a>).</li> <li>Replace <code>tomlkit</code> with <code>tomli</code>, which changes the interface of some <em>internal</em> classes (<a href="https://github.com/python-poetry/poetry-core/pull/483">#483</a>).</li> <li>Deprecate <code>Package.category</code> (<a href="https://github.com/python-poetry/poetry-core/pull/561">#561</a>).</li> <li>Fix a performance regression in marker handling (<a href="https://github.com/python-poetry/poetry-core/pull/568">#568</a>).</li> <li>Fix an issue where wildcard version constraints were not handled correctly (<a href="https://github.com/python-poetry/poetry-core/pull/402">#402</a>).</li> <li>Fix an issue where <code>poetry build</code> created duplicate Python classifiers if they were specified manually (<a href="https://github.com/python-poetry/poetry-core/pull/578">#578</a>).</li> <li>Fix an issue where local versions where not handled correctly (<a href="https://github.com/python-poetry/poetry-core/pull/579">#579</a>).</li> </ul> <h2 id="142---2023-04-02"><a href="https://github.com/python-poetry/poetry/releases/tag/1.4.2">1.4.2</a> - 2023-04-02</h2> <h3 id="changed-17">Changed</h3> <ul> <li>When trying to install wheels with invalid <code>RECORD</code> files, Poetry does not fail anymore but only prints a warning. This mitigates an unintended change introduced in Poetry 1.4.1 (<a href="https://github.com/python-poetry/poetry/pull/7694">#7694</a>).</li> </ul> <h3 id="fixed-23">Fixed</h3> <ul> <li>Fix an issue where relative git submodule urls were not parsed correctly (<a href="https://github.com/python-poetry/poetry/pull/7017">#7017</a>).</li> <li>Fix an issue where Poetry could freeze when building a project with a build script if it generated enough output to fill the OS pipe buffer (<a href="https://github.com/python-poetry/poetry/pull/7699">#7699</a>).</li> </ul> <h2 id="141---2023-03-19"><a href="https://github.com/python-poetry/poetry/releases/tag/1.4.1">1.4.1</a> - 2023-03-19</h2> <h3 id="fixed-24">Fixed</h3> <ul> <li>Fix an issue where <code>poetry install</code> did not respect the requirements for building editable dependencies (<a href="https://github.com/python-poetry/poetry/pull/7579">#7579</a>).</li> <li>Fix an issue where <code>poetry init</code> crashed due to bad input when adding packages interactively (<a href="https://github.com/python-poetry/poetry/pull/7569">#7569</a>).</li> <li>Fix an issue where <code>poetry install</code> ignored the <code>subdirectory</code> argument of git dependencies (<a href="https://github.com/python-poetry/poetry/pull/7580">#7580</a>).</li> <li>Fix an issue where installing packages with <code>no-binary</code> could result in a false hash mismatch (<a href="https://github.com/python-poetry/poetry/pull/7594">#7594</a>).</li> <li>Fix an issue where the hash of sdists was neither validated nor written to the <code>direct_url.json</code> during installation (<a href="https://github.com/python-poetry/poetry/pull/7594">#7594</a>).</li> <li>Fix an issue where <code>poetry install --sync</code> attempted to remove itself (<a href="https://github.com/python-poetry/poetry/pull/7626">#7626</a>).</li> <li>Fix an issue where wheels with non-normalized <code>dist-info</code> directory names could not be installed (<a href="https://github.com/python-poetry/poetry/pull/7671">#7671</a>).</li> <li>Fix an issue where <code>poetry install --compile</code> compiled with optimization level 1 (<a href="https://github.com/python-poetry/poetry/pull/7666">#7666</a>).</li> </ul> <h3 id="docs-16">Docs</h3> <ul> <li>Clarify the behavior of the <code>--extras</code> option (<a href="https://github.com/python-poetry/poetry/pull/7563">#7563</a>).</li> <li>Expand the FAQ on reasons for slow dependency resolution (<a href="https://github.com/python-poetry/poetry/pull/7620">#7620</a>).</li> </ul> <h3 id="poetry-core-152httpsgithubcompython-poetrypoetry-corereleasestag152">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/1.5.2"><code>1.5.2</code></a>)</h3> <ul> <li>Fix an issue where wheels built on Windows could contain duplicate entries in the RECORD file (<a href="https://github.com/python-poetry/poetry-core/pull/555">#555</a>).</li> </ul> <h2 id="140---2023-02-27"><a href="https://github.com/python-poetry/poetry/releases/tag/1.4.0">1.4.0</a> - 2023-02-27</h2> <h3 id="added-12">Added</h3> <ul> <li><strong>Add a modern installer (<code>installer.modern-installation</code>) for faster installation of packages and independence from pip</strong> (<a href="https://github.com/python-poetry/poetry/pull/6205">#6205</a>).</li> <li>Add support for <code>Private ::</code> trove classifiers (<a href="https://github.com/python-poetry/poetry/pull/7271">#7271</a>).</li> <li>Add the version of poetry in the <code>@generated</code> comment at the beginning of the lock file (<a href="https://github.com/python-poetry/poetry/pull/7339">#7339</a>).</li> <li>Add support for <code>virtualenvs.prefer-active-python</code> when running <code>poetry new</code> and <code>poetry init</code> (<a href="https://github.com/python-poetry/poetry/pull/7100">#7100</a>).</li> </ul> <h3 id="changed-18">Changed</h3> <ul> <li><strong>Deprecate the old installer, i.e. setting <code>experimental.new-installer</code> to <code>false</code></strong> (<a href="https://github.com/python-poetry/poetry/pull/7358">#7358</a>).</li> <li>Remove unused <code>platform</code> field from cached package info and bump the cache version (<a href="https://github.com/python-poetry/poetry/pull/7304">#7304</a>).</li> <li>Extra dependencies of the root project are now sorted in the lock file (<a href="https://github.com/python-poetry/poetry/pull/7375">#7375</a>).</li> <li>Remove upper boundary for <code>importlib-metadata</code> dependency (<a href="https://github.com/python-poetry/poetry/pull/7434">#7434</a>).</li> <li>Validate path dependencies during use instead of during construction (<a href="https://github.com/python-poetry/poetry/pull/6844">#6844</a>).</li> <li>Remove the deprecated <code>repository</code> modules (<a href="https://github.com/python-poetry/poetry/pull/7468">#7468</a>).</li> </ul> <h3 id="fixed-25">Fixed</h3> <ul> <li>Fix an issue where an unconditional dependency of an extra was not installed in specific environments (<a href="https://github.com/python-poetry/poetry/pull/7175">#7175</a>).</li> <li>Fix an issue where a pre-release of a dependency was chosen even if a stable release fulfilled the constraint (<a href="https://github.com/python-poetry/poetry/pull/7225">#7225</a>, <a href="https://github.com/python-poetry/poetry/pull/7236">#7236</a>).</li> <li>Fix an issue where HTTP redirects were not handled correctly during publishing (<a href="https://github.com/python-poetry/poetry/pull/7160">#7160</a>).</li> <li>Fix an issue where <code>poetry check</code> did not handle the <code>-C, --directory</code> option correctly (<a href="https://github.com/python-poetry/poetry/pull/7241">#7241</a>).</li> <li>Fix an issue where the subdirectory information of a git dependency was not written to the lock file (<a href="https://github.com/python-poetry/poetry/pull/7367">#7367</a>).</li> <li>Fix an issue where the wrong Python version was selected when creating an virtual environment (<a href="https://github.com/python-poetry/poetry/pull/7221">#7221</a>).</li> <li>Fix an issue where packages that should be kept were uninstalled when calling <code>poetry install --sync</code> (<a href="https://github.com/python-poetry/poetry/pull/7389">#7389</a>).</li> <li>Fix an issue where an incorrect value was set for <code>sys.argv[0]</code> when running installed scripts (<a href="https://github.com/python-poetry/poetry/pull/6737">#6737</a>).</li> <li>Fix an issue where hashes in <code>direct_url.json</code> files were not written according to the specification (<a href="https://github.com/python-poetry/poetry/pull/7475">#7475</a>).</li> <li>Fix an issue where poetry commands failed due to special characters in the path of the project or virtual environment (<a href="https://github.com/python-poetry/poetry/pull/7471">#7471</a>).</li> <li>Fix an issue where poetry crashed with a <code>JSONDecodeError</code> when running a Python script that produced certain warnings (<a href="https://github.com/python-poetry/poetry/pull/6665">#6665</a>).</li> </ul> <h3 id="docs-17">Docs</h3> <ul> <li>Add advice on how to maintain a poetry plugin (<a href="https://github.com/python-poetry/poetry/pull/6977">#6977</a>).</li> <li>Update tox examples to comply with the latest tox release (<a href="https://github.com/python-poetry/poetry/pull/7341">#7341</a>).</li> <li>Mention that the <code>poetry export</code> can export <code>constraints.txt</code> files (<a href="https://github.com/python-poetry/poetry/pull/7383">#7383</a>).</li> <li>Add clarifications for moving configuration files (<a href="https://github.com/python-poetry/poetry/pull/6864">#6864</a>).</li> <li>Mention the different types of exact version specifications (<a href="https://github.com/python-poetry/poetry/pull/7503">#7503</a>).</li> </ul> <h3 id="poetry-core-151httpsgithubcompython-poetrypoetry-corereleasestag151">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/1.5.1"><code>1.5.1</code></a>)</h3> <ul> <li>Improve marker handling (<a href="https://github.com/python-poetry/poetry-core/pull/528">#528</a>, <a href="https://github.com/python-poetry/poetry-core/pull/534">#534</a>, <a href="https://github.com/python-poetry/poetry-core/pull/530">#530</a>, <a href="https://github.com/python-poetry/poetry-core/pull/546">#546</a>, <a href="https://github.com/python-poetry/poetry-core/pull/547">#547</a>).</li> <li>Validate whether dependencies referenced in <code>extras</code> are defined in the main dependency group (<a href="https://github.com/python-poetry/poetry-core/pull/542">#542</a>).</li> <li>Poetry no longer generates a <code>setup.py</code> file in sdists by default (<a href="https://github.com/python-poetry/poetry-core/pull/318">#318</a>).</li> <li>Fix an issue where trailing newlines were allowed in <code>tool.poetry.description</code> (<a href="https://github.com/python-poetry/poetry-core/pull/505">#505</a>).</li> <li>Fix an issue where the name of the data folder in wheels was not normalized (<a href="https://github.com/python-poetry/poetry-core/pull/532">#532</a>).</li> <li>Fix an issue where the order of entries in the RECORD file was not deterministic (<a href="https://github.com/python-poetry/poetry-core/pull/545">#545</a>).</li> <li>Fix an issue where zero padding was not correctly handled in version comparisons (<a href="https://github.com/python-poetry/poetry-core/pull/540">#540</a>).</li> <li>Fix an issue where sdist builds did not support multiple READMEs (<a href="https://github.com/python-poetry/poetry-core/pull/486">#486</a>).</li> </ul> <h3 id="poetry-plugin-export-130httpsgithubcompython-poetrypoetry-plugin-exportreleasestag130">poetry-plugin-export (<a href="https://github.com/python-poetry/poetry-plugin-export/releases/tag/1.3.0"><code>^1.3.0</code></a>)</h3> <ul> <li>Fix an issue where the export failed if there was a circular dependency on the root package (<a href="https://github.com/python-poetry/poetry-plugin-export/pull/118">#118</a>).</li> </ul> <h2 id="132---2023-01-10"><a href="https://github.com/python-poetry/poetry/releases/tag/1.3.2">1.3.2</a> - 2023-01-10</h2> <h3 id="fixed-26">Fixed</h3> <ul> <li>Fix a performance regression when locking dependencies from PyPI (<a href="https://github.com/python-poetry/poetry/pull/7232">#7232</a>).</li> <li>Fix an issue where passing a relative path via <code>-C, --directory</code> fails (<a href="https://github.com/python-poetry/poetry/pull/7266">#7266</a>).</li> </ul> <h3 id="docs-18">Docs</h3> <ul> <li>Update docs to reflect the removal of the deprecated <code>get-poetry.py</code> installer from the repository (<a href="https://github.com/python-poetry/poetry/pull/7288">#7288</a>).</li> <li>Add clarifications for <code>virtualenvs.path</code> settings (<a href="https://github.com/python-poetry/poetry/pull/7286">#7286</a>).</li> </ul> <h2 id="131---2022-12-12"><a href="https://github.com/python-poetry/poetry/releases/tag/1.3.1">1.3.1</a> - 2022-12-12</h2> <h3 id="fixed-27">Fixed</h3> <ul> <li>Fix an issue where an explicit dependency on <code>lockfile</code> was missing, resulting in a broken Poetry in rare circumstances (<a href="https://github.com/python-poetry/poetry/pull/7169">7169</a>).</li> </ul> <h2 id="130---2022-12-09"><a href="https://github.com/python-poetry/poetry/releases/tag/1.3.0">1.3.0</a> - 2022-12-09</h2> <h3 id="added-13">Added</h3> <ul> <li>Mark the lock file with an <code>@generated</code> comment as used by common tooling (<a href="https://github.com/python-poetry/poetry/pull/2773">#2773</a>).</li> <li><code>poetry check</code> validates trove classifiers and warns for deprecations (<a href="https://github.com/python-poetry/poetry/pull/2881">#2881</a>).</li> <li>Introduce a top level <code>-C, --directory</code> option to set the working path (<a href="https://github.com/python-poetry/poetry/pull/6810">#6810</a>).</li> </ul> <h3 id="changed-19">Changed</h3> <ul> <li><strong>New lock file format (version 2.0)</strong> (<a href="https://github.com/python-poetry/poetry/pull/6393">#6393</a>).</li> <li>Path dependency metadata is unconditionally re-locked (<a href="https://github.com/python-poetry/poetry/pull/6843">#6843</a>).</li> <li>URL dependency hashes are locked (<a href="https://github.com/python-poetry/poetry/pull/7121">#7121</a>).</li> <li><code>poetry update</code> and <code>poetry lock</code> should now resolve dependencies more similarly (<a href="https://github.com/python-poetry/poetry/pull/6477">#6477</a>).</li> <li><code>poetry publish</code> will report more useful errors when a file does not exist (<a href="https://github.com/python-poetry/poetry/pull/4417">#4417</a>).</li> <li><code>poetry add</code> will check for duplicate entries using canonical names (<a href="https://github.com/python-poetry/poetry/pull/6832">#6832</a>).</li> <li>Wheels are preferred to source distributions when gathering metadata (<a href="https://github.com/python-poetry/poetry/pull/6547">#6547</a>).</li> <li>Git dependencies of extras are only fetched if the extra is requested (<a href="https://github.com/python-poetry/poetry/pull/6615">#6615</a>).</li> <li>Invoke <code>pip</code> with <code>--no-input</code> to prevent hanging without feedback (<a href="https://github.com/python-poetry/poetry/pull/6724">#6724</a>, <a href="https://github.com/python-poetry/poetry/pull/6966">#6966</a>).</li> <li>Invoke <code>pip</code> with <code>--isolated</code> to prevent the influence of user configuration (<a href="https://github.com/python-poetry/poetry/pull/6531">#6531</a>).</li> <li>Interrogate environments with Python in isolated (<code>-I</code>) mode (<a href="https://github.com/python-poetry/poetry/pull/6628">#6628</a>).</li> <li>Raise an informative error when multiple version constraints overlap and are incompatible (<a href="https://github.com/python-poetry/poetry/pull/7098">#7098</a>).</li> </ul> <h3 id="fixed-28">Fixed</h3> <ul> <li><strong>Fix an issue where concurrent instances of Poetry would corrupt the artifact cache</strong> (<a href="https://github.com/python-poetry/poetry/pull/6186">#6186</a>).</li> <li><strong>Fix an issue where Poetry can hang after being interrupted due to stale locking in cache</strong> (<a href="https://github.com/python-poetry/poetry/pull/6471">#6471</a>).</li> <li>Fix an issue where the output of commands executed with <code>--dry-run</code> contained duplicate entries (<a href="https://github.com/python-poetry/poetry/pull/4660">#4660</a>).</li> <li>Fix an issue where <code>requests</code>&rsquo;s pool size did not match the number of installer workers (<a href="https://github.com/python-poetry/poetry/pull/6805">#6805</a>).</li> <li>Fix an issue where <code>poetry show --outdated</code> failed with a runtime error related to direct origin dependencies (<a href="https://github.com/python-poetry/poetry/pull/6016">#6016</a>).</li> <li>Fix an issue where only the last command of an <code>ApplicationPlugin</code> is registered (<a href="https://github.com/python-poetry/poetry/pull/6304">#6304</a>).</li> <li>Fix an issue where git dependencies were fetched unnecessarily when running <code>poetry lock --no-update</code> (<a href="https://github.com/python-poetry/poetry/pull/6131">#6131</a>).</li> <li>Fix an issue where stdout was polluted with messages that should go to stderr (<a href="https://github.com/python-poetry/poetry/pull/6429">#6429</a>).</li> <li>Fix an issue with <code>poetry shell</code> activation and zsh (<a href="https://github.com/python-poetry/poetry/pull/5795">#5795</a>).</li> <li>Fix an issue where a url dependencies were shown as outdated (<a href="https://github.com/python-poetry/poetry/pull/6396">#6396</a>).</li> <li>Fix an issue where the <code>source</code> field of a dependency with extras was ignored (<a href="https://github.com/python-poetry/poetry/pull/6472">#6472</a>).</li> <li>Fix an issue where a package from the wrong source was installed for a multiple-constraints dependency with different sources (<a href="https://github.com/python-poetry/poetry/pull/6747">#6747</a>).</li> <li>Fix an issue where dependencies from different sources where merged during dependency resolution (<a href="https://github.com/python-poetry/poetry/pull/6679">#6679</a>).</li> <li>Fix an issue where <code>experimental.system-git-client</code> could not be used via environment variable (<a href="https://github.com/python-poetry/poetry/pull/6783">#6783</a>).</li> <li>Fix an issue where Poetry fails with an <code>AssertionError</code> due to <code>distribution.files</code> being <code>None</code> (<a href="https://github.com/python-poetry/poetry/pull/6788">#6788</a>).</li> <li>Fix an issue where <code>poetry env info</code> did not respect <code>virtualenvs.prefer-active-python</code> (<a href="https://github.com/python-poetry/poetry/pull/6986">#6986</a>).</li> <li>Fix an issue where <code>poetry env list</code> does not list the in-project environment (<a href="https://github.com/python-poetry/poetry/pull/6979">#6979</a>).</li> <li>Fix an issue where <code>poetry env remove</code> removed the wrong environment (<a href="https://github.com/python-poetry/poetry/pull/6195">#6195</a>).</li> <li>Fix an issue where the return code of a script was not relayed as exit code (<a href="https://github.com/python-poetry/poetry/pull/6824">#6824</a>).</li> <li>Fix an issue where the solver could silently swallow <code>ValueError</code> (<a href="https://github.com/python-poetry/poetry/pull/6790">#6790</a>).</li> </ul> <h3 id="docs-19">Docs</h3> <ul> <li>Improve documentation of package sources (<a href="https://github.com/python-poetry/poetry/pull/5605">#5605</a>).</li> <li>Correct the default cache path on Windows (<a href="https://github.com/python-poetry/poetry/pull/7012">#7012</a>).</li> </ul> <h3 id="poetry-core-140httpsgithubcompython-poetrypoetry-corereleasestag140">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/1.4.0"><code>1.4.0</code></a>)</h3> <ul> <li>The PEP 517 <code>metadata_directory</code> is now respected as an input to the <code>build_wheel</code> hook (<a href="https://github.com/python-poetry/poetry-core/pull/487">#487</a>).</li> <li><code>ParseConstraintError</code> is now raised on version and constraint parsing errors, and includes information on the package that caused the error (<a href="https://github.com/python-poetry/poetry-core/pull/514">#514</a>).</li> <li>Fix an issue where invalid PEP 508 requirements were generated due to a missing space before semicolons (<a href="https://github.com/python-poetry/poetry-core/pull/510">#510</a>).</li> <li>Fix an issue where relative paths were encoded into package requirements, instead of a file:// URL as required by PEP 508 (<a href="https://github.com/python-poetry/poetry-core/pull/512">#512</a>).</li> </ul> <h3 id="poetry-plugin-export-120httpsgithubcompython-poetrypoetry-plugin-exportreleasestag120">poetry-plugin-export (<a href="https://github.com/python-poetry/poetry-plugin-export/releases/tag/1.2.0"><code>^1.2.0</code></a>)</h3> <ul> <li>Ensure compatibility with Poetry 1.3.0. No functional changes.</li> </ul> <h3 id="cleo-200httpsgithubcompython-poetrypoetry-corereleasestag200">cleo (<a href="https://github.com/python-poetry/poetry-core/releases/tag/2.0.0"><code>^2.0.0</code></a>)</h3> <ul> <li>Fix an issue where shell completions had syntax errors (<a href="https://github.com/python-poetry/cleo/pull/247">#247</a>).</li> <li>Fix an issue where not reading all the output of a command resulted in a &ldquo;Broken pipe&rdquo; error (<a href="https://github.com/python-poetry/cleo/pull/165">#165</a>).</li> <li>Fix an issue where errors were not shown in non-verbose mode (<a href="https://github.com/python-poetry/cleo/pull/166">#166</a>).</li> </ul> <h2 id="122---2022-10-10"><a href="https://github.com/python-poetry/poetry/releases/tag/1.2.2">1.2.2</a> - 2022-10-10</h2> <h3 id="added-14">Added</h3> <ul> <li>Add forward compatibility for lock file format 2.0, which will be used by Poetry 1.3 (<a href="https://github.com/python-poetry/poetry/pull/6608">#6608</a>).</li> </ul> <h3 id="changed-20">Changed</h3> <ul> <li>Allow <code>poetry lock</code> to re-generate the lock file when invalid or incompatible (<a href="https://github.com/python-poetry/poetry/pull/6753">#6753</a>).</li> </ul> <h3 id="fixed-29">Fixed</h3> <ul> <li>Fix an issue where the deprecated JSON API was used to query PyPI for available versions of a package (<a href="https://github.com/python-poetry/poetry/pull/6081">#6081</a>).</li> <li>Fix an issue where versions were escaped wrongly when building the wheel name (<a href="https://github.com/python-poetry/poetry/pull/6476">#6476</a>).</li> <li>Fix an issue where the installation of dependencies failed if pip is a dependency and is updated in parallel to other dependencies (<a href="https://github.com/python-poetry/poetry/pull/6582">#6582</a>).</li> <li>Fix an issue where the names of extras were not normalized according to PEP 685 (<a href="https://github.com/python-poetry/poetry/pull/6541">#6541</a>).</li> <li>Fix an issue where sdist names were not normalized (<a href="https://github.com/python-poetry/poetry/pull/6621">#6621</a>).</li> <li>Fix an issue where invalid constraints, which are ignored, were only reported in a debug message instead of a warning (<a href="https://github.com/python-poetry/poetry/pull/6730">#6730</a>).</li> <li>Fix an issue where <code>poetry shell</code> was broken in git bash on Windows (<a href="https://github.com/python-poetry/poetry/pull/6560">#6560</a>).</li> </ul> <h3 id="docs-20">Docs</h3> <ul> <li>Rework the README and contribution docs (<a href="https://github.com/python-poetry/poetry/pull/6552">#6552</a>).</li> <li>Fix for inconsistent docs for multiple-constraint dependencies (<a href="https://github.com/python-poetry/poetry/pull/6604">#6604</a>).</li> <li>Rephrase plugin configuration (<a href="https://github.com/python-poetry/poetry/pull/6557">#6557</a>).</li> <li>Add a note about publishable repositories to <code>publish</code> (<a href="https://github.com/python-poetry/poetry/pull/6641">#6641</a>).</li> <li>Fix the path for lazy-loaded bash completion (<a href="https://github.com/python-poetry/poetry/pull/6656">#6656</a>).</li> <li>Fix a reference to the invalid option <code>--require</code> (<a href="https://github.com/python-poetry/poetry/pull/6672">#6672</a>).</li> <li>Add a PowerShell one-liner to the basic usage section (<a href="https://github.com/python-poetry/poetry/pull/6683">#6683</a>).</li> <li>Fix the minimum poetry version in the example for plugins (<a href="https://github.com/python-poetry/poetry/pull/6739">#6739</a>).</li> </ul> <h3 id="poetry-core-132httpsgithubcompython-poetrypoetry-corereleasestag132">poetry-core (<a href="https://github.com/python-poetry/poetry-core/releases/tag/1.3.2"><code>1.3.2</code></a>)</h3> <ul> <li>Add <code>3.11</code> to the list of available Python versions (<a href="https://github.com/python-poetry/poetry-core/pull/477">#477</a>).</li> <li>Fix an issue where caret constraints of pre-releases with a major version of 0 resulted in an empty version range (<a href="https://github.com/python-poetry/poetry-core/pull/475">#475</a>).</li> </ul> <h3 id="poetry-plugin-export-112httpsgithubcompython-poetrypoetry-plugin-exportreleasestag112">poetry-plugin-export (<a href="https://github.com/python-poetry/poetry-plugin-export/releases/tag/1.1.2"><code>^1.1.2</code></a>)</h3> <ul> <li>Add support for exporting <code>constraints.txt</code> files (<a href="https://github.com/python-poetry/poetry-plugin-export/pull/128">#128</a>).</li> <li>Fix an issue where a relative path passed via <code>-o</code> was not interpreted relative to the current working directory (<a href="https://github.com/python-poetry/poetry-plugin-export/pull/130">#130</a>).</li> </ul> <h2 id="121---2022-09-16"><a href="https://github.com/python-poetry/poetry/releases/tag/1.2.1">1.2.1</a> - 2022-09-16</h2> <h3 id="changed-21">Changed</h3> <ul> <li>Bump <code>poetry-core</code> to <a href="https://github.com/python-poetry/poetry-core/releases/tag/1.2.0"><code>1.2.0</code></a>.</li> <li>Bump <code>poetry-plugin-export</code> to <a href="https://github.com/python-poetry/poetry-plugin-export/releases/tag/1.0.7"><code>^1.0.7</code></a>.</li> </ul> <h3 id="fixed-30">Fixed</h3> <ul> <li>Fix an issue where <code>poetry cache clear</code> did not respect the <code>-n/--no-interaction</code> flag (<a href="https://github.com/python-poetry/poetry/pull/6338">#6338</a>).</li> <li>Fix an issue where <code>poetry lock --no-update</code> updated dependencies from non-PyPI package sources (<a href="https://github.com/python-poetry/poetry/pull/6335">#6335</a>).</li> <li>Fix a <code>poetry install</code> performance regression by falling back to internal pip (<a href="https://github.com/python-poetry/poetry/pull/6062">#6062</a>).</li> <li>Fix an issue where a virtual environment was created unnecessarily when running <code>poetry export</code> (<a href="https://github.com/python-poetry/poetry/pull/6282">#6282</a>).</li> <li>Fix an issue where <code>poetry lock --no-update</code> added duplicate hashes to the lock file (<a href="https://github.com/python-poetry/poetry/pull/6389">#6389</a>).</li> <li>Fix an issue where <code>poetry install</code> fails because of missing hashes for <code>url</code> dependencies (<a href="https://github.com/python-poetry/poetry/pull/6389">#6389</a>).</li> <li>Fix an issue where Poetry was not able to update pip in Windows virtual environments (<a href="https://github.com/python-poetry/poetry/pull/6430">#6430</a>).</li> <li>Fix an issue where Poetry was not able to install releases that contained less common link types (<a href="https://github.com/python-poetry/poetry/pull/5767">#5767</a>).</li> <li>Fix a <code>poetry lock</code> performance regression when checking non-PyPI sources for yanked versions (<a href="https://github.com/python-poetry/poetry/pull/6442">#6442</a>).</li> <li>Fix an issue where <code>--no-cache</code> was not respected when running <code>poetry install</code> (<a href="https://github.com/python-poetry/poetry/pull/6479">#6479</a>).</li> <li>Fix an issue where deprecation warnings for <code>--dev</code> were missing (<a href="https://github.com/python-poetry/poetry/pull/6475">#6475</a>).</li> <li>Fix an issue where Git dependencies failed to clone when <code>insteadOf</code> was used in <code>.gitconfig</code> using the Dulwich Git client (<a href="https://github.com/python-poetry/poetry/pull/6506">#6506</a>).</li> <li>Fix an issue where no cache entry is found when calling <code>poetry cache clear</code> with a non-normalized package name (<a href="https://github.com/python-poetry/poetry/pull/6537">#6537</a>).</li> <li>Fix an invalid virtualenv constraint on Poetry (<a href="https://github.com/python-poetry/poetry/pull/6402">#6402</a>).</li> <li>Fix outdated build system requirements for Poetry (<a href="https://github.com/python-poetry/poetry/pull/6509">#6509</a>).</li> </ul> <h3 id="docs-21">Docs</h3> <ul> <li>Add missing path segment to paths used by install.python-poetry.org (<a href="https://github.com/python-poetry/poetry/pull/6311">#6311</a>).</li> <li>Add recommendations about how to install Poetry in a CI environment (<a href="https://github.com/python-poetry/poetry/pull/6345">#6345</a>).</li> <li>Fix examples for <code>--with</code> and <code>--without</code> (<a href="https://github.com/python-poetry/poetry/pull/6318">#6318</a>).</li> <li>Update configuration folder path for macOS (<a href="https://github.com/python-poetry/poetry/pull/6395">#6395</a>).</li> <li>Improve the description of the <code>virtualenv.create</code> option (<a href="https://github.com/python-poetry/poetry/pull/6460">#6460</a>).</li> <li>Clarify that <code>poetry install</code> removes dependencies of non-installed extras (<a href="https://github.com/python-poetry/poetry/pull/6229">#6229</a>).</li> <li>Add a note about <code>pre-commit autoupdate</code> and Poetry&rsquo;s hooks (<a href="https://github.com/python-poetry/poetry/pull/6497">#6497</a>).</li> </ul> <h2 id="120---2022-08-31"><a href="https://github.com/python-poetry/poetry/releases/tag/1.2.0">1.2.0</a> - 2022-08-31</h2> <p>For a detailed breakdown of user-facing changes, refer to the <a href="https://python-poetry.org/blog/announcing-poetry-1.2.0/">1.2.0 release announcement</a>.</p>https://python-poetry.org/docs/libraries/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/libraries/<h1 id="libraries">Libraries</h1> <p>This chapter will tell you how to make your library installable through Poetry.</p> <h2 id="versioning">Versioning</h2> <p>Poetry requires <a href="https://peps.python.org/pep-0440">PEP 440</a>-compliant versions for all projects.</p> <p>While Poetry does not enforce any release convention, it used to encourage the use of <a href="https://semver.org/">semantic versioning</a> within the scope of <a href="https://peps.python.org/pep-0440/#semantic-versioning">PEP 440</a> and supports <a href="https://python-poetry.org/docs/dependency-specification/#caret-requirements">version constraints</a> that are especially suitable for semver.</p> <div class="admonition note"> <div class="title">Note</div> <div class="content">As an example, <code>1.0.0-hotfix.1</code> is not compatible with <a href="https://peps.python.org/pep-0440">PEP 440</a>. You can instead choose to use <code>1.0.0-post1</code> or <code>1.0.0.post1</code>.</div> </div> <h2 id="lock-file">Lock file</h2> <p>For your library, you may commit the <code>poetry.lock</code> file if you want to. This can help your team to always test against the same dependency versions. However, this lock file will not have any effect on other projects that depend on it. It only has an effect on the main project.</p>https://python-poetry.org/docs/1.8/libraries/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/1.8/libraries/<h1 id="libraries">Libraries</h1> <p>This chapter will tell you how to make your library installable through Poetry.</p> <h2 id="versioning">Versioning</h2> <p>Poetry requires <a href="https://peps.python.org/pep-0440">PEP 440</a>-compliant versions for all projects.</p> <p>While Poetry does not enforce any release convention, it used to encourage the use of <a href="https://semver.org/">semantic versioning</a> within the scope of <a href="https://peps.python.org/pep-0440/#semantic-versioning">PEP 440</a> and supports <a href="https://python-poetry.org/docs/1.8/dependency-specification/#caret-requirements">version constraints</a> that are especially suitable for semver.</p> <div class="admonition note"> <div class="title">Note</div> <div class="content">As an example, <code>1.0.0-hotfix.1</code> is not compatible with <a href="https://peps.python.org/pep-0440">PEP 440</a>. You can instead choose to use <code>1.0.0-post1</code> or <code>1.0.0.post1</code>.</div> </div> <h2 id="lock-file">Lock file</h2> <p>For your library, you may commit the <code>poetry.lock</code> file if you want to. This can help your team to always test against the same dependency versions. However, this lock file will not have any effect on other projects that depend on it. It only has an effect on the main project.</p>https://python-poetry.org/docs/main/libraries/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/main/libraries/<h1 id="libraries">Libraries</h1> <p>This chapter will tell you how to make your library installable through Poetry.</p> <h2 id="versioning">Versioning</h2> <p>Poetry requires <a href="https://peps.python.org/pep-0440">PEP 440</a>-compliant versions for all projects.</p> <p>While Poetry does not enforce any release convention, it used to encourage the use of <a href="https://semver.org/">semantic versioning</a> within the scope of <a href="https://peps.python.org/pep-0440/#semantic-versioning">PEP 440</a> and supports <a href="https://python-poetry.org/docs/main/dependency-specification/#caret-requirements">version constraints</a> that are especially suitable for semver.</p> <div class="admonition note"> <div class="title">Note</div> <div class="content">As an example, <code>1.0.0-hotfix.1</code> is not compatible with <a href="https://peps.python.org/pep-0440">PEP 440</a>. You can instead choose to use <code>1.0.0-post1</code> or <code>1.0.0.post1</code>.</div> </div> <h2 id="lock-file">Lock file</h2> <p>For your library, you may commit the <code>poetry.lock</code> file if you want to. This can help your team to always test against the same dependency versions. However, this lock file will not have any effect on other projects that depend on it. It only has an effect on the main project.</p>https://python-poetry.org/docs/managing-dependencies/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/managing-dependencies/<h1 id="managing-dependencies">Managing dependencies</h1> <p>Poetry supports specifying main dependencies in the <a href="https://python-poetry.org/docs/pyproject/#dependencies"><code>project.dependencies</code></a> section of your <code>pyproject.toml</code> according to PEP 621. For legacy reasons and to define additional information that are only used by Poetry the <a href="https://python-poetry.org/docs/pyproject/#dependencies-and-dependency-groups"><code>tool.poetry.dependencies</code></a> sections can be used.</p> <p>See <a href="https://python-poetry.org/docs/dependency-specification/">Dependency specification</a> for more information.</p> <h2 id="dependency-groups">Dependency groups</h2> <p>Poetry provides a way to <strong>organize</strong> your dependencies by <strong>groups</strong>.</p> <p>The dependencies declared in <code>project.dependencies</code> respectively <code>tool.poetry.dependencies</code> are part of an implicit <code>main</code> group. Those dependencies are required by your project during runtime.</p>https://python-poetry.org/docs/1.8/managing-dependencies/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/1.8/managing-dependencies/<h1 id="managing-dependencies">Managing dependencies</h1> <h2 id="dependency-groups">Dependency groups</h2> <p>Poetry provides a way to <strong>organize</strong> your dependencies by <strong>groups</strong>. For instance, you might have dependencies that are only needed to test your project or to build the documentation.</p> <p>To declare a new dependency group, use a <code>tool.poetry.group.&lt;group&gt;</code> section where <code>&lt;group&gt;</code> is the name of your dependency group (for instance, <code>test</code>):</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-toml" data-lang="toml"><span class="line"><span class="cl"><span class="p">[</span><span class="nx">tool</span><span class="p">.</span><span class="nx">poetry</span><span class="p">.</span><span class="nx">group</span><span class="p">.</span><span class="nx">test</span><span class="p">]</span> <span class="c"># This part can be left out</span> </span></span><span class="line"><span class="cl"> </span></span><span class="line"><span class="cl"><span class="p">[</span><span class="nx">tool</span><span class="p">.</span><span class="nx">poetry</span><span class="p">.</span><span class="nx">group</span><span class="p">.</span><span class="nx">test</span><span class="p">.</span><span class="nx">dependencies</span><span class="p">]</span> </span></span><span class="line"><span class="cl"><span class="nx">pytest</span> <span class="p">=</span> <span class="s2">&#34;^6.0.0&#34;</span> </span></span><span class="line"><span class="cl"><span class="nx">pytest-mock</span> <span class="p">=</span> <span class="s2">&#34;*&#34;</span> </span></span></code></pre></div><div class="admonition note"> <div class="title">Note</div> <div class="content"><p>All dependencies <strong>must be compatible with each other</strong> across groups since they will be resolved regardless of whether they are required for installation or not (see <a href="#installing-group-dependencies">Installing group dependencies</a>).</p>https://python-poetry.org/docs/main/managing-dependencies/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/main/managing-dependencies/<h1 id="managing-dependencies">Managing dependencies</h1> <p>Poetry supports specifying main dependencies in the <a href="https://python-poetry.org/docs/main/pyproject/#dependencies"><code>project.dependencies</code></a> section of your <code>pyproject.toml</code> according to PEP 621. For legacy reasons and to define additional information that are only used by Poetry the <a href="https://python-poetry.org/docs/main/pyproject/#dependencies-and-dependency-groups"><code>tool.poetry.dependencies</code></a> sections can be used.</p> <p>See <a href="https://python-poetry.org/docs/main/dependency-specification/">Dependency specification</a> for more information.</p> <h2 id="dependency-groups">Dependency groups</h2> <p>Poetry provides a way to <strong>organize</strong> your dependencies by <strong>groups</strong>.</p> <p>The dependencies declared in <code>project.dependencies</code> respectively <code>tool.poetry.dependencies</code> are part of an implicit <code>main</code> group. Those dependencies are required by your project during runtime.</p>https://python-poetry.org/docs/managing-environments/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/managing-environments/<h1 id="managing-environments">Managing environments</h1> <p>Poetry makes project environment isolation one of its core features.</p> <p>What this means is that it will always work isolated from your global Python installation. To achieve this, it will first check if it&rsquo;s currently running inside a virtual environment. If it is, it will use it directly without creating a new one. But if it&rsquo;s not, it will use one that it has already created or create a brand new one for you.</p>https://python-poetry.org/docs/1.8/managing-environments/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/1.8/managing-environments/<h1 id="managing-environments">Managing environments</h1> <p>Poetry makes project environment isolation one of its core features.</p> <p>What this means is that it will always work isolated from your global Python installation. To achieve this, it will first check if it&rsquo;s currently running inside a virtual environment. If it is, it will use it directly without creating a new one. But if it&rsquo;s not, it will use one that it has already created or create a brand new one for you.</p>https://python-poetry.org/docs/main/managing-environments/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/main/managing-environments/<h1 id="managing-environments">Managing environments</h1> <p>Poetry makes project environment isolation one of its core features.</p> <p>What this means is that it will always work isolated from your global Python installation. To achieve this, it will first check if it&rsquo;s currently running inside a virtual environment. If it is, it will use it directly without creating a new one. But if it&rsquo;s not, it will use one that it has already created or create a brand new one for you.</p>https://python-poetry.org/docs/plugins/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/plugins/<h1 id="plugins">Plugins</h1> <p>Poetry supports using and building plugins if you wish to alter or expand Poetry&rsquo;s functionality with your own.</p> <p>For example if your environment poses special requirements on the behaviour of Poetry which do not apply to the majority of its users or if you wish to accomplish something with Poetry in a way that is not desired by most users.</p> <p>In these cases you could consider creating a plugin to handle your specific logic.</p>https://python-poetry.org/docs/1.8/plugins/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/1.8/plugins/<h1 id="plugins">Plugins</h1> <p>Poetry supports using and building plugins if you wish to alter or expand Poetry&rsquo;s functionality with your own.</p> <p>For example if your environment poses special requirements on the behaviour of Poetry which do not apply to the majority of its users or if you wish to accomplish something with Poetry in a way that is not desired by most users.</p> <p>In these cases you could consider creating a plugin to handle your specific logic.</p>https://python-poetry.org/docs/main/plugins/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/main/plugins/<h1 id="plugins">Plugins</h1> <p>Poetry supports using and building plugins if you wish to alter or expand Poetry&rsquo;s functionality with your own.</p> <p>For example if your environment poses special requirements on the behaviour of Poetry which do not apply to the majority of its users or if you wish to accomplish something with Poetry in a way that is not desired by most users.</p> <p>In these cases you could consider creating a plugin to handle your specific logic.</p>https://python-poetry.org/docs/pre-commit-hooks/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/pre-commit-hooks/<h1 id="pre-commit-hooks">pre-commit hooks</h1> <p>pre-commit is a framework for building and running <a href="https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks">git hooks</a>. See the official documentation for more information: <a href="https://pre-commit.com/">pre-commit.com</a></p> <p>This document provides a list of available pre-commit hooks provided by Poetry.</p> <div class="admonition note"> <div class="title">Note</div> <div class="content">If you specify the <code>args:</code> for a hook in your <code>.pre-commit-config.yaml</code>, the defaults are overwritten. You must fully specify all arguments for your hook if you make use of <code>args:</code>.</div> </div> <div class="admonition note"> <div class="title">Note</div> <div class="content">If the <code>pyproject.toml</code> file is not in the root directory, you can specify <code>args: [&quot;-C&quot;, &quot;./subdirectory&quot;]</code>.</div> </div> <h2 id="poetry-check">poetry-check</h2> <p>The <code>poetry-check</code> hook calls the <code>poetry check</code> command to make sure the poetry configuration does not get committed in a broken state.</p>https://python-poetry.org/docs/1.8/pre-commit-hooks/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/1.8/pre-commit-hooks/<h1 id="pre-commit-hooks">pre-commit hooks</h1> <p>pre-commit is a framework for building and running <a href="https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks">git hooks</a>. See the official documentation for more information: <a href="https://pre-commit.com/">pre-commit.com</a></p> <p>This document provides a list of available pre-commit hooks provided by Poetry.</p> <div class="admonition note"> <div class="title">Note</div> <div class="content">If you specify the <code>args:</code> for a hook in your <code>.pre-commit-config.yaml</code>, the defaults are overwritten. You must fully specify all arguments for your hook if you make use of <code>args:</code>.</div> </div> <div class="admonition note"> <div class="title">Note</div> <div class="content">If the <code>pyproject.toml</code> file is not in the root directory, you can specify <code>args: [&quot;-C&quot;, &quot;./subdirectory&quot;]</code>.</div> </div> <h2 id="poetry-check">poetry-check</h2> <p>The <code>poetry-check</code> hook calls the <code>poetry check</code> command to make sure the poetry configuration does not get committed in a broken state.</p>https://python-poetry.org/docs/main/pre-commit-hooks/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/main/pre-commit-hooks/<h1 id="pre-commit-hooks">pre-commit hooks</h1> <p>pre-commit is a framework for building and running <a href="https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks">git hooks</a>. See the official documentation for more information: <a href="https://pre-commit.com/">pre-commit.com</a></p> <p>This document provides a list of available pre-commit hooks provided by Poetry.</p> <div class="admonition note"> <div class="title">Note</div> <div class="content">If you specify the <code>args:</code> for a hook in your <code>.pre-commit-config.yaml</code>, the defaults are overwritten. You must fully specify all arguments for your hook if you make use of <code>args:</code>.</div> </div> <div class="admonition note"> <div class="title">Note</div> <div class="content">If the <code>pyproject.toml</code> file is not in the root directory, you can specify <code>args: [&quot;-C&quot;, &quot;./subdirectory&quot;]</code>.</div> </div> <h2 id="poetry-check">poetry-check</h2> <p>The <code>poetry-check</code> hook calls the <code>poetry check</code> command to make sure the poetry configuration does not get committed in a broken state.</p>https://python-poetry.org/docs/repositories/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/repositories/<h1 id="repositories">Repositories</h1> <p>Poetry supports the use of <a href="https://pypi.org">PyPI</a> and private repositories for discovery of packages as well as for publishing your projects.</p> <p>By default, Poetry is configured to use the <a href="https://pypi.org">PyPI</a> repository, for package installation and publishing.</p> <p>So, when you add dependencies to your project, Poetry will assume they are available on PyPI.</p> <p>This represents most cases and will likely be enough for most users.</p> <h3 id="private-repository-example">Private Repository Example</h3> <h4 id="installing-from-private-package-sources">Installing from private package sources</h4> <p>By default, Poetry discovers and installs packages from <a href="https://pypi.org">PyPI</a>. But, you want to install a dependency to your project for a <a href="#simple-api-repository">simple API repository</a>? Let&rsquo;s do it.</p>https://python-poetry.org/docs/1.8/repositories/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/1.8/repositories/<h1 id="repositories">Repositories</h1> <p>Poetry supports the use of <a href="https://pypi.org">PyPI</a> and private repositories for discovery of packages as well as for publishing your projects.</p> <p>By default, Poetry is configured to use the <a href="https://pypi.org">PyPI</a> repository, for package installation and publishing.</p> <p>So, when you add dependencies to your project, Poetry will assume they are available on PyPI.</p> <p>This represents most cases and will likely be enough for most users.</p> <h3 id="private-repository-example">Private Repository Example</h3> <h4 id="installing-from-private-package-sources">Installing from private package sources</h4> <p>By default, Poetry discovers and installs packages from <a href="https://pypi.org">PyPI</a>. But, you want to install a dependency to your project for a <a href="#simple-api-repository">simple API repository</a>? Let&rsquo;s do it.</p>https://python-poetry.org/docs/main/repositories/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/main/repositories/<h1 id="repositories">Repositories</h1> <p>Poetry supports the use of <a href="https://pypi.org">PyPI</a> and private repositories for discovery of packages as well as for publishing your projects.</p> <p>By default, Poetry is configured to use the <a href="https://pypi.org">PyPI</a> repository, for package installation and publishing.</p> <p>So, when you add dependencies to your project, Poetry will assume they are available on PyPI.</p> <p>This represents most cases and will likely be enough for most users.</p> <h3 id="private-repository-example">Private Repository Example</h3> <h4 id="installing-from-private-package-sources">Installing from private package sources</h4> <p>By default, Poetry discovers and installs packages from <a href="https://pypi.org">PyPI</a>. But, you want to install a dependency to your project for a <a href="#simple-api-repository">simple API repository</a>? Let&rsquo;s do it.</p>https://python-poetry.org/docs/pyproject/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/pyproject/<h1 id="the-pyprojecttoml-file">The <code>pyproject.toml</code> file</h1> <p>In package mode, the only required fields are <code>name</code> and <code>version</code> (either in the <code>project</code> section or in the <code>tool.poetry</code> section). Other fields are optional. In non-package mode, the <code>name</code> and <code>version</code> fields are required if using the <code>project</code> section.</p> <div class="admonition note"> <div class="title">Note</div> <div class="content">Run <code>poetry check</code> to print warnings about deprecated fields.</div> </div> <h2 id="the-project-section">The <code>project</code> section</h2> <p>The <code>project</code> section of the <code>pyproject.toml</code> file according to the <a href="https://packaging.python.org/en/latest/specifications/pyproject-toml/#declaring-project-metadata-the-project-table">specification of the PyPA</a>.</p> <h3 id="name">name</h3> <p>The name of the package. <strong>Always required when the <code>project</code> section is specified</strong></p>https://python-poetry.org/docs/1.8/pyproject/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/1.8/pyproject/<h1 id="the-pyprojecttoml-file">The <code>pyproject.toml</code> file</h1> <p>The <code>tool.poetry</code> section of the <code>pyproject.toml</code> file is composed of multiple sections.</p> <h2 id="package-mode">package-mode</h2> <p>Whether Poetry operates in package mode (default) or not. <strong>Optional</strong></p> <p>See <a href="https://python-poetry.org/docs/1.8/basic-usage/#operating-modes">basic usage</a> for more information.</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-toml" data-lang="toml"><span class="line"><span class="cl"><span class="nx">package-mode</span> <span class="p">=</span> <span class="kc">false</span> </span></span></code></pre></div><h2 id="name">name</h2> <p>The name of the package. <strong>Required in package mode</strong></p> <p>This should be a valid name as defined by <a href="https://peps.python.org/pep-0508/#names">PEP 508</a>.</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-toml" data-lang="toml"><span class="line"><span class="cl"><span class="nx">name</span> <span class="p">=</span> <span class="s2">&#34;my-package&#34;</span> </span></span></code></pre></div><h2 id="version">version</h2> <p>The version of the package. <strong>Required in package mode</strong></p> <p>This should be a valid <a href="https://peps.python.org/pep-0440/">PEP 440</a> string.</p>https://python-poetry.org/docs/main/pyproject/Mon, 01 Jan 0001 00:00:00 +0000https://python-poetry.org/docs/main/pyproject/<h1 id="the-pyprojecttoml-file">The <code>pyproject.toml</code> file</h1> <p>In package mode, the only required fields are <code>name</code> and <code>version</code> (either in the <code>project</code> section or in the <code>tool.poetry</code> section). Other fields are optional. In non-package mode, the <code>name</code> and <code>version</code> fields are required if using the <code>project</code> section.</p> <div class="admonition note"> <div class="title">Note</div> <div class="content">Run <code>poetry check</code> to print warnings about deprecated fields.</div> </div> <h2 id="the-project-section">The <code>project</code> section</h2> <p>The <code>project</code> section of the <code>pyproject.toml</code> file according to the <a href="https://packaging.python.org/en/latest/specifications/pyproject-toml/#declaring-project-metadata-the-project-table">specification of the PyPA</a>.</p> <h3 id="name">name</h3> <p>The name of the package. <strong>Always required when the <code>project</code> section is specified</strong></p>