Description

This, for me, is the key: anything that's not a WSGI container is basically the wrong way to serve Django. Full stop. By continuing to include these other weird protocols we're implying that they're fully supported when they're actually totally not. Back in the day, we needed FCGI support because the options for hosting Python stuff was super limited. Today, there are a ton of options, even in the ultra-low-cost category.

Let's start FCGI (and the others) down the path to deprecation. If there's truly a community that finds value in these things -- and frankly I think that once they try modern options they'll quickly switch and never look back -- then let them maintain the code.