pkgsrc/databases/py-sqlite2/PLIST, branch cube-native-xorg[no description]https://git.osdyson.ru/mirror/pkgsrc/atom?h=cube-native-xorg2008-09-10T10:47:31ZDon't try to build and install the Python 2.5+ tests on 2.3 and 2.4 to2008-09-10T10:47:31Zjoergjoerg@pkgsrc.org2008-09-10T10:47:31Zurn:sha1:22ca0ff1bf943d1bf614452faca4b8eb781c7e09
unbreak PLIST for those versions. Bump revision.Found a new homepage, and an even newer version, including changelogs:2008-09-06T16:12:44Zwizwiz@pkgsrc.org2008-09-06T16:12:44Zurn:sha1:92208d78bfac5d4111cef86ddd186d3bc14b4486
2.5.0:
- Windows binaries are now cross-built using mingw on Linux
- import various fixes from Python 2.6 version
- Connection has new method iterdump() that allows you to create a script file
that can be used to clone a database
- the docs are now built using Sphinx and were imported from Python 2.6's
sqlite3 module
- Connection.enable_load_extension(enabled) to allow/disallow extension
loading. Allows you to use fulltext search extension, for example ;-)
- Give the remaining C functions used in multiple .c source files the pysqlite_
prefix.
- Release GIL during sqlite3_prepare() calls for better concurrency.
- Automatically download the SQLite amalgamation when building statically.
2.4.1:
- Made unicode strings for the database parameter in connect() work again
- Removed bad defaults from setup.cfg
2.4.0:
- Implemented context managers. pysqlite's connections can now be used as
context managers with Python 2.5 or later:
from __future__ import with_statement
from pysqlite2 import dbapi2 as sqlite
con = sqlite.connect(":memory:")
con.execute("create table person (id integer primary key, firstname varchar unique)")
# Successful, con.commit() is called automatically afterwards
with con:
con.execute("insert into person(firstname) values (?)", ("Joe",))
# con.rollback() is called after the with block finishes with an exception, the
# exception is still raised and must be catched
try:
with con:
con.execute("insert into person(firstname) values (?)", ("Joe",))
except sqlite.IntegrityError:
print "couldn't add Joe twice"
- pysqlite connections can now be created from APSW connections. This enables
users to use APSW functionality in applications using the DB-API from
pysqlite:
from pysqlite2 import dbapi2 as sqlite
import apsw
apsw_con = apsw.Connection(":memory:")
apsw_con.createscalarfunction("times_two", lambda x: 2*x, 1)
# Create pysqlite connection from APSW connection
con = sqlite.connect(apsw_con)
result = con.execute("select times_two(15)").fetchone()[0]
assert result == 30
con.close()
Caveat: This will only work if both pysqlite and APSW are dynamically
linked against the same SQLite shared library. Otherwise you will
experience a segfault.
- Fixed shuffled docstrings for fetchXXX methods.
- Workaround for SQLite 3.5.x versions which apparently return NULL for
"no-operation" statements.
- Disable the test for rollback detection on old SQLite versions. This prevents
test failures on systems that ship outdated SQLite libraries like MacOS X.
- Implemented set_progress_handler for progress callbacks from SQLite. This is
particularly useful to update GUIs during long-running queries. Thanks to
exarkun for the original patch.Update to 2.4.1, changes undocumented.2008-09-06T16:03:09Zwizwiz@pkgsrc.org2008-09-06T16:03:09Zurn:sha1:279a309d61d088d7d83ae6138cdfcc141abb5f11update to 2.3.22007-01-10T10:39:18Zdrochnerdrochner@pkgsrc.org2007-01-10T10:39:18Zurn:sha1:cc51ebe5ad22dec0df74f00b1983edaf4f6d9963
This is a major update (since 2.0.7), involving an API rework
add a bl3 fileimport pysqlite-2.0.7, an (incompatible) redesign of pysqlite2006-03-14T20:17:59Zdrochnerdrochner@pkgsrc.org2006-03-14T20:17:59Zurn:sha1:a35e788c973a8ddfd81169f751ea791ce57a7753