search

astral-sh / packse

Python packaging scenarios
Apache License 2.0
93 stars 9 forks source link

Add failing incomplete markers scenarios #200

Closed konstin closed 1 month ago

konstin commented 1 month ago

We're currently (https://github.com/astral-sh/uv/issues/4732) failing to install c from the added scenario:

$ echo "fork-incomplete-markers-8137fed5" | uv pip compile --index-url http://127.0.0.1:3141 -p 3.9 --universal -
Resolved 4 packages in 38ms
# This file was autogenerated by uv via the following command:
#    uv pip compile -p 3.9 --universal -
fork-incomplete-markers-8137fed5==0.0.0
fork-incomplete-markers-a-8137fed5==1.0.0 ; python_version < '3.10'
    # via fork-incomplete-markers-8137fed5
fork-incomplete-markers-a-8137fed5==2.0.0 ; python_version >= '3.11'
    # via fork-incomplete-markers-8137fed5
fork-incomplete-markers-b-8137fed5==1.0.0
    # via fork-incomplete-markers-8137fed5

This is one particular scenario that we need to test for solving https://github.com/astral-sh/uv/issues/4732

I had to update the lockfile for the recent uv lockfile changes, split out to #199 which removes it from the diff here.