FS#77375 - [python-poetry-core] poetry-core 1.5.0 breaks poetry 1.3.2

Attached to Project: Community Packages
Opened by Dragoon Aethis (DragoonAethis) - Friday, 03 February 2023, 23:08 GMT
Last edited by Caleb Maclennan (alerque) - Thursday, 02 March 2023, 17:49 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Caleb Maclennan (alerque)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 7
Private No

Details

* python-poetry-core 1.5.0 was released a week ago (and in Arch repos on 31.01) and includes this PR, which removes the 'platform' field from the underlying package model: https://github.com/python-poetry/poetry-core/pull/548
* ...which is a dependency for this PR in the main python-poetry package, mostly doing the same thing: https://github.com/python-poetry/poetry/pull/7304
* ...but the current stable Poetry 1.3.2 still requires those fields and does not yet include the PR listed above.
* Trying to `poetry update` any project with python-poetry 1.3.2 + python-poetry-core 1.5.0 will fail with: `'ProjectPackage' object has no attribute 'platform'`
* Downgrading to poetry-core 1.4.0 resolves this issue.

The missing second PR could also be patched in on top of Poetry 1.3.2, but the upstream project locks the dependent poetry-core version at 1.4.0 for poetry 1.3.2, so a temporary downgrade is probably the correct option: https://github.com/python-poetry/poetry/blob/1.3.2/pyproject.toml#L50
This task depends upon

Closed by  Caleb Maclennan (alerque)
Thursday, 02 March 2023, 17:49 GMT
Reason for closing:  Fixed
Additional comments about closing:  Updated poetry in community should have fixed this.
Comment by Alan Orth (stickyboy) - Tuesday, 07 February 2023, 13:33 GMT
I just hit this issue myself and reported it upstream to poetry. They mentioned that I had somehow gotten conflicting versions of python-poetry and python-poetry-core installed:

https://github.com/python-poetry/poetry/issues/7482

Downgrading to 1.4.0 works.
Comment by Caleb Maclennan (alerque) - Tuesday, 28 February 2023, 07:51 GMT
Sorry I missed this issue. The poetry-core did sit in testing for quite a while and nobody caught this and I got a couple pings asking why it wasn't moved along yet. One of the things I've really struggled with on this package is there are so many permutations to testing and I personally have such limited use cases that it's difficult to know whether or not it's ready to push. Upstream tagging miss-matched versions all the time doesn't help either.

I see poetry itself has a new release today that goes with poetry-core 1.5.1 so I'll build that and probably expedite getting it into [community] to fix this bug rather than backtracking poetry-core.

Loading...