Looking more into this, we should be splitting our docs by major distribution again. The fact that we require python3.7 now fragments instructions enough that we should be ensuring each distribution has separate docs which full cover what end users need.
In #2920 I've added a section for Fedora Linux, and, given that version 29 and above has Python 3.7 in official repositories, it's very straightforward.
For now, I decided to keep development tools, since it adds a failsafe when one of our dependencies which include C extensions doesn't have a wheel available. For example, this would probably happen if someone installed Fedora on an ARM machine (not as unusual as you might think - RPi 3 and above users looking to take advantage of their 64-bit armv8 CPU would need to look away from Raspbian). From what I gather, @development-tools is the equivalent of build-essential and linux headers on Debian - we install build-essential with all of the debian-based distributions as well.
In case you were wondering, these dependencies have C extensions:
aiohttp (provides wheels on win/mac/linux for x86 and x86-64)
python-Levenshtein (we provide wheels on win/mac/linux for x86, x86-64 and ARM)
PyYAML (only provides wheels on Windows)
uvloop (only gets installed on non-Windows systems, provides wheels on mac/linux for x86 and x86-64)
websockets (provides wheels on win/mac/linux for x86 and x86-64)
yarl (provides wheels on win/linux for x86 and x86-64)
pymongo (mongo extra only, provides wheels on win/mac/linux for x86 and x86-64)
asyncpg (future, postgres extra only, provides wheels on win/mac/linux for x86 and x86-64)
On Raspbian, some of these packages may be available on piwheels, but it's not guaranteed.