-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(python): Add support for astral UV #7653
Comments
I assigned it to @nikpivkin since he has time now, but @DmitriyLewen, please help him as you have more knowledge regarding lockfile analysis. |
There are several things to do, like dependency tree, etc. @DmitriyLewen Can you make a list for him first? |
@knqyf263 @nikpivkin I added a TODO list to the issue description. |
@DmitriyLewen Thanks! |
The list of direct dependencies and the root package can be retrieved from the lockfile. But, there is a concept of workspaces in uv that we can add support for later, so I implemented the analyzer as |
Was the documentation ever updated to reflect this? It's currently missing from the live site |
Hi @Aweptimum . v59.0 has not been released yet. |
Description
Parse uv.lock to identify dependencies (example).
TODO
uv.lock
contains dependencies for package - so parser should detect[]Package
and[]Dependency
.(check the case when 2 packages with different versions are used (if possible)uv.lock
contains root package (e.g. https://github.com/astral-sh/uv/blob/312eeb8f573d36f6df658f85ecadc52799647bb3/scripts/benchmark/uv.lock#L27). Can we detect that this is root package (e.g. fromsource
field)?uv.lock
file - we can use analyzer interface. If no - we need to use PostAnalyzer and detect root package frompyproject.toml
file.TypeLanguages
)Discussed in #7647
The text was updated successfully, but these errors were encountered: