Pre built wheel files not used if different for multiple python versions

[enCHineer]

Pre built wheel files not used if different for multiple python versions

[frostming]

I don't understand what you encounter because pdm.lock does record all wheels.

what does it contain on your side?

[enCHineer]

You got me thinking. While doing a minimal example I found that you are right in the default case.
The problem does only occur when doing pdm lock --strategy no_cross_platform

But what I intend to do with no_cross_platform is only limiting the platform and not the python version. I would expect to see all the wheel files of my current platform but with multiple python versions. But I get only a single wheel file.

Or is it intended to lock as well the python version?

[frostming]

Or is it intended to lock as well the python version?

If you know the mechanic of the wheel selection, the platform tags are compared together.

[enCHineer]

But it looks like not only the platform tag is compared.

If I define the python version as >=3.8.*,<3.10.* using --strategy cross_platform I get all the wheel files for the selected version of matplotlib (3.7.4) in the pdm.lock. These include the following for Windows (and many more for the other platforms):

• matplotlib-3.7.4-cp39-cp39-win_amd64.whl
• matplotlib-3.7.4-cp38-cp38-win_amd64.whl

If I change over to pdm lock --strategy no_cross_platform only one wheel file will be included in pdm.lock:

• matplotlib-3.7.4-cp39-cp39-win_amd64.whl

This means not only the platform tag of the wheel file is compared but as well the python-tag. This is not what I would expect. I would still expect to see all wheel files for the available python versions but only one platform.

[frostming]

Platform tags means python+abi+platform

[enCHineer]

When looking at PEP427 this does not sound right. The python-tag is something different and is not part of the platform-tag. All the three last ones together are called "compatibility tags" (PEP425).

But okay. So my enhancement proposal would be to get a possibility to lock to a specific platform (platform-part of the platform-tag?) with multiple python versions. As this is currently not possible.

[frostming]

. So my enhancement proposal would be to get a possibility to lock to a specific platform (platform-part of the platform-tag?) with multiple python versions.

The cross-platform strategy does more than that. Under non-cross-platform tag, the environment markers will be evaluated at lock time to discard unmatching requirements. So it is not easy to strip the python tag out of it.