@JulienPalard: Would you mind to review this PR?

@JulienPalard could you take a look at this?

An alternative is to remove the download sizes. I don't expect that release managers update this page as part of the release process:
https://www.python.org/dev/peps/pep-0101/

An alternative is to remove the download sizes. I don't expect that release managers update this page as part of the release process:
https://www.python.org/dev/peps/pep-0101/

I also think that documentation size isn't that important nowadays, but perhaps there's a rationale we are missing here?

@andresdelfino there are regions here in germany where people only get very slow internet connections. So it makes a difference for them if it is 1 MB or 5 MB. But they might not be python developers...

@davidak thanks for the insight!

@vstinner I'd keep the file sizes. Let me know how do you want to proceed on this one and I'll update the PR.

@vstinner how should I proceed? Should I remove the file sizes or preserve them and fix the typo pointed by Serhiy?

@andresdelfino: Honestly, I'm very confused by this issue. I don't understand why it takes months to fix such trivial issue :-) I skip my turn and let others handle it, sorry :-(

With the commit of @vstinner (see 8c663fd#diff-9c9d6c705ef5234b89019a8310a89d21), we don't need to specify the unit because it's explicitly indicated in the table.

Moreover, the commit removes the ambiguity with the unit.

The best thing to do is removing the complete line with the detailed unit.

I am going to close your PR and will fix the line.

Thank you a lot for your PR and hope to see your next contributions in the future.

PS: Before closing this issue, I have discussed with @JulienPalard about this issue.

@matrixise thanks for the reply :)

The best thing to do is removing the complete line with the detailed unit. I am going to close your PR and will fix the line.

@matrixise: Would you mind to add a link to your fix here?