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

Exclude the package itself from requirements #204

Open
The-One-Who-Speaks-and-Depicts opened this issue May 18, 2024 · 0 comments
Open

Exclude the package itself from requirements #204

The-One-Who-Speaks-and-Depicts opened this issue May 18, 2024 · 0 comments

Comments

@The-One-Who-Speaks-and-Depicts

Is your feature request related to a problem? Please describe.
I had my package installed within the environment, where I developed my package. I have cross-imports between package modules, so each time I run pigar generate within the project folder, my package appears in the requirements.txt.

Describe the solution you'd like
Something like --exclude-package option for generate function that takes strings of package names, split by space, and excludes them from generated file.

Describe alternatives you've considered
I have tried deleting package from the environment, but then there is a warning of a non-installed package.

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

No branches or pull requests

1 participant