1.2.0a1

This release is the first testing release of the upcoming 1.2.0 version.

It drops support for Python 2.7 and 3.5.

Added

• Poetry now supports a plugin system to alter or expand Poetry's functionality. (#3733)
• Poetry now supports PEP 610. (#3876)
• Several configuration options to better control the way virtual environments are created are now available. (#3157, #3711).
• The new command now supports namespace packages. (#2768)
• The add command now supports the --editable option to add packages in editable mode. (#3940)

Changed

• Python 2.7 and 3.5 are no longer supported. (#3405)
• The usage of the get-poetry.py script is now deprecated and is replaced by the install-poetry.py script. (#3706)
• Directory dependencies are now in non-develop mode by default. (poetry-core#98)
• Improved support for PEP 440 specific versions that do not abide by semantic versioning. (poetry-core#140)
• Improved the CLI experience and performance by migrating to the latest version of Cleo. (#3618)
• Packages previously considered as unsafe (pip, setuptools, wheels and distribute) can now be managed as any other package. (#2826)
• The new command now defaults to the Markdown format for README files. (#2768)

Fixed

• Fixed an error where command line options were not taken into account when using the run command. (#3618)
• Fixed an error in the way custom repositories were resolved. (#3406)

1.1.6

Fixed

• Fixed export format for path dependencies. (#3121)
• Fixed errors caused by environment modification when executing some commands. (#3253)
• Fixed handling of wheel files with single-digit versions. (#3338)
• Fixed an error when handling single-digit Python markers. (poetry-core#156)
• Fixed dependency markers not being properly copied when changing the constraint leading to resolution errors. (poetry-core#163)
• Fixed an error where VCS dependencies were always updated. (#3947)
• Fixed an error where the incorrect version of a package was locked when using environment markers. (#3945)

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 the add 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 and packaging. (#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 to true) 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 when PATH is not defined in environment variables. (#3159)
• Fixed error when using config command in a directory with an existing pyproject.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 using requirements.txt format. (#3119)

1.1.2

Release 1.1.2

1.1.1

Added

• Added --no-update option to lock 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 a pyproject.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 existing pyproject.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 the init 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

Changed

• When running under Python 2.7 on Windows, install command will be limited to one worker to mitigate threading issue (#2941).