pdm install won't install local development package about pdm HOT 3 CLOSED

Well, I'm going to verify the case if Python 3.6 might be the bad guy.
It's just a behavior to install setuptools and wheel as part of the dev dependencies.

from pdm.

It looks like requires-python = ">=3.6" is preventing the build system to use recent version of setuptools and wheel. Upgrading it to requires-python = ">=3.7" seems to fix the issue. Your build requirements actually require Python >= 3.8, so I'd recommend using that.

This behavior was explained by the numerous warnings printed to the console:

PackageWarning: Skipping [email protected] because it requires Python>=3.8 but the project claims to work with Python>=3.6. Instead, another 
version of setuptools that supports Python>=3.6 will be used.
If you want to install [email protected], narrow down the `requires-python` range to include this version. For example, ">=3.8" should work.
...
PackageWarning: Skipping [email protected] because it requires Python>=3.7 but the project claims to work with Python>=3.6. Instead, another version
of wheel that supports Python>=3.6 will be used.
If you want to install [email protected], narrow down the `requires-python` range to include this version. For example, ">=3.7" should work.
...

(but maybe you had the quiet option turned on)

Or maybe something clashes between your build requirements and your optional dependencies. Why do you list setuptools and wheel in a dev optional group? This would only be useful if you wanted to build your package in non-isolated mode.

from pdm.

@pawamoy is right, the bad file name is generated by the backend setuptools, which installs a problematic version on Python 3.6. Not a bug of PDM. I am closing it now.

from pdm.