pdm config lock.format behavior should be consistent both ways

[sigma67]

Feature Description

Not sure if this is a bug or a feature, just wanted to note this small inconsistency.

When I set pdm config lock.format pylock, pdm handles projects with pdm.lock just fine. It will only yield a warning:

WARNING: `lock.format` is set to pylock but pylock.toml is not found, using pdm.lock instead. You can generate pylock with `pdm export -f pylock -o pylock.toml`.

However, the other way around this is not the case. I set pdm config lock.format pdm, pdm will reject/ignore pylock.toml files present in the repository and treat the repository as if it had no lock file at all.

Problem and Solution

PDM should issue the same/respective warning in both cases, and use the lock file that is present gracefully.

Additional Context

No response

Are you willing to contribute to the development of this feature?

• [ ] Yes, I am willing to contribute to the development of this feature.