I added another commit where I achieve what I was saying here: #7983 (comment)

This:

• Requires no release of pypa/installer
• Makes the installation process faster, as we compute file hashes just once
• Does not lose any validation capabilities. They are just handled a bit later

Cons: some pypa/installer code spilling into the Poetry codebase

Not sure if the second commit is worth it or if we should just turn off validation until there is a solution in installer (or we really need validation for some reason). For a patch release I'd probably go with the first commit only (and include the second commit in the next minor if we want to include it).

First commit is a temporary solution to #7983 until pypa/installer#183 gets released.

The installer PR only reduces the memory consumption, the hash will still be computed twice, won't it?

Correct, we would still need either a more invasive change of installer or this second commit

@radoering yes, I agree the PR still needs some touches. The way I got it is that we wouldn't have merged the additional work on top of the simple validate_contents=False, am I right?

Yes, I think for 1.5.1 the first commit is fine. The second commit needs more work and testing. You can split the second commit into a separate PR if you want to keep working on it.

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.