Python 2.5 and sqlite

[Steve Holden]

Re: Python 2.5 and sqlite

timotoole@gmail .com wrote:

On Nov 12, 10:14 am, Thorsten Kampe <thors...@thors tenkampe.dewrot e:

>* timoto...@gmail .com (Wed, 12 Nov 2008 01:27:01 -0800 (PST))
>>

>>Python (2.5.1) was compiled from source on the webserver that I use,
>>without an associated sqlite present on the machine, so trying "import
>>sqlite3" in a python application gives an error, but aside from that
>>python is mostly behaving itself. Again further clarification, the
>>webserver is a sun machine, my machine is linux and all drives of all
>>machine in the network are mounted, so a ssh,telnet,rlog in is not
>>required to gain access to other machines.
>>Now with that out of the way, I'm still not clear if I can install a
>>copy of sqlite on my local machine and get that to work with python on
>>the webserver? Possibly via pysqlite?

>No, if Python was compiled without SQLite support or pysqlite is not
>installed on that machine it will not run anything SQLite related.
>>
>Thorsten

>
>
ok, thanks for the clarification Thorsten. would it be the same
situation trying to get another db such as MySQL or PostgreSQL working?

No, as those database are supported by modules you have to load separately.

Seems like the easiest answer to your problem would be to install SQLite
and then rebuild the Python interpreter.

regards
Steve
--
Steve Holden +1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/

[david.lyon@preisshare.net]

Re: Python 2.5 and sqlite


Thorsten,

Quoting Thorsten Kampe <thorsten@thors tenkampe.de>:

* (Tue, 11 Nov 2008 17:58:15 -0500)

Can you ask them if sqlite3 is installed? and if not... to install
it?
>
Why would he have to install SQLite?!

>>
>Seems a stupid question. If he wants to use SQLite... it needs to be
>on the system....

>
No.

really...?

Python cannot check whether SQLite is installed or not.

Of course it can....

It checks
whether it can find the SQLite header files. So the SQLite source (or
the binary) is only needed for compiling Python. If you build SQLite
support as a shared library, you need the libsqlite package (not the
SQLite binary itself) at runtime. If you build it static, you don't need
SQLite at all at runtime. See Martin's answer in the same thread.

Anyway.. I think you just want to argue endlessly with silly
statements.. you're being too pedantic..

Fact is different *nux distributions come with different parts
(static/dynamic-libraries, header files etc). There is no blanket
solution that will work on every platform every time.

I know many *nix distro's work with python out of the box.. but we are
not talking about that..

Anyway.. I have work to do

Take care

David

[Thorsten Kampe]

Re: Python 2.5 and sqlite

* (Wed, 12 Nov 2008 17:52:55 -0500)

Quoting Thorsten Kampe <thorsten@thors tenkampe.de>:

* (Tue, 11 Nov 2008 17:58:15 -0500)
It checks whether it can find the SQLite header files. So the SQLite
source (or the binary) is only needed for compiling Python. If you
build SQLite support as a shared library, you need the libsqlite
package (not the SQLite binary itself) at runtime. If you build it
static, you don't need SQLite at all at runtime. See Martin's answer
in the same thread.

>
Anyway.. I think you just want to argue endlessly with silly
statements.. you're being too pedantic..

If you think making a distinction between the SQLite package and the
libsqlite package is pedantic - I don't have a problem with that. Fact
is that none of the packages are required for using sqlite3 with Python
- they are only required when you want to compile Python yourself or
when Python uses the shared library.

And even if you want to compile Python yourself, SQLite doesn't have to
be _installed_. You simply can dump the files wherever you like and
point Python to it. This is often necessary on a machine where you
cannot install anything to the default locations because you don't have
admin rights.

Thorsten

[david.lyon@preisshare.net]

Re: Python 2.5 and sqlite

Quoting Thorsten Kampe <thorsten@thors tenkampe.de>:

