Make it more clear that the file doesn't need to be deleted (#17546)

pypi · Feb 3, 2025 · fa5ff03 · fa5ff03
1 parent 61d5516
commit fa5ff03
Show file tree

Hide file tree

Showing 6 changed files with 6 additions and 6 deletions.
diff --git a/warehouse/templates/email/pep625-extension-email/body.html b/warehouse/templates/email/pep625-extension-email/body.html
@@ -34,7 +34,7 @@
   <p>
     In most cases, this can be resolved by upgrading the version of your build
     tooling to a later version that supports PEP 625 and produces compliant
-    filenames.
+    filenames. You do not need to remove the file.
   </p>
   <p>
     If you have questions, you can email

diff --git a/warehouse/templates/email/pep625-extension-email/body.txt b/warehouse/templates/email/pep625-extension-email/body.txt
@@ -21,7 +21,7 @@ In the future, PyPI will require all newly uploaded source distribution filename
 
 Specifically, your recent upload of '{{ filename }}' is incompatible with PEP 625 because it uses the .zip extension.
 
-In most cases, this can be resolved by upgrading the version of your build tooling to a later version that supports PEP 625 and produces compliant filenames.
+In most cases, this can be resolved by upgrading the version of your build tooling to a later version that supports PEP 625 and produces compliant filenames. You do not need to remove the file.
 
 If you have questions, you can email admin@pypi.org to communicate with the PyPI administrators.
 

diff --git a/warehouse/templates/email/pep625-name-email/body.html b/warehouse/templates/email/pep625-name-email/body.html
@@ -35,7 +35,7 @@
   <p>
     In most cases, this can be resolved by upgrading the version of your build
     tooling to a later version that supports PEP 625 and produces compliant
-    filenames.
+    filenames. You do not need to remove the file.
   </p>
   <p>
     If you have questions, you can email

diff --git a/warehouse/templates/email/pep625-name-email/body.txt b/warehouse/templates/email/pep625-name-email/body.txt
@@ -21,7 +21,7 @@ In the future, PyPI will require all newly uploaded source distribution filename
 
 Specifically, your recent upload of '{{ filename }}' is incompatible with PEP 625 because it does not contain the normalized project name '{{ normalized_name }}'.
 
-In most cases, this can be resolved by upgrading the version of your build tooling to a later version that supports PEP 625 and produces compliant filenames.
+In most cases, this can be resolved by upgrading the version of your build tooling to a later version that supports PEP 625 and produces compliant filenames. You do not need to remove the file.
 
 If you have questions, you can email admin@pypi.org to communicate with the PyPI administrators.
 

diff --git a/warehouse/templates/email/pep625-version-email/body.html b/warehouse/templates/email/pep625-version-email/body.html
@@ -35,7 +35,7 @@
   <p>
     In most cases, this can be resolved by upgrading the version of your build
     tooling to a later version that supports PEP 625 and produces compliant
-    filenames.
+    filenames. You do not need to remove the file.
   </p>
   <p>
     If you have questions, you can email

diff --git a/warehouse/templates/email/pep625-version-email/body.txt b/warehouse/templates/email/pep625-version-email/body.txt
@@ -21,7 +21,7 @@ In the future, PyPI will require all newly uploaded source distribution filename
 
 Specifically, your recent upload of '{{ filename }}' is incompatible with PEP 625 because it does not contain contain the normalized project version '{{ normalized_version }}'.
 
-In most cases, this can be resolved by upgrading the version of your build tooling to a later version that supports PEP 625 and produces compliant filenames.
+In most cases, this can be resolved by upgrading the version of your build tooling to a later version that supports PEP 625 and produces compliant filenames. You do not need to remove the file.
 
 If you have questions, you can email admin@pypi.org to communicate with the PyPI administrators.