You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently pin development requirements in both requirements.in and requirements_ci.in. This is duplicative, and can be avoided by using pip constraints. The solution would involve building one of the requirement.txt files, then using that as a constraint in the other .in file. Then when pip sees black in the second .in file, it will also see the constraint and use that version. Better explanation with example at https://github.com/jazzband/pip-tools#workflow-for-layered-requirements
The text was updated successfully, but these errors were encountered:
We currently pin development requirements in both
requirements.in
andrequirements_ci.in
. This is duplicative, and can be avoided by using pip constraints. The solution would involve building one of the requirement.txt files, then using that as a constraint in the other .in file. Then when pip sees black in the second .in file, it will also see the constraint and use that version. Better explanation with example at https://github.com/jazzband/pip-tools#workflow-for-layered-requirementsThe text was updated successfully, but these errors were encountered: