Martin v. Löwis wrote:
> Neal Norwitz wrote:
>> # 61 Modules/_sqlite/cursor.c:599 Null pointer may be dereferenced
>>
>> Null pointer 'self->statement' that comes from line 674 may be
>> dereferenced by passing argument 1 to function
>> 'statement_mark_dirty' at line 599.
>
> Looks li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Looks like I don't know C so well after all ...
Apparently at least gcc on Linux exports all symbols by default that are
not static. This creates problems with Python extensions that export
symbols that are also used in other contexts. For example som
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I maintain the sqlite module in the standard library, which makes heavy use
of PyString_* C API. Now I've made it work under Python 3000 insofar as
tests pass, but the new Python string semantics mean I have more work to do
here and make some API choic
[EMAIL PROTECTED] wrote:
> On Nov 25 Gerhard Haering checked in a change to the release25-maint branch:
>
> Author: gerhard.haering
> Date: Sun Nov 25 18:40:35 2007
> New Revision: 59184
>
> Modified:
>python/branches/release25-maint/Modules/_sqlite/statement.c
>py
Hello Barry,
Great job with the releases!
Barry Warsaw wrote:
> On behalf of the Python development team and the Python community, I'm
> happy to announce the second alpha release of Python 2.6, and the
> fourth alpha release of Python 3.0. [...]
In case you don't know already, the website i
As far as I can see, the specification of the dbm interface is the
module docstring in dbm/__init__.py, which reads:
"""
[...]
It has the following interface (key and data are strings):
d[key] = data # store data at key (may override data at
# existing key)
techtonik wrote:
Can somebody remind how to check script compatibility with old Python versions?
I can remember PHP_CompatInfo class for PHP that parses a script or directory to
find out the minimum version and extensions required for them to run,
and I wonder
if there was anything like this for
Calvin Spealman wrote:
On Mon, Nov 3, 2008 at 6:29 AM, Gerhard Häring <[EMAIL PROTECTED]> wrote:
Stefan Behnel wrote:
Michael Foord wrote:
Moving more C extensions to an implementation based on ctypes would be
enormously useful for PyPy, IronPython and Jython, but ctypes is not
Stefan Behnel wrote:
Michael Foord wrote:
Moving more C extensions to an implementation based on ctypes would be
enormously useful for PyPy, IronPython and Jython, but ctypes is not yet
as portable as Python itself which could be an issue (although one worth
resolving).
In the same line, movin
Jeremy Hylton wrote:
> I don't think this message is on-topic for python-dev. There are lots
> of great places to discuss the design of the python web site, but the
> list for developers doesn't seem like a good place for it. Do we need
> a different list for people to gripe^H^H^H^H^H discuss the
Georg Brandl wrote:
> Anthony Baxter wrote:
>
>>This came up before (back in October 2004!) but didn't go anywhere
>>since, AFAICR. Do we want to consider including pysqlite in Python
>>2.5? It's the only DB adaptor that I'd really consider suitable for
>>shipping with the distribution, because
Georg Brandl wrote:
> Gerhard Häring wrote:
>>I'll try to throw in a bit more information that will be necessary for
>>this discussion:
>>
>>pysqlite 2.x is (almost) feature complete now. I've a few more changes
>>sitting in SVN trunk that are waiting
Martin v. Löwis wrote:
> Anthony Baxter wrote:
>
>>This came up before (back in October 2004!) but didn't go anywhere
>>since, AFAICR. Do we want to consider including pysqlite in Python
>>2.5? It's the only DB adaptor that I'd really consider suitable for
>>shipping with the distribution, beca
Neal Norwitz wrote:
> On 3/28/06, Gerhard Häring <[EMAIL PROTECTED]> wrote:
>
>>>Even better, the authors should be willing to keep the version in
>>>Python synchronized with the separate release.
>>
>>In particular, I would then synchronize changes t
Barry Warsaw wrote:
> On Wed, 2006-03-29 at 19:47 +1100, Anthony Baxter wrote:
>
>>My only concern about this is that it wouldn't be possible for other
>>authors to provide 3rd party packages as (for instance) db.mysqldb
>>because of the way package importing works. And I'd prefer
>>'database.sq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Phillip J. Eby wrote:
> At 11:36 AM 3/29/2006 -0800, Guido van Rossum wrote:
>> [...] Perhaps one person in favor and one
>> person against could summarize the argument for me?
>
> Pro:
>
> * SQLite is really nice to have for writing simple applicati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brett Cannon wrote:
> While this is going to require a PEP (which I am willing to write),
> the discussion of adding pysqlite has brought forth some discussion on
> naming and packaging in the stdlub. Perhaps it's time to start
> discussing the Great
M.-A. Lemburg wrote:
> [...]
> Also your statement regarding sqlite3 suggests that sqlite
> itself is not included - why not ?
- SQLite sources are 1.57 MiB uncompressed, we wouldn't want to add that
to the Python sources download size, would we?
- I personally would not want to have the job to "
Fredrik Lundh wrote:
> Anthony Baxter wrote:
>
>
>>>Such a module name is less likely to cause problems.
>>
>>Excellent point. Hm. Maybe we should just go with 'sqlite', instead.
>
>
> except that "sqlite" was the name used by the first pysqlite
> generation:
>
> $ python2.3
>
import sqli
M.-A. Lemburg wrote:
> Will it also work with e.g. sqlite 2.8.15 (ie. sqlite < v3) -
> this is the standard version on SuSE 9.2.
No, SQLite 3 has a completely different API than SQLite 2.x. If you need
a Python module for it, you can use pysqlite 1.0.1.
>>>Also your statement regarding sqlite3 s
Martin v. Löwis wrote:
> Terry Reedy wrote:
>
>>"Gerhard Häring" <[EMAIL PROTECTED]> wrote in message
>>news:[EMAIL PROTECTED]
>>
>>>I proposed to link dynamically on Windows, and ship the Windows
>>>SQLite3.DLL. This has two advantag
Posting here because I don't know a better place:
Federico di Gregorio and me have both faxed PSF contributor agreements
to the PSF for integration of pysqlite into Python 2.5.
-- Gerhard
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.py
Neal Norwitz wrote:
> What are the doc plans for these modules:
> + * ctypes
> + * ElementTree/cElementTree
> + * msilib
> + * pysqlite
pysqlite: I've started on new module docs for the "sqlite3" module in
the Python standard library, based on the text from the existing
pysql
Brett Cannon wrote:
> here is the rough draft of the PEP for packages maintained externally
> from Python itself. There is some missing, though, that I would like
> help filling in.
>
> I don't know who to list as the contact person (i.e., the Python
> developer in charge of the code) for Expat,
Brett Cannon wrote:
> OK, I am going to write the PEP I proposed a week or so ago, listing
> all modules and packages within the stdlib that are maintained
> externally so we have a central place to go for contact info or where
> to report bugs on issues. This should only apply to modules that wan
Thomas Heller wrote:
> [...] I'm now happy with the tool that converts the ctypes tutorial from reST
> to LaTeX,
> I will later (today or tomorrow) commit that into Python SVN.
Did you commit that already? Alternatively, can you send it to me, please?
-- Gerhard
_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I've now moved over all the content from the pysqlite reference manual to
the sqlite3 module docs.
It would be nice if now somebody with more experience with Python
documentation could look over it.
A few things I know could be changed:
- -
Neal Norwitz wrote:
> It's June 9 in most parts of the world. The schedule calls for beta 1
> on June 14. That means there's less than 4 days until the expected
> code freeze. Please don't rush to get everything in at the last
> minute. The buildbots should remain green to keep Anthony happy an
Co-posting to python-dev in the hope of getting help of people verifying
my suspicion ...
Gerhard Häring wrote:
> [...]
> For some reason, they don't seem to have picked up the changed tests of
> the sqlite3 module. At least the error messages look exactly like the
> ones I h
Gerhard Häring wrote:
Co-posting to python-dev in the hope of getting help of people verifying
my suspicion ...
Gerhard Häring wrote:
[...]
For some reason, they don't seem to have picked up the changed tests of
the sqlite3 module. At least the error messages look exactly like the
o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Peters wrote:
> [Gerhard Häring]
>>> ...
>>> Until recently, SQLite was buggy and it was only fixed in
>>>
>>> http://www.sqlite.org/cvstrac/chngview?cn=2981
>>>
>>> that callbacks can th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Anthony Baxter wrote:
> Well, the just-released Ubuntu 06.06 LTS (Long Term Support) ships
> with sqlite 3.2.8. I'd suggest that whatever version ships with
> Python should _at_ _least_ work with this version.
I have no problems continuing to suppo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Heller wrote:
> Martin v. Löwis wrote:
>> Guido van Rossum wrote:
4 of the 6 modules in PEP 360 were added to Python in 2.5, so if you want
to get rid of it, *now* would be the time.
>>> I'm all for it.
>>>
>>> While I am an enthusiast
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://www.python.org/sf/1509584
Please apply if you think it should go in Python 2.5b1, otherwise I'll
commit it after the freeze.
I'd personally postpone it, because it's only cosmetic (but maybe it's
related to the strange sqlite3 regression test
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Peters wrote:
> [Gerhard Häring]
>> ...
>> Also, somebody please add me as Python developer on Sourceforge (I cannot
>> assign items to myself there).
>
> If you still can't, scream at me ;-)
Bwah!!! :
Brett Cannon wrote:
> I have been working on a design doc for restricted execution of Python
> [...]
All the rest of the API made sense to me, but I couldn't understand why
PyXXX_MemoryFree
is needed. How could memory usage possibly fall below 0?
-- Gerhard
_
Brett Cannon wrote:
> On 6/22/06, *Gerhard Häring* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
> wrote:
>
> Brett Cannon wrote:
> > I have been working on a design doc for restricted execution of
> Python
> > [...]
>
> Al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ka-Ping Yee wrote:
> [...]
> (b) If more handholding seems like a good idea, then:
>
> class ExitHatch:
> def __call__(self): sys.exit()
> def __repr__(self): return ''
> __builtins__.exit = __builtins__.qui
38 matches
Mail list logo
