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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

devenv: use poetry instead of requirements.txt #547

Merged
merged 1 commit into from
Apr 23, 2023

Conversation

bobvanderlinden
Copy link
Contributor

Currently requirements.txt is used within devenv's devenv.nix. It is installed in enterShell. This has 2 downsides that I found:

  • Loading devenv shell takes a longer time, because pip install reruns every time the devenv shell is entered.
  • The dependencies that are installed are not locked. The latest version is chosen, which will result in differences in tooling for different people. devenv docs from the past might not be reproducible.

The biggest downside I have seen is that the files are larger in size. I might be biased to using poetry vs pip directly and not seeing more of the downsides 馃槄

Currently requirements.txt is used. It is installed in enterShell. This
has 2 downsides:

- Loading devenv shell takes a longer time, because pip install reruns
every time the devenv shell is entered.
- The dependencies that are installed are not locked. The latest version
is chosen, which will result in differences in tooling for different
people. devenv docs from the past might not be reproducible.

The biggest downside I have seen is that the files are larger in size.
Though I might be biased to using poetry vs pip directly.
@domenkozar domenkozar merged commit dc1c08f into cachix:main Apr 23, 2023
@bobvanderlinden bobvanderlinden deleted the pr-devenv-poetry branch April 24, 2023 05:24
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 this pull request may close these issues.

None yet

3 participants