Release 1.1.0b3

[radoering]

Some poetry PRs have been waiting for a new poetry-core beta for some time now. Since the latest poetry beta pinned poetry-core to 1.1.0b2, the risk of a new beta should be low. Thus, I propose to just cut a new poetry-core beta.

(Order of sections according to python-poetry/poetry#5725 (comment).)

Added

• Added support for valid PEP 517 projects with another build-system than poetry-core as directory dependencies (#368, #377).
• Added support for yanked files and releases according to PEP 592 (#400).

Changed

• Relaxed schema validation to allow additional properties (#369).
• Harmonized string representation of dependencies (#393).
• Changed wheel name normalization to follow most recent packaging specification (#394).
• Changed equality check of direct origin dependencies, so that constraints are not considered anymore (#405).
• Deprecated Dependency.set_constraint() and replaced it by a constraint property for consistency (#370).
• Removed Package.requires_extras (#374).
• Improved marker handling (#380, #383, #384, #390, #395).

Fixed

• Fixed hash method for PackageSpecification, Package, Dependency and their sub classes (#370).
• Fixed merging of markers python_version and python_full_version (#382, #388).
• Fixed python version normalization (#385, #407).
• Fixed an issue where version identifiers with a local version segment allowed non local versions (#396).
• Fixed an issue where version identifiers without a post release segment allowed post releases (#396).
• Fixed script definitions that didn't work when extras were not explicitly defined (#404).

[dimbleby]

Does this need still to be a beta? Why not release 1.1.0 proper?

(Arguably it should be 2.0.0 anyway because it surely has breaking changes since 1.0.x: but I'm more keen to encourage dropping the beta tag than I am to debate semantic versioning)

[radoering]

I'm not aware of the full impact of a proper release. I suppose a beta does not influence projects with something like

[build-system]
requires = ["poetry-core>=1.0.0"]

whereas a proper release might. I suppose we will do the proper release of poetry-core immediately before poetry 1.2 and according to python-poetry/poetry#5586 we are still not close enough. (Just my personal opinion.)

[dimbleby]

fwiw I also think it's time to cut poetry 1.2.0 - all the blockers listed in python-poetry/poetry#5586 have fixes pending, let's merge them and go. But it really ought to be possible to cut releases in this project without being blocked on that.

[mkniewallner]

Unless it was left out intentionally, #404 seems to be missing. In Fixed:

- Fixed script definitions that didn't work when extras were not explicitly defined ([#404](https://github.com/python-poetry/poetry-core/pull/404)).

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.8% Duplication

[radoering]

Unless it was left out intentionally, #404 seems to be missing.

Slipped through my fingers. Added it. Thanks. 👍