From 442fc27dd2a129188f910eaabaae43bb1b971a2c Mon Sep 17 00:00:00 2001 From: Barry Warsaw Date: Wed, 2 Oct 2024 11:37:01 -0700 Subject: [PATCH] Update peps/pep-0759.rst Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> --- peps/pep-0759.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/peps/pep-0759.rst b/peps/pep-0759.rst index f269d17b53e..163c6b8006b 100644 --- a/peps/pep-0759.rst +++ b/peps/pep-0759.rst @@ -133,7 +133,7 @@ dependency confusion attacks. There is another class of problem that a safe external wheel hosting solution can mitigate: artifact size limits. PyPI imposes a `default artifact size limit `__ of -100MiB and a default overall `project size limit +100 MiB and a default overall `project size limit `__ of 10 GiB. Most packages and artifacts can easily fit in these limits, even for packages containing binary extension modules for a variety of platforms. A small, but important class of packages routinely exceed these