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

What happened to .lnk files? #15

Open
msftcangoblowm opened this issue Oct 24, 2024 · 1 comment
Open

What happened to .lnk files? #15

msftcangoblowm opened this issue Oct 24, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@msftcangoblowm
Copy link
Owner

pipenv-unlock is_lock and pipenv-unlock refresh commands have been removed.

Realized

  • dependencies is either unlocked or locked

This does not change. An app never becomes a package. And a package never becomes an app.

  • optional dependencies are all locked

The issue becomes for each optional dependency (.lock file) which venv does it apply to. The .lock file applies to one or more venv, but rarely all.

#14 proposes a strategy to solve this issue

@msftcangoblowm msftcangoblowm added the documentation Improvements or additions to documentation label Oct 24, 2024
@msftcangoblowm
Copy link
Owner Author

4f25fc3 Manifest.in no longer includes .lnk files

The symlink support codebase and unittests can now be considered tech debt.

... to be removed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant