daniel
4ae0352ca7
update py-sqlparse to 0.5.4
2025-12-02 11:36:42 +00:00
sthen
93ef55c0db
remove MODPY_COMMENT from PLISTs, no longer needed (expands to nothing, so bumps not required)
2025-10-23 13:19:02 +00:00
sthen
ec91832428
garbage-collect old @conflict entries; many were never needed, some are
...
no longer needed since 6.9 was dropped from quirks. (experience has shown
that having these around when not needed causes some confusion when using
another port as a template for a new one; not least by me ;)
2025-10-20 19:22:54 +00:00
sthen
680b8b8d5c
update to py3-sqlparse-0.5.3
2025-01-11 12:43:39 +00:00
sthen
e5a598879f
handle py3.12 switchover in databases
2024-12-21 11:37:48 +00:00
sthen
ca7aa64559
update to py3-sqlparse-0.5.0
2024-04-14 11:18:54 +00:00
sthen
6377e68c6c
update to py3-sqlparse-0.4.4
2023-05-19 10:28:09 +00:00
sthen
9ee5e83502
update to py3-sqlparse-0.4.3
2022-10-03 22:11:24 +00:00
naddy
7a958849ed
drop RCS Ids
2022-03-11 18:31:17 +00:00
sthen
9c21fd051e
update py-sqlparse to 0.4.1, dropping py2 support.
...
disable py2 for py-sqlalchemy-migrate.
updated from a diff from wen heping.
2020-11-13 22:41:14 +00:00
sthen
142f53539a
de-conflict
2017-04-07 21:55:11 +00:00
espie
4ada1dde64
if py and py3 conflict so be it.
2017-04-06 10:21:30 +00:00
danj
7e963f398c
Update to py-sqlparse-0.2.2 and add a py3 flavor
2016-12-02 21:42:19 +00:00
landry
0eebb07761
Import py-sqlparse 0.2.1.
...
sqlparse is a non-validating SQL parser module for Python.
Needed by an upcoming py-sqlachemy-migrate update.
ok edd@
2016-09-02 08:52:33 +00:00