pyparsing VS uwsgi-nginx-flask-docker

After over a year since the last release of pyparsing, I've bundled up all the bug-fixes and changes, and they are now released as pyparsing 3.1.0. Visit this link for the details.

Look into "parser combinators" for building an interpreter. There's a few ones out there, but PyParsing is one I've seen around that looks pretty nifty.

I havent found a way to specify an exact character match in pyparsing - https://github.com/pyparsing/pyparsing/discussions/443

STDOUT: Lark or pyparsing

Since it is not mentioned in the article: Python users may also want to check out pyparsing [0]. It is slightly different from Parsec/FParsec (for instance, it ignores all whitespace by default), but I think it is a really good project.

[0]: https://github.com/pyparsing/pyparsing/

Here is the page of all the new changes and features in pyparsing 3.0.

Your pyparsing parser might benefit from a tune-up. This page has some performance tips: https://github.com/pyparsing/pyparsing/wiki/Performance-Tips.

If your SQL has fairly complex structure, you will need a full blown SQL parser. If your statements are mostly simple select, you can get pretty close with Pyparsing, here is an example.

I'm using a dockerimage based on https://github.com/tiangolo/uwsgi-nginx-flask-docker/tree/master/python3.6. I am running a python app inside that accepts a POST, does some processing on the json body, and returns a simple json response back. A post like this:

uwsgi-nginx-flask

I use this container for dev and testing purposes (though you could use it for production if it was hosted somewhere reliable). It spins up nice and easy, has everything you need for a functioning Flask web app, and is lightweight.

I have tried to enable threading to run the flask web server and a discord bot. The code runs fine in vscode on 127.0.0.1:5000 but when I git pull into a docker image it still runs on port 5000 and not on port 80.