Skip to content

Remove uv and dependencies that are not direct #13

Open
@llucax

Description

@llucax

What's needed?

uv is not really being used, so we shouldn't depend on it (developers that want to use it can install it manually on their envs).

The non-direct dependencies should go, I guess they were added because of uv?. See:

I'm OK to keep the uv and non-direct dependencies experimentally for a while, but we should at least add a comment to the dependency saying why it is there, and the current issues we have with uv. Also if it is not much work it would be nice if it were actually used in the CI, so we can also see more in practice how much faster the CI could be with it.

Proposed solution

No response

Use cases

No response

Alternatives and workarounds

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    part:toolingAffects the development tooling (CI, deployment, dependency management, etc.)type:enhancementNew feature or enhancement visitble to users

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions