Use "your requirements" consistently in resolver error messages (#6113)

Follow-up to
#6092 (comment)

Author: zanieb

crates/uv-resolver/src/pubgrub/report.rs

@@ -357,8 +357,8 @@ impl PubGrubReportFormatter<'_> {
             }
         }
         match &**package {
-            PubGrubPackageInner::Root(Some(_)) => Some("the requirements".to_string()),
-            PubGrubPackageInner::Root(None) => Some("the requirements".to_string()),
+            PubGrubPackageInner::Root(Some(_)) => Some("your requirements".to_string()),
+            PubGrubPackageInner::Root(None) => Some("your requirements".to_string()),
             _ => None,
         }
     }

crates/uv/tests/cache_prune.rs

@@ -244,7 +244,7 @@ fn prune_unzipped() -> Result<()> {
           and iniconfig==0.1 network connectivity is disabled, but the metadata wasn't found in the cache, we can conclude that iniconfig<1.0.0 cannot be used.
           And because iniconfig==1.0.0 network connectivity is disabled, but the metadata wasn't found in the cache and iniconfig==1.0.1 network connectivity is disabled, but the metadata wasn't found in the cache, we can conclude that iniconfig<1.1.0 cannot be used.
           And because iniconfig==1.1.0 network connectivity is disabled, but the metadata wasn't found in the cache and iniconfig==1.1.1 network connectivity is disabled, but the metadata wasn't found in the cache, we can conclude that iniconfig<2.0.0 cannot be used.
-          And because iniconfig==2.0.0 network connectivity is disabled, but the metadata wasn't found in the cache and you require iniconfig, we can conclude that the requirements are unsatisfiable.
+          And because iniconfig==2.0.0 network connectivity is disabled, but the metadata wasn't found in the cache and you require iniconfig, we can conclude that your requirements are unsatisfiable.
 
           hint: Pre-releases are available for iniconfig in the requested range (e.g., 0.2.dev0), but pre-releases weren't enabled (try: `--prerelease=allow`)
 

crates/uv/tests/pip_compile.rs

@@ -1132,7 +1132,7 @@ fn compile_python_37() -> Result<()> {
     ----- stderr -----
       × No solution found when resolving dependencies:
       ╰─▶ Because the requested Python version (3.7.0) does not satisfy Python>=3.8 and black==23.10.1 depends on Python>=3.8, we can conclude that black==23.10.1 cannot be used.
-          And because you require black==23.10.1, we can conclude that the requirements are unsatisfiable.
+          And because you require black==23.10.1, we can conclude that your requirements are unsatisfiable.
     "###);
 
     Ok(())
@@ -1759,7 +1759,7 @@ fn conflicting_direct_url_dependency() -> Result<()> {
 
     ----- stderr -----
       × No solution found when resolving dependencies:
-      ╰─▶ Because there is no version of werkzeug==3.0.0 and you require werkzeug==3.0.0, we can conclude that the requirements are unsatisfiable.
+      ╰─▶ Because there is no version of werkzeug==3.0.0 and you require werkzeug==3.0.0, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -1886,7 +1886,7 @@ fn conflicting_transitive_url_dependency() -> Result<()> {
     ----- stderr -----
       × No solution found when resolving dependencies:
       ╰─▶ Because only werkzeug<3.0.0 is available and flask==3.0.0 depends on werkzeug>=3.0.0, we can conclude that flask==3.0.0 cannot be used.
-          And because you require flask==3.0.0, we can conclude that the requirements are unsatisfiable.
+          And because you require flask==3.0.0, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -2237,7 +2237,7 @@ fn requirement_constraint_override_url() -> Result<()> {
 
     ----- stderr -----
       × No solution found when resolving dependencies:
-      ╰─▶ Because there is no version of anyio==3.7.0 and you require anyio==3.7.0, we can conclude that the requirements are unsatisfiable.
+      ╰─▶ Because there is no version of anyio==3.7.0 and you require anyio==3.7.0, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -2459,7 +2459,7 @@ dependencies = ["anyio==3.7.0", "anyio==4.0.0"]
 
     ----- stderr -----
       × No solution found when resolving dependencies:
-      ╰─▶ Because my-project depends on anyio==3.7.0 and anyio==4.0.0, we can conclude that the requirements are unsatisfiable.
+      ╰─▶ Because my-project depends on anyio==3.7.0 and anyio==4.0.0, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -2491,7 +2491,7 @@ dependencies = ["anyio==300.1.4"]
 
     ----- stderr -----
       × No solution found when resolving dependencies:
-      ╰─▶ Because there is no version of anyio==300.1.4 and my-project depends on anyio==300.1.4, we can conclude that the requirements are unsatisfiable.
+      ╰─▶ Because there is no version of anyio==300.1.4 and my-project depends on anyio==300.1.4, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -2938,7 +2938,7 @@ fn compile_yanked_version_indirect() -> Result<()> {
               attrs==21.1.0
               attrs>=21.2.0
           and attrs==21.1.0 was yanked (reason: Installable but not importable on Python 3.4), we can conclude that attrs>20.3.0,<21.2.0 cannot be used.
-          And because you require attrs>20.3.0,<21.2.0, we can conclude that the requirements are unsatisfiable.
+          And because you require attrs>20.3.0,<21.2.0, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -5402,7 +5402,7 @@ fn no_index_requirements_txt() -> Result<()> {
 
     ----- stderr -----
       × No solution found when resolving dependencies:
-      ╰─▶ Because tqdm was not found in the provided package locations and you require tqdm, we can conclude that the requirements are unsatisfiable.
+      ╰─▶ Because tqdm was not found in the provided package locations and you require tqdm, we can conclude that your requirements are unsatisfiable.
 
           hint: Packages were unavailable because index lookups were disabled and no additional package locations were provided (try: `--find-links <uri>`)
     "###
@@ -5511,7 +5511,7 @@ fn offline_registry() -> Result<()> {
 
     ----- stderr -----
       × No solution found when resolving dependencies:
-      ╰─▶ Because black was not found in the cache and you require black==23.10.1, we can conclude that the requirements are unsatisfiable.
+      ╰─▶ Because black was not found in the cache and you require black==23.10.1, we can conclude that your requirements are unsatisfiable.
 
           hint: Packages were unavailable because the network was disabled
     "###
@@ -5642,7 +5642,7 @@ fn offline_find_links() -> Result<()> {
 
     ----- stderr -----
       × No solution found when resolving dependencies:
-      ╰─▶ Because tqdm was not found in the cache and you require tqdm, we can conclude that the requirements are unsatisfiable.
+      ╰─▶ Because tqdm was not found in the cache and you require tqdm, we can conclude that your requirements are unsatisfiable.
 
           hint: Packages were unavailable because the network was disabled
     "###
@@ -5661,7 +5661,7 @@ fn offline_find_links() -> Result<()> {
 
     ----- stderr -----
       × No solution found when resolving dependencies:
-      ╰─▶ Because tqdm was not found in the cache and you require tqdm, we can conclude that the requirements are unsatisfiable.
+      ╰─▶ Because tqdm was not found in the cache and you require tqdm, we can conclude that your requirements are unsatisfiable.
 
           hint: Packages were unavailable because the network was disabled
     "###
@@ -5747,7 +5747,7 @@ fn invalid_metadata_requires_python() -> Result<()> {
 
     ----- stderr -----
       × No solution found when resolving dependencies:
-      ╰─▶ Because validation==2.0.0 has invalid metadata and you require validation==2.0.0, we can conclude that the requirements are unsatisfiable.
+      ╰─▶ Because validation==2.0.0 has invalid metadata and you require validation==2.0.0, we can conclude that your requirements are unsatisfiable.
 
           hint: Metadata for validation==2.0.0 could not be parsed:
             Failed to parse version: Unexpected end of version specifier, expected operator:
@@ -5779,7 +5779,7 @@ fn invalid_metadata_multiple_dist_info() -> Result<()> {
 
     ----- stderr -----
       × No solution found when resolving dependencies:
-      ╰─▶ Because validation==3.0.0 has an invalid package format and you require validation==3.0.0, we can conclude that the requirements are unsatisfiable.
+      ╰─▶ Because validation==3.0.0 has an invalid package format and you require validation==3.0.0, we can conclude that your requirements are unsatisfiable.
 
           hint: The structure of validation==3.0.0 was invalid:
             Multiple .dist-info directories found: validation-2.0.0, validation-3.0.0
@@ -6048,7 +6048,7 @@ fn compile_constraints_incompatible_url() -> Result<()> {
 
     ----- stderr -----
       × No solution found when resolving dependencies:
-      ╰─▶ Because only anyio>=4 is available and you require anyio<4, we can conclude that the requirements are unsatisfiable.
+      ╰─▶ Because only anyio>=4 is available and you require anyio<4, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -6071,7 +6071,7 @@ fn index_url_in_requirements() -> Result<()> {
 
     ----- stderr -----
       × No solution found when resolving dependencies:
-      ╰─▶ Because anyio was not found in the package registry and you require anyio<4, we can conclude that the requirements are unsatisfiable.
+      ╰─▶ Because anyio was not found in the package registry and you require anyio<4, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -8021,7 +8021,7 @@ fn universal_requires_python_incomplete() -> Result<()> {
               uv{python_version >= '3.8'}==0.1.23
               uv{python_version >= '3.8'}==0.1.24
           and the requested Python version (>=3.7) does not satisfy Python>=3.8, we can conclude that all versions of uv{python_version >= '3.8'} are incompatible.
-          And because you require uv{python_version >= '3.8'}, we can conclude that the requirements are unsatisfiable.
+          And because you require uv{python_version >= '3.8'}, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -8368,7 +8368,7 @@ fn compile_constraints_incompatible_version() -> Result<()> {
 
     ----- stderr -----
       × No solution found when resolving dependencies:
-      ╰─▶ Because you require filelock==1.0.0 and filelock==3.8.0, we can conclude that the requirements are unsatisfiable.
+      ╰─▶ Because you require filelock==1.0.0 and filelock==3.8.0, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -8396,7 +8396,7 @@ fn conflicting_url_markers() -> Result<()> {
 
     ----- stderr -----
       × No solution found when resolving dependencies:
-      ╰─▶ Because you require filelock==1.0.0 and filelock==3.8.0, we can conclude that the requirements are unsatisfiable.
+      ╰─▶ Because you require filelock==1.0.0 and filelock==3.8.0, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -8550,7 +8550,7 @@ fn override_with_incompatible_constraint() -> Result<()> {
 
     ----- stderr -----
       × No solution found when resolving dependencies:
-      ╰─▶ Because you require anyio>=3.0.0 and anyio<3.0.0, we can conclude that the requirements are unsatisfiable.
+      ╰─▶ Because you require anyio>=3.0.0 and anyio<3.0.0, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -9078,7 +9078,7 @@ requires-python = "<=3.8"
     ----- stderr -----
       × No solution found when resolving dependencies:
       ╰─▶ Because the current Python version (3.12.[X]) does not satisfy Python<=3.8 and example==0.0.0 depends on Python<=3.8, we can conclude that example==0.0.0 cannot be used.
-          And because only example==0.0.0 is available and you require example, we can conclude that the requirements are unsatisfiable.
+          And because only example==0.0.0 is available and you require example, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -9130,7 +9130,7 @@ requires-python = "<=3.8"
     ----- stderr -----
       × No solution found when resolving dependencies:
       ╰─▶ Because the requested Python version (3.11.0) does not satisfy Python<=3.8 and example==0.0.0 depends on Python<=3.8, we can conclude that example==0.0.0 cannot be used.
-          And because only example==0.0.0 is available and you require example, we can conclude that the requirements are unsatisfiable.
+          And because only example==0.0.0 is available and you require example, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -9358,7 +9358,7 @@ requires-python = "<=3.8"
     ----- stderr -----
       × No solution found when resolving dependencies:
       ╰─▶ Because the current Python version (3.12.[X]) does not satisfy Python<=3.8 and example==0.0.0 depends on Python<=3.8, we can conclude that example==0.0.0 cannot be used.
-          And because only example==0.0.0 is available and you require example, we can conclude that the requirements are unsatisfiable.
+          And because only example==0.0.0 is available and you require example, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -10494,7 +10494,7 @@ requires-python = ">3.8"
       × No solution found when resolving dependencies:
       ╰─▶ Because there is no version of anyio==0.0.0 and lib==0.0.0 depends on anyio==0.0.0, we can conclude that lib==0.0.0 cannot be used.
           And because only lib==0.0.0 is available and example==0.0.0 depends on lib, we can conclude that example==0.0.0 cannot be used.
-          And because only example==0.0.0 is available and you require example, we can conclude that the requirements are unsatisfiable.
+          And because only example==0.0.0 is available and you require example, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -10665,7 +10665,7 @@ fn compile_index_url_first_match() -> Result<()> {
 
     ----- stderr -----
       × No solution found when resolving dependencies:
-      ╰─▶ Because there is no version of jinja2==3.1.0 and you require jinja2==3.1.0, we can conclude that the requirements are unsatisfiable.
+      ╰─▶ Because there is no version of jinja2==3.1.0 and you require jinja2==3.1.0, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -11693,7 +11693,7 @@ fn no_binary_only_binary() -> Result<()> {
     ----- stderr -----
       × No solution found when resolving dependencies:
       ╰─▶ Because only source-distribution==0.0.1 is available and source-distribution==0.0.1 has no usable wheels and building from source is disabled, we can conclude that all versions of source-distribution cannot be used.
-          And because you require source-distribution, we can conclude that the requirements are unsatisfiable.
+          And because you require source-distribution, we can conclude that your requirements are unsatisfiable.
     "###
     );
 
@@ -11778,7 +11778,7 @@ fn incompatible_build_constraint() -> Result<()> {
     error: Failed to download and build `requests==1.2.0`
       Caused by: Failed to install requirements from setup.py build (resolve)
       Caused by: No solution found when resolving: setuptools>=40.8.0
-      Caused by: Because you require setuptools>=40.8.0 and setuptools==1, we can conclude that the requirements are unsatisfiable.
+      Caused by: Because you require setuptools>=40.8.0 and setuptools==1, we can conclude that your requirements are unsatisfiable.
     "###
     );
 

crates/uv/tests/pip_compile_scenarios.rs

@@ -128,7 +128,7 @@ fn compatible_python_incompatible_override() -> Result<()> {
                  warning: The requested Python version 3.9 is not available; 3.11.[X] will be used to build dependencies instead.
                    × No solution found when resolving dependencies:
                    ╰─▶ Because the requested Python version (3.9.0) does not satisfy Python>=3.10 and package-a==1.0.0 depends on Python>=3.10, we can conclude that package-a==1.0.0 cannot be used.
-                       And because you require package-a==1.0.0, we can conclude that the requirements are unsatisfiable.
+                       And because you require package-a==1.0.0, we can conclude that your requirements are unsatisfiable.
                  "###
     );
 
@@ -182,7 +182,7 @@ fn incompatible_python_compatible_override_unavailable_no_wheels() -> Result<()>
                  warning: The requested Python version 3.11 is not available; 3.9.[X] will be used to build dependencies instead.
                    × No solution found when resolving dependencies:
                    ╰─▶ Because the current Python version (3.9.[X]) does not satisfy Python>=3.10 and package-a==1.0.0 depends on Python>=3.10, we can conclude that package-a==1.0.0 cannot be used.
-                       And because you require package-a==1.0.0, we can conclude that the requirements are unsatisfiable.
+                       And because you require package-a==1.0.0, we can conclude that your requirements are unsatisfiable.
                  "###
     );
 
@@ -294,7 +294,7 @@ fn incompatible_python_compatible_override_no_compatible_wheels() -> Result<()>
                  warning: The requested Python version 3.11 is not available; 3.9.[X] will be used to build dependencies instead.
                    × No solution found when resolving dependencies:
                    ╰─▶ Because the current Python version (3.9.[X]) does not satisfy Python>=3.10 and package-a==1.0.0 depends on Python>=3.10, we can conclude that package-a==1.0.0 cannot be used.
-                       And because you require package-a==1.0.0, we can conclude that the requirements are unsatisfiable.
+                       And because you require package-a==1.0.0, we can conclude that your requirements are unsatisfiable.
                  "###
     );
 
@@ -359,7 +359,7 @@ fn incompatible_python_compatible_override_other_wheel() -> Result<()> {
 
                        Because the requested Python version (3.11.0) does not satisfy Python>=3.12 and package-a==2.0.0 depends on Python>=3.12, we can conclude that package-a==2.0.0 cannot be used.
                        And because we know from (1) that package-a<2.0.0 cannot be used, we can conclude that all versions of package-a cannot be used.
-                       And because you require package-a, we can conclude that the requirements are unsatisfiable.
+                       And because you require package-a, we can conclude that your requirements are unsatisfiable.
                  "###
     );
 
@@ -407,7 +407,7 @@ fn python_patch_override_no_patch() -> Result<()> {
                  ----- stderr -----
                    × No solution found when resolving dependencies:
                    ╰─▶ Because the requested Python version (3.8.0) does not satisfy Python>=3.8.4 and package-a==1.0.0 depends on Python>=3.8.4, we can conclude that package-a==1.0.0 cannot be used.
-                       And because you require package-a==1.0.0, we can conclude that the requirements are unsatisfiable.
+                       And because you require package-a==1.0.0, we can conclude that your requirements are unsatisfiable.
                  "###
     );