Skip to content
This repository has been archived by the owner on Jan 5, 2024. It is now read-only.

[securedrop-proxy] Remove pipenv in favor of pip-tools #138

Closed
redshiftzero opened this issue May 15, 2019 · 0 comments · Fixed by #33
Closed

[securedrop-proxy] Remove pipenv in favor of pip-tools #138

redshiftzero opened this issue May 15, 2019 · 0 comments · Fixed by #33
Assignees

Comments

@redshiftzero
Copy link
Contributor

See detailed rationale in original issue on the client side here: freedomofpress/securedrop-client#370

@redshiftzero redshiftzero self-assigned this May 15, 2019
@zenmonkeykstop zenmonkeykstop changed the title Remove pipenv in favor of pip-tools [securedrop-proxy] Remove pipenv in favor of pip-tools Dec 13, 2023
@zenmonkeykstop zenmonkeykstop transferred this issue from freedomofpress/securedrop-proxy Dec 13, 2023
@zenmonkeykstop zenmonkeykstop transferred this issue from freedomofpress/securedrop-client Dec 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant