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.

Sign up for GitHub

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

Jump to bottom

Should we keep the automatic generation of requirements.txt? #1526

Open
fabcor-maxiv opened this issue Jan 15, 2025 · 2 comments
Open

Should we keep the automatic generation of requirements.txt? #1526

fabcor-maxiv opened this issue Jan 15, 2025 · 2 comments

Comments

@fabcor-maxiv
Copy link
Contributor

Should we keep the automatic generation of requirements.txt?

There is a bit of friction around this. For example: #1521. And we are not sure that anyone is actually using the requirements.txt file. So maybe we can get rid of it.
@fabcor-maxiv
Copy link
Contributor Author

We should ask if anyone is using the automatically generated requirements.txt file. In which channel(s) should we ask? At a developers meeting? On the developers mailing list? In the "deployment" working group? All of the above?

@fabcor-maxiv fabcor-maxiv mentioned this issue Jan 15, 2025
Merged
@fabcor-maxiv
Copy link
Contributor Author

This feature was added in #1269 and discussed in #1268.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fabcor-maxiv