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

Jump to bottom

Drop requirements.txt file #182

Closed
abravalheri opened this issue Jun 18, 2018 · 2 comments
Closed

Drop requirements.txt file #182

abravalheri opened this issue Jun 18, 2018 · 2 comments
Milestone
v4.0

Comments

@abravalheri
Copy link
Collaborator

As mentioned in #140 , requirements.txt and test-requirements.txt are not exactly support anymore. Should we stop generating this files and instruct the user to just setup.cfg directly?
@FlorianWilhelm
Copy link
Member

Maybe we should in a version 3.1 first add a --no-req-file flag and wait for the complete removal until version 4.0 (due to semantic versioning). Also we need to discuss if we rather advocate the usage of pipenv or something else. Definitely I think we should have the separation of unpinned requirements and pinned requirements as discussed in #140. From my experience it's extremely important for production to have a clean separation for that in order to guarantee reproducibility and at the same time avoid the dependency hell.

@abravalheri abravalheri added this to the v4.0 milestone Jun 18, 2018
@FlorianWilhelm
Copy link
Member

Removed in f880339

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
v4.0
Development

No branches or pull requests
2 participants
@abravalheri @FlorianWilhelm