Don't force table widths in versions.rst by ferdnyc · Pull Request #1041 · python/devguide
I added these widths for two reasons:
- Make the columns wide enough to fit their content, and prevent it to be split on two lines
Unfortunately, that's the exact thing it's failing to do, but removing the :widths: easily achieves.
- Make the two tables have the same widths and therefore be aligned
If you just want the tables to have the same width, setting the :width: 100% option on both might be better than setting column widths explicitly. Granted, the columns won't align between the two tables, but... I'm not sold on that being important, TBH. It looks fine without it, at least to me:
(That's with :width: 100% set on both tables, but :widths: still removed.)
Admittedly I think I only tested it on Firefox, which might explain different behaviors on Chrome it other browsers.
Or, it could be that it did originally fit, but some values have gotten wider/narrower since then. That "Georg Brandl, Ned Deily (3.3.7+)" string in the unsupported table is an outlier, and it's going to force that one out of whack no matter what, compared to the supported-versions table. I'm not personally convinced that it's really worth trying to struggle against that, but YMMV.
For any table where the data isn't static, fixed column widths will inevitably fall out of alignment with reality unless they're constantly being adjusted to account for every single change in the data. IMHO, that kind of thing gets filed under, "that's the code's problem to solve, not mine!"