And even if you want to compile Python yourself, SQLite doesn't have to
be _installed_. You simply can dump the files wherever you like and
point Python to it. This is often necessary on a machine where you
cannot install anything to the default locations because you don't have
admin rights.

Oh.. ok now I understand what you were trying to say.

That is fair enough.

Take care

David

[=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=]

Re: Python 2.5 and sqlite

If you think making a distinction between the SQLite package and the

libsqlite package is pedantic - I don't have a problem with that.

I think that is not only pedantic - it is also inaccurate. There is
no SQLite package, nor is there a libsqlite package, in the bigger+
world. From

http://www.sqlite.org/download.html

I can download the following pieces:

sqlite3-x.y.z.bin.gz (for Linux, likewise for OSX and Windows)
tclsqlite3* (Tcl bindings - clearly irrelevant here)
sqlite-x.y.z.so.gz (for Linux, likewise for Windows)
sqlite3_analyze r-x.y.z (also clearly irrelevant here)
sqlite-amalgation-x.y.z (amalgated sources)
sqlite-x.y.z (complete sources, in tar.gz and .zip)

So there is no SQLite download, nor is there a libsqlite download.

I don't know what specific packages you are talking about - probably
about the way your Linux distribution choses to package things.

Fact
is that none of the packages are required for using sqlite3 with Python
- they are only required when you want to compile Python yourself or
when Python uses the shared library.

So the shared library *is* required (as that is the typical way in which
SQLite is built)

And even if you want to compile Python yourself, SQLite doesn't have to
be _installed_. You simply can dump the files wherever you like and
point Python to it. This is often necessary on a machine where you
cannot install anything to the default locations because you don't have
admin rights.

And that is nit-picking. You don't have to do the "make install" step,
but I would suggest to do that, anyway, even on a machine where
you don't have admin rights. You just pass --prefix to the configure
of the amalgamated sources. This puts sqlite nicely into bin, include,
and lib directories, so that Python's setup.py can find it easier.

Regards,
Martin

[Thorsten Kampe]

Re: Python 2.5 and sqlite

* "Martin v. Löwis" (Thu, 13 Nov 2008 20:58:35 +0100)

If you think making a distinction between the SQLite package and the
libsqlite package is pedantic - I don't have a problem with that.

>
I think that is not only pedantic - it is also inaccurate. There is
no SQLite package, nor is there a libsqlite package, in the bigger+
world.
[..]
So there is no SQLite download, nor is there a libsqlite download.
>
I don't know what specific packages you are talking about - probably
about the way your Linux distribution choses to package things.

Some Distributions (for example SUSE) have a package called libsqlite
[1].

Fact is that none of the packages are required for using sqlite3
with Python - they are only required when you want to compile Python
yourself or when Python uses the shared library.

>
So the shared library *is* required (as that is the typical way in
which SQLite is built)

,--- * [2]
| That's not what I meant: the question is, do you need SQLite /after/
| you've built from source or if you install the Python binary.
|
| Depends on how you built SQLite on your system. If it was a static
| library, you won't need it - if it is a shared library, you certainly
| need the shared library at run-time.
`---

And even if you want to compile Python yourself, SQLite doesn't have
to be _installed_. You simply can dump the files wherever you like
and point Python to it. This is often necessary on a machine where
you cannot install anything to the default locations because you
don't have admin rights.

>
And that is nit-picking.

No, it's not. That was my advice for people here who wanted to build
Python with SQLite support but claimed not having rights to install it.
Obviously...

You don't have to do the "make install" step, but I would suggest to
do that, anyway, even on a machine where you don't have admin rights.
You just pass --prefix to the configure of the amalgamated sources.
This puts sqlite nicely into bin, include, and lib directories, so
that Python's setup.py can find it easier.

....this advice is even much better (but I didn't think of it).

Thorsten
[1] http://software.opensuse.org/search?q=libsqlite
[2] http://groups.google.com/group/comp....7ec003e4d3ea42