Support distribution with different locks (feature)

[RoelantStegmann]

I am wondering if we could create poeblix lock. I have the following use case in mind.

• In the pyproject.toml file, I want to have the packages that I need. I prefer to keep them open ended. Specifying a max version here makes people lazy and stops incremental progress.
• As long as it gives me a single lock pyproject.toml for a working development environment, it is great to work with. When something new is needed, people can run poetry update to move onward.
• When I build a package to be used at a single point, poeblix build --only-lock works great. It pins dependencies from the lock file.
• However, sometimes I want to be much more flexible, but I don't trust just poeblix build: either the oldest dependency formulated in pyproject.toml might no longer work, or a new one might introduce breaking changes. Essentially, I want to be able to create multiple lock files, and use these with a tool like tox.
  poeblix lock python[5] pandas[3] numpy[2]
  • Python[5]: I want to test at most 3 python versions (low, some majors in between, latest)
  • Pandas[3]: I want to test at most 3 pandas versions (low, middle, max)
  • numpy[2]: I want to test at most 2 numpy versions (low, max)
• After this poeblix build uses dependencies within the ranges defined above.

Please let me know if this use case makes sense, and if you would be interested to solve this with poeblix.

[spoorn]

I believe there was some issue in the poetry github related to multiple lock files, but I can't find it now. poeblix is only a plugin built on top of poetry, which only supports a single lock file per project. Unless poetry supports multiple lock files, doing so in poeblix is out of scope for this plugin IMO