Make it easier to use purely pip and venv instead of requiring Hatch
#228
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.
In #207, I made it so that hatch would create a
.venvin the repository root. The reason was to make common scenarios work better for editors (most which currently don't understand hatch).Still, lots of people don't use Hatch, and in #215, @pamelafox pointed out that it's nice to have control over this stuff. So this PR makes it possible to use use pip directly with our
pyproject.toml. To do so, dev-time dependencies for TypeChat, along with dependencies for our examples, are moved into their own respective arrays inoptional-dependencies.Since pip allows you to install "extras" (see here, here, and here), developers can just write something like the following: