Code

Opened 12 months ago

Closed 12 months ago

Last modified 5 weeks ago

#20766 closed Cleanup/optimization (fixed)

Deprecate fastcgi support

Reported by: timo Owned by: timo
Component: Core (Other) Version: master
Severity: Normal Keywords: fastcgi
Cc: timograham@… Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

from Jacob in django-developers:

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.

Attachments (0)

Change History (7)

comment:1 Changed 12 months ago by timo

  • Cc timograham@… added
  • Has patch set
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

comment:2 Changed 12 months ago by apollo13

Even if we drop FCGI support in Django, the docs should make clear that you can still use it…; eg have a small page describing it like this: http://werkzeug.pocoo.org/docs/deployment/fastcgi/ and offer http://uwsgi-docs.readthedocs.org/en/latest/Options.html#fastcgi-socket as a runfcgi replacement.

Last edited 12 months ago by apollo13 (previous) (diff)

comment:3 Changed 12 months ago by timo

I don't know enough about using FastCGI via uWSGI to write a how-to. If someone else is interested in writing something, I'm happy to review it.

comment:4 Changed 12 months ago by Tim Graham <timograham@…>

  • Resolution set to fixed
  • Status changed from new to closed

In bd0dcc6c89e262780df3c17f18b2462f50b48137:

Fixed #20766 -- Deprecated FastCGI support.

comment:5 Changed 12 months ago by timo

Created a separate ticket for the doc update: #20799

comment:6 Changed 5 weeks ago by Tim Graham <timograham@…>

In 67ce2e74e1aafd3f85f6d64059d204e434e0e5f4:

Added missing deprecation note for fastcgi in 1.7 release notes; refs #20766.

comment:7 Changed 5 weeks ago by Tim Graham <timograham@…>

In a11ed8dcfdce6820012ea219d1bbadb28c67b60d:

[1.7.x] Added missing deprecation note for fastcgi in 1.7 release notes; refs #20766.

Backport of 67ce2e74e1 from master

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.