| {"task_id": "uv-000", "category": "versions", "prompt": "Sort these versions into PEP 440 order, lowest first: '1.0.0.post1', '1.0.0', '1.0.0rc1', '1.0.0a1', '1.0.0.dev1', '1.0.0b1'. Return one row of the six version strings.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"1.0.0.dev1\", \"1.0.0a1\", \"1.0.0b1\", \"1.0.0rc1\", \"1.0.0\", \"1.0.0.post1\"]]}"}
|
| {"task_id": "uv-001", "category": "versions", "prompt": "Are '1.0', '1.0.0' and '1.0.0.0' equal under PEP 440? Give 1 or 0 for each of the comparisons 1.0 == 1.0.0, 1.0.0 == 1.0.0.0 and 1.0 == 1.0.0.0. Return one row of three values.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[1, 1, 1]]}"}
|
| {"task_id": "uv-002", "category": "versions", "prompt": "PEP 440 epochs. Sort '2.0', '1!1.0' and '1!0.5' lowest first. Return one row of the three version strings.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"2.0\", \"1!0.5\", \"1!1.0\"]]}"}
|
| {"task_id": "uv-003", "category": "versions", "prompt": "Where does a LOCAL version sort? Sort '1.0.0', '1.0.0+local', '1.0.0.post1' and '1.0.0rc1' lowest first. Return one row of the four version strings.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"1.0.0rc1\", \"1.0.0\", \"1.0.0+local\", \"1.0.0.post1\"]]}"}
|
| {"task_id": "uv-004", "category": "versions", "prompt": "Give 1 if the version is a pre-release and 0 if not, for '1.0.0', '1.0.0rc1', '1.0.0.post1', '1.0.0.dev1' and '1.1.0rc1'. Return one row of five values.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[0, 1, 0, 1, 1]]}"}
|
| {"task_id": "uv-005", "category": "versions", "prompt": "Normalise these version strings the way PEP 440 does and give the results: '1.0.0-alpha.1', '1.0.0-rc1', '1.0.0.RELEASE'. If a string cannot be parsed, give the exact word 'invalid' instead. Return one row of three values.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"1.0.0a1\", \"1.0.0rc1\", \"invalid\"]]}"}
|
| {"task_id": "uv-006", "category": "versions", "prompt": "Sort every version of 'epsilon' in the index into PEP 440 order, lowest first, and then give how many of them are pre-releases. Return one row: the version strings followed by the count.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"0.5.0\", \"1.0.0\", \"1.1.0rc1\", 1]]}"}
|
| {"task_id": "uv-007", "category": "specifiers", "prompt": "The compatible-release operator. For the specifier '~=1.4.2', give 1 or 0 for whether it matches '1.4.2', '1.4.9', '1.5.0' and '1.4.1'. Return one row of four values.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[1, 1, 0, 0]]}"}
|
| {"task_id": "uv-008", "category": "specifiers", "prompt": "For the specifier '~=1.4', give 1 or 0 for whether it matches '1.4.0', '1.9.0', '2.0.0' and '1.3.0'. Return one row of four values.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[1, 1, 0, 0]]}"}
|
| {"task_id": "uv-009", "category": "specifiers", "prompt": "Wildcard equality. For '==1.4.*', give 1 or 0 for '1.4.0', '1.4.9', '1.5.0' and '1.40.0'. Return one row of four values.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[1, 1, 0, 0]]}"}
|
| {"task_id": "uv-010", "category": "specifiers", "prompt": "THE PRE-RELEASE ASYMMETRY. Using the specifier '>=1.0' and the candidate list ['0.9', '1.0', '1.1.0rc1', '1.1.0', '2.0.0a1'], give (a) how many candidates the `in` operator accepts, and (b) how many SpecifierSet.filter returns with its default settings. Return one row of the two integers.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[4, 2]]}"}
|
| {"task_id": "uv-011", "category": "specifiers", "prompt": "Continuing the asymmetry: give the versions SpecifierSet('>=1.0').filter returns from ['0.9', '1.0', '1.1.0rc1', '1.1.0', '2.0.0a1'], in the order returned. Then do the same for SpecifierSet('>=1.0rc1'). Return two rows of version strings.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"1.0\", \"1.1.0\"], [\"1.0\", \"1.1.0rc1\", \"1.1.0\", \"2.0.0a1\"]]}"}
|
| {"task_id": "uv-012", "category": "specifiers", "prompt": "For the combined specifier '>=1.0,<2.0,!=1.5.0', give 1 or 0 for '1.0.0', '1.5.0', '1.9.9' and '2.0.0'. Return one row of four values.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[1, 0, 1, 0]]}"}
|
| {"task_id": "uv-013", "category": "specifiers", "prompt": "Which versions of 'beta' in the index satisfy '>=1.0,<1.1'? Give them newest first. Return one row of version strings.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"1.0.1\", \"1.0.0\"]]}"}
|
| {"task_id": "uv-014", "category": "specifiers", "prompt": "Which versions of 'epsilon' in the index satisfy '>=0.5' with pre-releases excluded, and which satisfy '>=1.1.0rc1'? Give each newest first. Return two rows of version strings.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"1.0.0\", \"0.5.0\"], [\"1.1.0rc1\"]]}"}
|
| {"task_id": "uv-015", "category": "markers", "prompt": "Evaluate the PEP 508 marker 'python_version >= \"3.11\"' in each of the environments linux311, win310 and macarm312. Give 1 or 0 for each, in that order. Return one row of three values.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[1, 0, 1]]}"}
|
| {"task_id": "uv-016", "category": "markers", "prompt": "Evaluate 'sys_platform == \"linux\" and platform_machine == \"x86_64\"' in linux311, win310 and macarm312. Return one row of three values.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[1, 0, 0]]}"}
|
| {"task_id": "uv-017", "category": "markers", "prompt": "Evaluate 'sys_platform != \"win32\" or python_version < \"3.11\"' in linux311, win310 and macarm312. Return one row of three values.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[1, 1, 1]]}"}
|
| {"task_id": "uv-018", "category": "markers", "prompt": "python_version is compared as a VERSION, not lexically. For the marker 'python_version >= \"3.9\"', give its value in linux311, win310 and macarm312; then give what a NAIVE LEXICAL string comparison of that environment's python_version against \"3.9\" would give in the same three environments. Return two rows of three values.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[1, 1, 1], [0, 0, 0]]}"}
|
| {"task_id": "uv-019", "category": "markers", "prompt": "How many of the three environments satisfy 'platform_system == \"Darwin\" and platform_machine == \"arm64\"', and which one — give its name, or the exact word 'none'. Return one row [count, name].", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[1, \"macarm312\"]]}"}
|
| {"task_id": "uv-020", "category": "markers", "prompt": "Given the requirement list ['gamma>=0.2', 'delta>=2 ; sys_platform == \"win32\"', 'epsilon>=1 ; python_version >= \"3.12\"'], give the number of requirements that APPLY in linux311, in win310 and in macarm312. Return one row of three values.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[1, 2, 2]]}"}
|
| {"task_id": "uv-021", "category": "resolution", "prompt": "Resolve the single requirement 'alpha' against the fixed index under the stated rules. Return one row per resolved package, [name, version], sorted by name.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"alpha\", \"2.0.0\"], [\"beta\", \"1.1.0\"], [\"delta\", \"2.1.0\"], [\"gamma\", \"0.3.0\"]]}"}
|
| {"task_id": "uv-022", "category": "resolution", "prompt": "Resolve 'alpha<2'. Return one row per resolved package, [name, version], sorted by name.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"alpha\", \"1.2.0\"], [\"beta\", \"1.1.0\"], [\"gamma\", \"0.3.0\"]]}"}
|
| {"task_id": "uv-023", "category": "resolution", "prompt": "Resolve 'alpha==1.0.0'. Return one row per resolved package, [name, version], sorted by name.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"alpha\", \"1.0.0\"], [\"beta\", \"1.0.1\"], [\"gamma\", \"0.3.0\"]]}"}
|
| {"task_id": "uv-024", "category": "resolution", "prompt": "Resolve the two requirements 'alpha' and 'gamma<0.3' together. Return one row per resolved package, [name, version], sorted by name.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"alpha\", \"1.1.0\"], [\"beta\", \"1.0.1\"], [\"gamma\", \"0.2.0\"]]}"}
|
| {"task_id": "uv-025", "category": "resolution", "prompt": "Resolve 'delta>=2' together with 'gamma>=0.3'. This forces a backtrack: delta 2.0.0 requires gamma<0.3. Return one row per resolved package, [name, version], sorted by name.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"delta\", \"2.1.0\"], [\"gamma\", \"0.3.0\"]]}"}
|
| {"task_id": "uv-026", "category": "resolution", "prompt": "Resolve 'epsilon'. Note the pre-release rule. Return one row per resolved package, [name, version], sorted by name.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"epsilon\", \"1.0.0\"], [\"gamma\", \"0.3.0\"]]}"}
|
| {"task_id": "uv-027", "category": "resolution", "prompt": "Give the number of packages in the resolution of 'alpha', of 'alpha<2', and of 'delta>=2'. Return one row of three integers.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[4, 3, 2]]}"}
|
| {"task_id": "uv-028", "category": "resolution", "prompt": "Is the requirement pair 'alpha==1.2.0' and 'gamma<0.3' satisfiable? Give 1 or 0, then the number of packages in the resolution (0 if unsatisfiable). Return one row of two integers.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[0, 0]]}"}
|
| {"task_id": "uv-029", "category": "resolution", "prompt": "Is 'alpha==1.2.0' together with 'gamma==0.1.0' satisfiable? Give 1 or 0, then the number of packages in the resolution (0 if unsatisfiable). Return one row of two integers.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[0, 0]]}"}
|
| {"task_id": "uv-030", "category": "extras", "prompt": "Resolve 'alpha[plus]<2' — alpha with its 'plus' extra. Return one row per resolved package, [name, version], sorted by name.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"alpha\", \"1.2.0\"], [\"beta\", \"1.1.0\"], [\"delta\", \"2.1.0\"], [\"epsilon\", \"1.0.0\"], [\"gamma\", \"0.3.0\"]]}"}
|
| {"task_id": "uv-031", "category": "extras", "prompt": "Resolve 'alpha[plus]==2.0.0'. Return one row per resolved package, [name, version], sorted by name.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"alpha\", \"2.0.0\"], [\"beta\", \"1.1.0\"], [\"delta\", \"2.1.0\"], [\"epsilon\", \"1.0.0\"], [\"gamma\", \"0.3.0\"]]}"}
|
| {"task_id": "uv-032", "category": "extras", "prompt": "How many packages does 'alpha<2' resolve to WITHOUT the plus extra, and how many WITH it? Return one row of two integers.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[3, 5]]}"}
|
| {"task_id": "uv-033", "category": "extras", "prompt": "Resolve 'beta[fast]'. Return one row per resolved package, [name, version], sorted by name.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"beta\", \"1.1.0\"], [\"delta\", \"2.1.0\"], [\"gamma\", \"0.3.0\"]]}"}
|
| {"task_id": "uv-034", "category": "extras", "prompt": "Give the names of every package in the resolution of 'alpha[plus]<2', sorted alphabetically. Return one row of the names.", "api_description": "The tasks use this FIXED package index. There is no network; these are all the\ndistributions that exist.\n\n alpha: 1.0.0, 1.1.0, 1.2.0, 2.0.0\n beta: 0.9.0, 1.0.0, 1.0.1, 1.1.0\n gamma: 0.1.0, 0.2.0, 0.3.0\n delta: 1.0.0, 2.0.0, 2.1.0\n epsilon: 0.5.0, 1.0.0, 1.1.0rc1\n\nRequirements of each distribution:\n\n alpha 1.0.0 -> beta>=0.9,<1.1\n alpha 1.1.0 -> beta>=1.0, gamma>=0.2\n alpha 1.2.0 -> beta>=1.1, gamma>=0.2\n alpha 2.0.0 -> beta>=1.1, delta>=2\n beta 0.9.0 -> (none)\n beta 1.0.0 -> gamma>=0.1\n beta 1.0.1 -> gamma>=0.1\n beta 1.1.0 -> gamma>=0.3\n gamma any -> (none)\n delta 1.0.0 -> (none)\n delta 2.0.0 -> gamma<0.3\n delta 2.1.0 -> gamma>=0.2\n epsilon 0.5.0 -> (none)\n epsilon 1.0.0 -> gamma>=0.2\n epsilon 1.1.0rc1 -> gamma>=0.3\n\nExtras:\n alpha[plus] 1.2.0 -> delta>=1, epsilon>=0.5\n alpha[plus] 2.0.0 -> epsilon>=1\n beta[fast] 1.1.0 -> delta>=2.1\n\nRESOLUTION RULES — these are the rules to apply, and they are the ones uv and pip follow:\n * prefer the HIGHEST version of every package that satisfies all constraints;\n * PRE-RELEASES ARE EXCLUDED unless a constraint on that package explicitly names a\n pre-release. This is the `SpecifierSet.filter` behaviour, not the `in` behaviour — they\n differ, and the difference is the point of two of these tasks;\n * when a choice fails, BACKTRACK on the most recently chosen package;\n * a resolution is a set of (name, version) pairs; report it sorted by package name.\n\nMARKER ENVIRONMENTS, referred to by name:\n linux311 python_version 3.11, sys_platform linux, platform_machine x86_64\n win310 python_version 3.10, sys_platform win32, platform_machine AMD64\n macarm312 python_version 3.12, sys_platform darwin, platform_machine arm64\n\nAvailable imports: packaging.version (Version), packaging.specifiers (SpecifierSet),\npackaging.markers (Marker), itertools. Nothing else is needed and there is no network.\n\nPut the requested values in `result` as a list of rows of plain values. Versions are returned\nas STRINGS exactly as they appear in the index above. A resolution is one row per resolved\npackage, each row [name, version], sorted by name.\n", "expected_output": "{\"rows\": [[\"alpha\", \"beta\", \"delta\", \"epsilon\", \"gamma\"]]}"}
|
|
|
