| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
return negative numbers, per the underlying C implementation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
merged into the 2.5 maintenance branch:
- self->statement was not checked while fetching data, which could
lead to crashes if you used the pysqlite API in unusual ways.
Closing the cursor and continuing to fetch data was enough.
- Converters are stored in a converters dictionary. The converter name
is uppercased first. The old upper-casing algorithm was wrong and
was replaced by a simple call to the Python string's upper() method
instead.
-Applied patch by Glyph Lefkowitz that fixes the problem with
subsequent SQLITE_SCHEMA errors.
- Improvement to the row type: rows can now be iterated over and have a keys()
method. This improves compatibility with both tuple and dict a lot.
- A bugfix for the subsecond resolution in timestamps.
- Corrected the way the flags PARSE_DECLTYPES and PARSE_COLNAMES are
checked for. Now they work as documented.
- gcc on Linux sucks. It exports all symbols by default in shared
libraries, so if symbols are not unique it can lead to problems with
symbol lookup. pysqlite used to crash under Apache when mod_cache
was enabled because both modules had the symbol cache_init. I fixed
this by applying the prefix pysqlite_ almost everywhere. Sigh.
|
|
|
|
|
| |
of HANDLE, WPARAM, LPARAM data types. Make parameterless foreign
function calls work.
|
| |
|
| |
|
|
|
|
| |
'void' instead of just a set of empty parentheses.
|
| |
|
|
|
|
| |
(will backport to 2.5)
|
|
|
|
|
| |
to avoid relying on atexit.
Will backport to 2.5.
|
| |
|
| |
|
|
|
|
| |
offsets > 2Gb
|
|
|
|
|
| |
the sock_addr_t storage out of the socket object.
Will backport to 2.5.
|
|
|
|
|
|
|
| |
The contents of ffi_darwin.c must be compiled unless __APPLE__ is
defined and __ppc__ is not.
Will backport.
|
| |
|
|
|
|
|
|
|
|
|
| |
The problem is that _DB_get_type() can't be called without the GIL
because it calls a bunch of PyErr_* APIs when an error occurs.
There were no other cases in this file that it was called without the GIL.
Removing the BEGIN/END THREAD around _DB_get_type() made everything work.
Will backport.
|
|
|
|
|
| |
There should be no functional changes. However, the error msgs are
slightly different. Also verified that the module dict is not NULL on init.
|
|
|
|
|
| |
arguments (even for -1). Fixes the last bit of
#1359365.
|
|
|
|
|
| |
a2b_qp() function, instead leave it in the string as quopri.decode()
does.
|
| |
|
|
|
|
|
|
| |
it's held (even by the current thread).
Will backport.
|
|
|
|
|
|
|
| |
some warnings from Klokwork. They verify the assumptions of the format
of svn version output.
The assert in the thread module helped debug a problem on HP-UX.
|
| |
|
| |
|
|
|
|
| |
Fixes #1545696 and #1566140. Will backport to 2.5.
|
|
|
|
|
| |
ctypes isn't considered as requiring executable stacks.
Will backport to 2.5.
|
|
|
|
| |
decode unicode objects and returns an unicode object when the argument is one.
|
|
|
|
| |
PyArg_ParseTuple.
|
| |
|
|
|
|
|
|
|
|
| |
Check this and raise an error when something else is used - before
this change ctypes would hang or crash when such a callback was
called. This is a partial fix for #1574584.
Will backport to release25-maint.
|
|
|
|
| |
Will backport to 2.5.
|
| |
|
|
|
|
|
| |
arguments with the system default encoding just like the write()
method does, instead of converting it to a raw buffer.
|
| |
|
| |
|
|
|
|
| |
when encoding non-BMP unicode characters. (Submitted by Ray Chason)
|
|
|
|
|
|
|
| |
add 'if (PyErr_Occurred())' checks to various places so that NULL is
returned properly.
2.4 backport candidate.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* unified the way intobject, longobject and mystrtoul handle
values around -sys.maxint-1.
* in general, trying to entierely avoid overflows in any computation
involving signed ints or longs is extremely involved. Fixed a few
simple cases where a compiler might be too clever (but that's all
guesswork).
* more overflow checks against bad data in marshal.c.
* 2.5 specific: fixed a number of places that were still confusing int
and Py_ssize_t. Some of them could potentially have caused
"real-world" breakage.
* list.pop(x): fixing overflow issues on x was messy. I just reverted
to PyArg_ParseTuple("n"), which does the right thing. (An obscure
test was trying to give a Decimal to list.pop()... doesn't make
sense any more IMHO)
* trying to write a few tests...
|
|
|
|
| |
(unsigned long vs. unsigned int).
|
|
|
|
| |
datetime's strftime function.
|
|
|
|
| |
anyone cares.
|
|
|
|
|
|
| |
which breaks negative counts
* added test for negative numbers
will backport to 2.5.1
|
|
|
|
|
|
| |
arguments are transposed. (reported by Louis Zechtzer)
..already committed to release24-maint
..needs committing to release25-maint
|
| |
|
|
|
|
| |
lot of them.)
|
| |
|
|
|
|
|
| |
as first argument, and failed with a 'bad argument to internal function'
error message.
|
|
|
|
|
|
|
| |
and they gave a strange error message from PyArg_ParseTuple:
function takes exactly 2 arguments (3 given).
With tests.
|
|
|
|
|
|
|
|
|
|
|
| |
timeout on the select()
if an input hook has been defined. Patch by Richard Boulton.
This select() code is only executed with readline 2.1, or if
READLINE_CALLBACKS is defined.
Backport candidate for 2.5, 2.4, probably earlier versions too.
|
|
|
|
| |
of os.urandom().
|