From: Jose Isaias Cabrera <jicman@outlook.com>
To: Jim Garrison via Cygwin <cygwin@cygwin.com>
Subject: Changing the python sqlite3 version to the latest
Date: Sat, 11 Feb 2023 21:37:08 +0000 [thread overview]
Message-ID: <DB9P251MB006335721B0284B32132E802DEDF9@DB9P251MB0063.EURP251.PROD.OUTLOOK.COM> (raw)
Greetings.
If I install python39 and thus,
$ python
Python 3.9.10 (main, Jan 20 2022, 21:37:52)
[GCC 11.2.0] on cygwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import sqlite3
>>> sqlite3.sqlite_version
'3.34.0'
>>>
The SQlite3 version installed is v3.34.0. Right now, the version available is 3.40.1. What I would like to do is to work with the latest SQLite version. I have 3 Cygwin instances, 2 of them are working ok, another one is not. This is what I have done to get python to use 3.41.0:
- downloaded the latest SQlite check-in from the site
- $ tar -xvf SQLite-44200596.tar.gz
- cd to SQLite-44200596
- $ ./configure --prefix=/usr
- $ make install
These steps above have worked on two PCs, but I don't know what is the difference that make the other two work and not this one. I have started a few instances of Cygwin on the PC that is not working, and I have been trying since last night, and I am humbling myself, and asking for help. So, the request is to get python3 to change the SQLite3 library from 3.34.0 to 3.41.0. Any help would be greatly appreciated. Thanks.
josé
next reply other threads:[~2023-02-11 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 21:37 Jose Isaias Cabrera [this message]
2023-02-13 20:24 ` Jose Isaias Cabrera
2023-02-14 22:58 ` Marco Atzeri
2023-02-15 1:45 ` Jose Isaias Cabrera
2023-02-15 12:43 ` Jose Isaias Cabrera
2023-02-15 15:55 ` Andrey Repin
2023-02-15 18:29 ` Jose Isaias Cabrera
2023-02-16 6:14 ` Andrey Repin
2023-02-16 14:25 ` Jose Isaias Cabrera
2023-02-16 18:40 ` Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DB9P251MB006335721B0284B32132E802DEDF9@DB9P251MB0063.EURP251.PROD.OUTLOOK.COM \
--to=jicman@outlook.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).