Tim de Jager
Tim de Jager
I'm wondering about this statement: > If an environment has additional exclusions beyond its solve-group, those exclusions and their dependency trees are removed post-resolution, and not written to the lock...
Is `IDESupport` really needed in the initial version. Maybe you can also make a mock-up how you would use this API :)? Like what the user should type.
Couple of questions for @baszalmstra and @hunger: * @baszalmstra This PR removes the `from_str` because of the relative directory requirements, any way around that you think? * I like that...
@baszalmstra any Idea why that gatekeeper is failing I tried to re-run it a bunch of times.
@baszalmstra isn't it integrated here? https://github.com/prefix-dev/pixi/pull/4788
We are going to merge this in with the other lock-file break, we'll close this branch after, don't be suprised!
There has been some talk in the python packaging space along these lines, where the lock-file would still need to be rendered into a suitable format. Could be food for...
Like discussed in the discord. I'm also curious what we can do if we deduplicate some of the common prefixes.
> Not off the top of my head -- I definitely acknowledge it's a hard problem, so I was at least somewhat relieved to find that it still compressed reasonably...
Not really, we should investigate we have some test to check for minimal lock file updates for PyPI as well. But not sure if that works with `pixi update`