In #207, I made it so that hatch would create a .venv in 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 in optional-dependencies.
Since pip allows you to install "extras" (see here, here, and here), developers can just write something like the following:
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: