Tim de Jager
Tim de Jager
Thanks @dhirschfeld good one! I think you might be able to do `pixi exec -s copier -s copier_template_extensions copier`, (haven't tried it 👼, so ymmv) to work around this for...
Yeah I can reproduce for sure, I'll add it to our cycles to be fixed.
Yeah we are in the process of doing a uv upgrade and are making a distinction between the open-source `pep_*` crates and the `uv_pep` crates, now we should be able...
It has been completed indeed!
Just added this to start on into our cycle in two weeks :)
Hey @travishathaway, excellent initial work on the first steps so far. I still feel as @iamthebot said, that it might be better to split up the parts into different `pypi-*`...
The last time I inquired, they said they were not willing to support a stable API and such for now, and focus more on the application itself. This might change...
I do have the say, as one of the authors as `rip` and working a lot on the uv integration in `pixi`. That the uv crates handle everything a lot...
@jacopoabramo I agree. It would make sense to keep this as lean as possible, just reading the `dist-info` folders, which should not be as performance depending like solving or querying...
Note that we are working on a revamped pixi global, so this consideration might need to be taken into account: https://pixi.sh/latest/design_proposals/pixi_global_manifest/ cc @Hofer-Julian @nichmor