It's still a problem, even if it's a problem in the opposite direction than you first thought (Python has a newer sqlite, rather than older). Updating your API fixes the problem now, but you still need to decide how you check for and handle newer, potentially incompatible library versions.
On Mon, Jun 22, 2020 at 1:13 PM Seth G <se...@geographika.co.uk> wrote: > Thanks Ned. > I did double check the docs for sqlite3 after posting and wondering why > the versions were so different. > I guess the clue should have been the sqlite-3 ! > Reading the history of the module I presume sqlite3 has its own module > version number as it was integrated from a separate project. > > Seth >
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/NYFXECAXMGZM73DSB5AF74O5FV4TFXOL/ Code of Conduct: http://python.org/psf/codeofconduct/
