Am Sonntag, den 13.04.2008, 23:31 +0100 schrieb Alan Gauld:
> "Dinesh B Vadhia" <[EMAIL PROTECTED]> wrote
>
> > Your last paragraph is the gist of my note ie. it's the
> > documentation, documentation, documentation.
>
> I agree it can be very variable in quality.
> One of the problems of Open
Alan Gauld wrote:
[snip]
> (*)And of course that's a gamble too because there are
> many badly documented commercial libraries too!
>
How true.
> But at least you can complain to somebody!
Oh yeah? Try complaining to MS! They built a wall to protect themselves
from their customers.
--
"Dinesh B Vadhia" <[EMAIL PROTECTED]> wrote
> Your last paragraph is the gist of my note ie. it's the
> documentation, documentation, documentation.
I agree it can be very variable in quality.
One of the problems of Open Source is that there are more
people who want to write code than there ar
Alan
Your last paragraph is the gist of my note ie. it's the documentation,
documentation, documentation.
In addition to Python, we use Numpy/Scipy/webpy at the server - all of them
Python libraries written in Python and/or C - and have faced no end of problems
with these libraries.
We also u
"Dinesh B Vadhia" <[EMAIL PROTECTED]> wrote
> Why do you say: "Now you didn't mention webpy before,
> that makes a big difference!" ?
Because any time you change the operating environment
different rules apply. That's not a Python thing that's true
of all programming languages. If you operate
Dinesh B Vadhia wrote:
> And, from my
> experience with Python so far it is not of my incompetance (well, not
> most of the time!).
Hmm. You are very much a beginner. Perhaps you will learn not to be so
quick to blame your tools. When you have trouble, you would do well to
ask, "What is it tha
3:30 +0100
From: "Alan Gauld" <[EMAIL PROTECTED]>
Subject: Re: [Tutor] in-memory pysqlite databases
To: tutor@python.org
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; format=flowed; charset="Windows-1252";
reply-type=original
"Dinesh B Vadhia&q
"Dinesh B Vadhia" <[EMAIL PROTECTED]> wrote
> However, a web version using webpy doesn't work
Now you didn't mention webpy before, that makes a big
difference!
> an execution thread is created by pysqlite and
> another thread by webpy and hence webpy is not
> seeing the table.
Almost ce
python.org
Sent: Saturday, April 12, 2008 11:25 AM
Subject: Re: [Tutor] in-memory pysqlite databases
Dinesh B Vadhia wrote:
Say, you have already created a pysqlite database "testDB". In a Python
program, you connect to the database as:
> con = sqlite3.connect("testDB")
"Dinesh B Vadhia" <[EMAIL PROTECTED]> wrote
> Say, you have already created a pysqlite database "testDB".
> In a Python program, you connect to the database as:
> con = sqlite3.connect("testDB")
> cur = con.cursor()
OK so far.
> To use a database in memory (ie. all the 'testDB' tables
> are
Dinesh B Vadhia wrote:
Say, you have already created a pysqlite
database "testDB". In a Python program, you connect to the database as:
> con = sqlite3.connect("testDB")
> cur = con.cursor()
To use a database in memory (ie. all the
'testDB' tables are held in memory)
Say, you have already created a pysqlite database "testDB". In a Python
program, you connect to the database as:
> con = sqlite3.connect("testDB")
> cur = con.cursor()
To use a database in memory (ie. all the 'testDB' tables are held in memory)
the pysqlite documentation says the declaration i
12 matches
Mail list logo
