Poetry 1.4.0 uninstalls charset-normalizer when resuming install on Windows

[l0b0]

• Poetry version: 1.4.0 only

• Python version: 3.8, 3.9, 3.10 and 3.11

• OS version and name: Microsoft Windows Server 2022 10.0.20348 Datacenter (windows-2022 GitHub runner)

• pyproject.toml: Gist

• I am on the latest stable Poetry version, installed using a recommended method.

• I have searched the issues of this repo and believe that this is not a duplicate.

• I have consulted the FAQ and blog for any relevant entries or release notes.

• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option) and have included the output below. See gist from this PR.

Issue

To work around broken Poetry package installs on Windows I've set up a retrying job which uses the latest version of Poetry. Since the release of Poetry 1.4.0 this broke further, since now repeated package install attempts uninstall the charset-normalizer package, which is required by the request package to continue installation.

Proving that this is a Poetry and not a Conda/Windows/other issue is that reverting to Poetry 1.3.2 fixes the issue.

[dimbleby]

poetry is trying to upgrade charset-normalizer: the process for upgrading a package has always been to remove the old version and then install the new version. You just happen to be hitting #1031 between those two actions.

This is therefore a duplicate of #1031: it will be fixed if/when that is fixed, and cannot be fixed independently of that

[l0b0]

@dimbleby I don't think it's exactly the same as #1031, because that is intermittent while this is 100% reproducible across tens of builds since 1.4.0.

[dimbleby]

plausible that the new installer disturbs the balance as to what files are open at what time so that the frequency or exact realisation of this changes. You could experiment with disabling the new installer.

Still: your logs pretty clearly show that this is a duplicate, in the way that I described in my previous comment.

[dimbleby]

should have been closed long ago as a duplicate, a fix for the thing that it is a duplicate of has now been released too. So this should be closed twice!

[radoering]

Duplicate: #1031

[github-actions]

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