Skip to content

dev requirements: Bring back editable install #2790

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

Merged
merged 1 commit into from
Feb 20, 2025

Conversation

jku
Copy link
Member

@jku jku commented Feb 15, 2025

This partially reverts 4e889e7 and now again installs the current project as editable in requirements/dev.txt:

  • the test suite does work without this
  • but running the examples was now more difficult

so enabling editable install in dev requirements seems like the right compromise.

Fixes #2786

This partially reverts 4e889e7 and now again installs the current
project as editable in requirements/dev.txt:
* the test suite does work without this
* but running the examples is now more difficult

Fixes theupdateframework#2786

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
@jku jku requested a review from a team as a code owner February 15, 2025 10:05
@jku jku merged commit c6b9e37 into theupdateframework:develop Feb 20, 2025
17 checks passed
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.

Path issue in tuf import in examples/client and examples/repository
2 participants