Fix a bug with Quick Create not installing workspace dependencies #1054
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
StellaHuang95
added
the
bug
eleanorjboyd
approved these changes
Dec 11, 2025
Member
|
great catch! Thanks! |
Yoyokrazy
approved these changes
Dec 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are two ways user can do
Quick Create.When user goes from
Create Virtual Environment -> Quick Create, the workspace dependencies are installed in the newly created virtual environment.When user goes from
Create Virtual Environment -> venv -> Quick Create, the workspace dependencies are NOT installed in the newly created virtual environment. This is because the packages are not collected in the code flow. This PR adds that step back.