Opened 9 years ago
Closed 9 years ago
#5419 closed defect (fixed)
Settle on a local development server for both Python 3 and Python 2
Reported by: | Christopher Allan Webber | Owned by: | |
---|---|---|---|
Priority: | blocker | Milestone: | 0.9.0 |
Component: | programming | Keywords: | |
Cc: | Boris Bobrov, tsyesika | Parent Tickets: |
Description
We need a local development server that works on *both* Python 2 and Python 3. gunicorn is a likely candidate since we kind of used this for Python 3 before.
Paste is not an option at this time of writing and it doesn't make sense for us to have two different strategies... we should unify.
Attachments (1)
Change History (4)
comment:1 by , 9 years ago
by , 9 years ago
Attachment: | 0001-Switch-from-Paste-for-serving-to-Waitress.patch added |
---|
Replace Paste(/Gunicorn) code with Waitress
comment:2 by , 9 years ago
Cc: | added |
---|---|
Status: | new → review |
I switched to Waitress locally using the above, and everything seems to work really nicely! It requires no special changes at all to our documentation, and seems to clean up a lot of conditionals (though I guess gunicorn would too, but that would require a lot more docs changes).
I think a switch to Waitress would result in the lowest barrier to entry for this release. We could still switch to something like gunicorn afterwards if we evaluate it to make sense, but for now this seems to work and is a smooth path forward. How do others feel? And does my patch look sane?
comment:3 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | review → closed |
Breton approved of my match (via IRC) so I merged and pushed it. Woo woo!
Waitress is another likely candidate. One selling point is that WebTest, which we also use, uses Waitress, so that would be one less dependency along the chain, which appeals to me. It also seems to support PasteDeploy a bit more nicely, though that may be me misunderstanding things. :)