sqlparse: add python3 package

[peter-stadler]

Maintainer: Peter Stadler peter.stadler@student.uibk.ac.at
Compile tested: MIPS 74K, Asus RT-N16, master snapshot
Run tested: MIPS 74K, Asus RT-N16, master snapshot, run some tests from the package directory

Description: This is a dependency for django-cors-headers (see my other PR) and in turn for the etesync-server (I will update the corresponding PR later).

[neheb]

Could use https://github.com/openwrt/packages/blob/master/lang/python/pypi.mk

ping @jefferyto

[BKPepe]

While you will take a look at my feedback, you might want to check this example.

[peter-stadler]

Thank you very much :-) I changed it to use pypi.mk fixing the license info and adding a source package, too. I have one question left: Should I add the sqlformat?

[jefferyto]

Perhaps you can add a separate package for sqlformat, then add python3-sqlparse and python3-pkg-resources as dependencies for that package.

[peter-stadler]

I looked into sqlformat: It is using pkg-resources to call the sqlparse/__main__.py script. We can avoid the dependency by installing this script as /usr/bin/sqlformat.

Alternatively, a python3 -m sqlparse would work, too.

[peter-stadler]

(fixed the whitespace error)

[peter-stadler]

(nothing changed)

[jefferyto]

I don't know enough about how Python handles main scripts to say if there are any side effects to using __main__.py directly, so I suppose we can go with it for now.

Would be great if you can squash the two commits.

[peter-stadler]

I did squash the commits.

As I know python -m sqlparse would just call the __main__.py, the entry_point of the pkg-resources would do a bit more, e.g. check the version or so, but I am not sure what are all the side effects ...