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

Also classify .in as valid requirements file #52

Open
mering opened this issue Jun 14, 2024 · 0 comments · May be fixed by #59
Open

Also classify .in as valid requirements file #52

mering opened this issue Jun 14, 2024 · 0 comments · May be fixed by #59

Comments

@mering
Copy link

mering commented Jun 14, 2024

The .in extension is often used when using pip-compile to "compile" the .in to .txt. It should be treated as valid in

extension_ok = filename.endswith('txt') or filename.endswith('pip')

Currently there is no way to tell pip-upgrader to work on such files.

Furthermore, I don't understand why you are checking file extensions at all in the case one is explicitly specifying a file via command line argument.

@mering mering linked a pull request Oct 4, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant