So, with 2.18.0, can one turn on lockfiles just for tools? We cannot use lockfiles for the regular code, since we are using parametrised interpreter constrains, but if I don't enable

enable_resolves

, no lockfiles are generated. And if I do that, I can't use

requirement_constraints

.

maybe @happy-kitchen-89482 has insight

I don't think so, this is not a use case we anticipated. Hmm.

But there isn't one, we have a couple of dependencies that aren't compatible. And, are you sure? The lockfile points to a file, and that file (a wheel, generally) will be different between Python versions.

Just to answer the second question: yes, the lockfile includes more than one file for each dependency, so if a dependency publishes wheels for all Python versions required, then the resolve can be locked, and all those files will be included. At runtime/when building a package, and appropriate subset of those will be chosen, based on the actual platform.

Fair enough. Still can't get rid of the different deps for different versions, since there are some packages that don't have versions that don't support both 3.7 and 3.10. Thankfully, we're getting rid of 3.7 in a few weeks, and our next upgrade, to 3.11, will probably not have this issue

Ah yes, 3.7 and 3.10 would be tricky, I was hoping it was more of a 3.9+3.10 situation or something