Switch uv-venv to uv project env in example-basic

Open
#14 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
python
Domain
build-system, tooling

Research direction

Start by locating the example-basic configuration that currently uses uv-venv and identify how the project environment is defined. Compare the current setup with the requested uv project environment, including how utility packages and inputs are represented. Done means the example uses the new environment approach without losing required inputs.

Written by the indexing model from the issue text.

Description

This way users could have their own package of various utilities. On the other hand, that does make it easier to forget inputs.

Dominant language
Python
Stars
0
Forks
1
Avg merge
4h 57m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from calkit/example-basic

All issues in calkit/example-basic

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.