Ticket Type
馃挕 Feature Request / Improvement
Description
You got a good setup for your dependency management. Setting the ranges to what you test is a really good way to provide a clear workflow for you users. However the upperbounds on some of your dependencies are blocking users that are mixing lots of dependencies together.
In my case I've been blocked by torch being limited. The builds I want to use are for version 2.13. This seems to work when I force it in with custom configuration to avoid your constraints.
My ask is whether you would be open to remove upper limits or use the semver limit. e.g. >=2.x.x,<3 where you do constrain a major version but not every minor version.
Checklist
Additional Info / Workarounds
My workaround is to repackage lerobot with different constraints. Which I would rather not have to do as it's churn whenever you update your dependencies.
I work for https://prefix.dev so my focus is on making package management better, I'd love to help here.
Ticket Type
馃挕 Feature Request / Improvement
Description
You got a good setup for your dependency management. Setting the ranges to what you test is a really good way to provide a clear workflow for you users. However the upperbounds on some of your dependencies are blocking users that are mixing lots of dependencies together.
In my case I've been blocked by
torchbeing limited. The builds I want to use are for version2.13. This seems to work when I force it in with custom configuration to avoid your constraints.My ask is whether you would be open to remove upper limits or use the semver limit. e.g.
>=2.x.x,<3where you do constrain a major version but not every minor version.Checklist
mainbranch.Additional Info / Workarounds
My workaround is to repackage lerobot with different constraints. Which I would rather not have to do as it's churn whenever you update your dependencies.
I work for https://prefix.dev so my focus is on making package management better, I'd love to help here.