Use dense formatting for requirement version specifiers in diagnostics (#2601)

For consistency with the output in "no solution" errors
This commit is contained in:
Zanie Blue 2024-03-22 16:35:49 -05:00 committed by GitHub
parent 90a1f89ac4
commit d0cb301d59
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
5 changed files with 26 additions and 26 deletions

View file

@ -243,7 +243,7 @@ impl Display for Requirement {
VersionOrUrl::VersionSpecifier(version_specifier) => {
let version_specifier: Vec<String> =
version_specifier.iter().map(ToString::to_string).collect();
write!(f, " {}", version_specifier.join(", "))?;
write!(f, "{}", version_specifier.join(","))?;
}
VersionOrUrl::Url(url) => {
// We add the space for markers later if necessary
@ -1627,7 +1627,7 @@ mod tests {
#[test]
fn basic_examples() {
let input = r"requests[security,tests] >=2.8.1, ==2.8.* ; python_version < '2.7'";
let input = r"requests[security,tests]>=2.8.1,==2.8.* ; python_version < '2.7'";
let requests = Requirement::from_str(input).unwrap();
assert_eq!(input, requests.to_string());
let expected = Requirement {