I had this codebase building last year, but pip is giving me some sass this time around
Apparently the new pip version resolver gets angry about subtle URL string mismatches
In this case, luna specifies a trailing @main
in some git URLs (yes, really, that's enough to upset pip now)
The conflict is caused by:
The user requested amaranth 0.4.dev5+gc6dc08c (from git+https://github.com/amaranth-lang/amaranth.git)
amaranth-boards 0.1.dev236+g809587c depends on amaranth<=4 and >=0.2
luna 0.1.0.dev0 depends on amaranth 0.4.dev5+gc6dc08c (from git+https://github.com/amaranth-lang/amaranth.git@main)
I consider this a bug in pip, the (temporary and extremely brittle) workaround is to tweak the requirements.txt to match precisely the URLs listed in luna
The following completes pip resolution, but I had to point to the wrong amaranth-boards.git
.
-git+https://github.com/amaranth-lang/amaranth.git
-git+https://github.com/amaranth-community-unofficial/amaranth-boards.git
+git+https://github.com/amaranth-lang/amaranth.git@main
+git+https://github.com/amaranth-lang/amaranth-boards.git@main
git+https://github.com/amaranth-community-unofficial/usb2-highspeed-core.git
-git+https://github.com/amaranth-community-unofficial/amlib.git
+git+https://github.com/amaranth-community-unofficial/amlib@main
Thanks for the link to retroramblings
, that article was useful.
I'll follow this up with a resolution next week when I bully pip into giving me the repos I need.