Quantco / Quantco/quant-ranger
Make sandboxed pixi available for other (custom) updaters
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 0
- Avg merge
- 3h 39m
- Merged PRs (30d)
- 6
Description
It would be nice if custom updaters could easily use the sandboxed Pixi as well.
Low prio because with https://github.com/prefix-dev/pixi/issues/6672, the prefix-dev team might address this differently, eliminating the need of sandboxing completely.
Contributor guide
No contributing guide indexed for this repository
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 locating the existing sandboxed Pixi implementation and the entry points used by custom updaters. Read the linked pixi issue for context, then determine how custom updaters can access the sandbox; the work is done when a custom updater can use the sandboxed Pixi through a clear, supported path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100