Support `create` in Environment Manager
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 2
- Avg merge
- 13h 11m
- Merged PRs (30d)
- 3
Description
In my opinion, create should go through the flow of adding hatch config to pyproject.toml or hatch.toml.
In a case where there is no config, see venv when no .venv is found in the current workspace. It goes through the flow of creating venv in two ways: Quick Create (opinionated way), and custom (user configured way). Hatch could add default config as QuickCreate, and custom config as part of create.
The actual environment creation is handled on get anyway.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Environment Manager's existing get flow and compare it with the venv behavior when no .venv exists in the workspace. Define how create should handle Quick Create versus custom configuration in pyproject.toml or hatch.toml, with environment creation remaining handled by get.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100