Brian S. Stephan 27d4d16572 go back to using the "or any later version" clause of GPLv3 ... I think arguments that "Such new versions will be similar in spirit to the present version", in my own reading and readings such as in https://www.draketo.de/software/gpl-or-later, convince me for now that it is acceptable to allow the "or later" for compatibility and future problem's sake Signed-off-by: Brian S. Stephan <bss@incorporeal.org>		2025-03-21 08:22:49 -05:00
..
mdx	go back to using the "or any later version" clause of GPLv3	2025-03-21 08:22:49 -05:00
static	go back to using the "or any later version" clause of GPLv3	2025-03-21 08:22:49 -05:00
templates	go back to using the "or any later version" clause of GPLv3	2025-03-21 08:22:49 -05:00
__init__.py	go back to using the "or any later version" clause of GPLv3	2025-03-21 08:22:49 -05:00
config.py	go back to using the "or any later version" clause of GPLv3	2025-03-21 08:22:49 -05:00
error_pages.py	go back to using the "or any later version" clause of GPLv3	2025-03-21 08:22:49 -05:00
feed.py	go back to using the "or any later version" clause of GPLv3	2025-03-21 08:22:49 -05:00
markdown.py	go back to using the "or any later version" clause of GPLv3	2025-03-21 08:22:49 -05:00
ssg.py	go back to using the "or any later version" clause of GPLv3	2025-03-21 08:22:49 -05:00