Releases: python-poetry/poetry
Releases · python-poetry/poetry
1.1.5
Fixed
- Fixed an error in the
export
command when no lock file existed and a verbose flag was passed to the command. (#3310) - Fixed an error where the
pyproject.toml
was not reverted when using theadd
command. (#3622) - Fixed errors when using non-HTTPS indices. (#3622)
- Fixed errors when handling simple indices redirection. (#3622)
- Fixed errors when trying to handle newer wheels by using the latest version of
poetry-core
andpackaging
. (#3677) - Fixed an error when using some versions of
poetry-core
due to an incorrect import . (#3696)
1.1.4
Added
- Added
installer.parallel
boolean flag (defaults totrue
) configuration to enable/disable parallel execution of operations when using the new installer. (#3088)
Changed
- When using system environments as an unprivileged user, user site and bin directories are created if they do not already exist. (#3107)
Fixed
- Fixed editable installation of poetry projects when using system environments. (#3107)
- Fixed locking of nested extra activations. If you were affected by this issue, you will need to regenerate the lock file using
poetry lock --no-update
. (#3229) - Fixed prioritisation of non-default custom package sources. (#3251)
- Fixed detection of installed editable packages when non-poetry managed
.pth
file exists. (#3210) - Fixed scripts generated by editable builder to use valid import statements. (#3214)
- Fixed recursion error when locked dependencies contain cyclic dependencies. (#3237)
- Fixed propagation of editable flag for VCS dependencies. (#3264)
1.1.3
Changed
- Python version support deprecation warning is now written to
stderr
. (#3131)
Fixed
- Fixed
KeyError
whenPATH
is not defined in environment variables. (#3159) - Fixed error when using
config
command in a directory with an existingpyproject.toml
without any Poetry configuration. (#3172) - Fixed incorrect inspection of package requirements when same dependency is specified multiple times with unique markers. (#3147)
- Fixed
show
command to use already resolved package metadata. (#3117) - Fixed multiple issues with
export
command output when usingrequirements.txt
format. (#3119)
1.1.2
Release 1.1.2
1.1.1
Added
- Added
--no-update
option tolock
command. (#3034)
Fixed
- Fixed resolution of packages with missing required extras. (#3035)
- Fixed export of
requirements.txt
dependencies to include development dependencies. (#3024) - Fixed incorrect selection of unsupported binary distribution formats when selecting a package artifact to install. (#3058)
- Fixed incorrect use of system executable when building package distributions via
build
command. (#3056) - Fixed errors in
init
command when specifying--dependency
in non-interactive mode when apyproject.toml
file already exists. (#3076) - Fixed incorrect selection of configured source url when a publish repository url configuration with the same name already exists. (#3047)
- Fixed dependency resolution issues when the same package is specified in multiple dependency extras. (#3046)
1.1.0
Changed
- The
init
command will now use existingpyproject.toml
if possible (#2448). - Error messages when metadata information retrieval fails have been improved (#2997).
Fixed
- Fixed parsing of version constraint for
rc
prereleases (#2978). - Fixed how some metadata information are extracted from
setup.cfg
files (#2957). - Fixed return codes returned by the executor (#2981).
- Fixed whitespaces not being accepted for the list of extras when adding packages (#2985).
- Fixed repositories specified in the
pyproject.toml
file not being taken into account for authentication when downloading packages (#2990). - Fixed permission errors when installing the root project if the
site-packages
directory is not writeable (#3002). - Fixed environment marker propagation when exporting to the
requirements.txt
format (#3002). - Fixed errors when paths in run command contained spaces (#3015).
1.1.0rc1
Changed
- The
virtualenvs.in-project
setting will now always be honored, if set explicitly, regardless of the presence of a.venv
directory (#2771). - Adding packages already present in the
pyproject.toml
file will no longer raise an error (#2886). - Errors when authenticating against custom repositories will now be logged (#2577).
Fixed
- Fixed an error on Python 3.5 when resolving URL dependencies (#2954).
- Fixed the
dependency
option of theinit
command being ignored (#2587). - Fixed the
show
command displaying erroneous information following the changes in the lock file format (#2967). - Fixed dependency resolution errors due to invalid python constraints propagation (#2968).
Notice for FreeBSD Users
For using poetry
on FreeBSD 11 and 13 under Python 3.5, we recommend that you use an installation method other than the get-poetry.py
script.
Installation using get-poetry.py
script of FreeBSD 11 and 13 releases do not included vendored dependencies for Python 3.5 environments. This is due to FreeBSD build environments not provided python35
packages at the time of this release. Users on these environments, with a previous 1.1.0
preview releases should not use poetry update
to consume this release.
FreeBSD 12 release will also drop Python 3.5 vendored dependencies in future releases.
1.1.0b4
1.1.0b3
Changed
- Improved the error reporting when HTTP error are encountered for legacy repositories (#2459).
- When displaying the name of packages retrieved from remote repositories, the original name will now be used (#2305).
- Failed package downloads will now be retried on connection errors (#2813).
- Path dependencies will now be installed as editable only when
develop
option is set totrue
(#2887).
Fixed
- Fixed the detection of the type of installed packages (#2722).
- Fixed deadlocks when installing packages on systems not supporting non-ascii characters (#2721).
- Fixed handling of wildcard constraints for packages with prereleases only (#2821).
- Fixed dependencies of some packages not being discovered by ensuring we use the PEP-516 backend if specified (#2810).
- Fixed recursion errors when retrieving extras (#2787).
- Fixed
PyPI
always being displayed when publishing even for custom repositories (#2905). - Fixed handling of packages extras when resolving dependencies (#2887).