Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configurable Lock File Location #1038

Closed
Xdynix opened this issue Apr 13, 2022 · 3 comments · Fixed by #1055
Closed

Configurable Lock File Location #1038

Xdynix opened this issue Apr 13, 2022 · 3 comments · Fixed by #1055
Labels
⭐ enhancement Improvements for existing features

Comments

@Xdynix
Copy link

Xdynix commented Apr 13, 2022

Is your feature request related to a problem? Please describe.

I want to keep my project root as clean as possible. So I put all controllable configuration files like pre-commit-config.yaml, .pylintrc, .coveragerc etc into a separate folder. I want to do the same with pdm.lock.

Describe the solution you'd like

The location of pdm.lock can be changed by setting in pyproject.toml, or by command line arguments. Something like:

# pyproject.toml
[tool.pdm]
# ...
lock_file = "config/pdm.lock"

or

pdm install --lock-file "config/pdm.lock"
@Xdynix Xdynix added the ⭐ enhancement Improvements for existing features label Apr 13, 2022
@frostming
Copy link
Collaborator

That might be a good idea worth doing, but it involves many commands:

  • install
  • sync
  • lock
  • add
  • update
  • remove

@akvadrako
Copy link

Does this configuration work when set in pyproject.toml ? To me, it looks like it's ignored.

@Xdynix
Copy link
Author

Xdynix commented Nov 11, 2022

Does this configuration work when set in pyproject.toml ? To me, it looks like it's ignored.

Currently it can only be specified by CLI argument -L/--lockfile or env var PDM_LOCKFILE. Ref

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⭐ enhancement Improvements for existing features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants