| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
foreign function argtypes sequence as long as they provide a
from_param method, no longer is it required that the object is a
ctypes type.
|
|
|
|
|
|
| |
Add a new function uses_seh() to the _ctypes extension module. This
will return True if Windows Structured Exception handling (SEH) is
used when calling functions, False otherwise.
|
|
|
|
|
| |
- change the pyexpat wrapper to not be so sensitive to this detail of the
Expat implementation (the ex-crasher test still passes)
|
|
|
|
| |
containing bitfields may have different layout on MSVC and MingW .
|
|
|
|
|
|
|
|
| |
of bugs in that port. The most annoying ones were due to some subtle differences
between the document ABI and the actual implementation :-(
(there are no python unittests that fail without this patch, but without it
some of libffi's unittests fail).
|
|
|
|
| |
to test for the C compiler version when determining if we have the secure CRT from microsoft. Must test with an undocumented macro, __STDC_SECURE_LIB__ too.
|
|
|
|
|
|
|
|
|
|
|
|
| |
will return True if Windows Structured Exception handling (SEH) is
used when calling functions, False otherwise.
Currently, only MSVC supports SEH.
Fix the test so that it doesn't crash when run with MingW compiled
_ctypes. Note that two tests are still failing when mingw is used, I
suspect structure layout differences and function calling conventions
between MSVC and MingW.
|
|
|
|
|
|
|
| |
It seems that the definition of '__attribute__(x)' was responsible for
the compiler ignoring the '__fastcall' attribute on the
ffi_closure_SYSV function in libffi_msvc/ffi.c, took me quite some
time to figure this out.
|
| |
|
| |
|
|
|
|
| |
character before sending it to a custom converter. This has been fixed now.
|
|
|
|
|
|
|
|
| |
handler would cause a segfault. This merges in Expat's lib/xmlparse.c
revisions 1.154 and 1.155, which fix this and a closely related problem
(the later does not affect Python).
Moved the crasher test to the tests for xml.parsers.expat.
|
| |
|
| |
|
| |
|
|
|
|
| |
#ifdef WITH_THREADS/#endif blocks. Found by Sam Rushing.
|
|
|
|
|
|
| |
a KeyboardInterrupt since PyTuple_Pack was passed a NULL.
Will backport.
|
|
|
|
| |
(http://python.org/sf/1295808)
|
| |
|
|
|
|
|
|
| |
reference API in pysqlite 2.2.1.
Bumbed pysqlite version number to upcoming pysqlite 2.3.1 release.
|
|
|
|
|
| |
is_term_resized, resize_term and resizeterm. This uses three
separate configure checks (one for each function).
|
| |
|
|
|
|
|
|
|
|
|
| |
This backs out the test changes in 46962 which prevented crashes
by not running the tests via a version check. All the version checks
added in that rev were removed from the tests.
Code was added to the error handler in connection.c that seems
to work with older versions of sqlite including 3.1.3.
|
|
|
|
|
|
|
|
|
|
|
| |
SQLite versions.
- Added version checks in test suite so that we don't execute tests that we
know will fail with older (buggy) SQLite versions.
Now, all tests should run against all SQLite versions from 3.0.8 until 3.3.6
(latest one now). The sqlite3 module can be built against all these SQLite
versions and the sqlite3 module does its best to not trigger bugs in SQLite,
but using SQLite 3.3.3 or later is recommended.
|
| |
|
|
|
|
| |
follow in a few hours at the latest. Then we should be ready for beta1.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Heavily revised, comprising revisions:
46640 - original trunk revision (backed out in r46655)
46647 - markup fix (backed out in r46655)
46692:46918 merged from branch aimacintyre-sf1454481
branch tested on buildbots (Windows buildbots had problems
not related to these changes).
|
| |
|
|
|
|
|
|
| |
CRT error handler and disable the assertion for debug builds. This causes CRT to set errno to EINVAL.
This update fixes crash cases in the test suite where the default CRT error handler would cause process exit.
|
|
|
|
| |
the -c switch
|
|
|
|
| |
duplicated. Thanks to Simon Percivall for the heads up.
|
| |
|
|
|
|
|
| |
copy is only in newer versions of zlib. This should allow zlibmodule
to work with older versions like the Tru64 buildbot.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Python coded COM objects.
|
|
|
|
|
| |
Top/Bottom factor out some common expressions
Add a XXX comment about widing offset.
|
|
|
|
|
| |
We know it's not NULL from the ParseTuple and DbObject_Check will verify
it's not NULL.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Summary of changes:
- support for 'variable sized' data
- support for anonymous structure/union fields
- fix severe bug with certain arrays or structures containing more than 256 fields
|
|
|
|
|
|
| |
- update header checks, using autoconf
- provide dummies for getenv, environ, and GetVersion
- adjust MSC_VER check in socketmodule.c
|
|
|
|
| |
Make the definition #ARRAYSIZE conditional. VisualStudio .NET 2005 already has it defined using a better gimmick.
|
|
|
|
|
|
|
|
|
| |
the char buffer was requested. Now it actually returns the char buffer if
available or raises a TypeError if it isn't (as is raised for the other buffer
types if they are not present but requested).
Not a backport candidate since it does change semantics of the buffer object
(although it could be argued this is enough of a bug to bother backporting).
|
|
|
|
| |
match its documentation stating it accepts any read-only buffer.
|