Release 1.2.0a1

[sdispater]

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)
• Poetry no longer uses pip installed within the project virtualenvironment when installing packages. (#4011)
• 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)

[aviramha]

Hi @sdispater,
Any chance to include this #3406 in the release? This is a bug introduced in a patch change, and it is open for few months impacting a lot of users. It'd be wonderful to have it fixed...

[GooseYArd]

#3483 is another critical issue for sites with private https repositories with certs issued by a non-public CA, or anywhere that a custom CA file location is configured via auth.yaml. I'm desperately hoping for this to be merged in time for 1.2.0.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.