| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
(Contributed by Andrew Gaul.)
Fixes a minor leak.
|
| |
|
|
|
|
| |
Avoid Armin Rigo's dastardly exercise in re-entrancy.
|
|
|
|
| |
database environments to use shared memory on systems supporting it.
|
| |
|
| |
|
| |
|
|
|
|
| |
docs
|
|
|
|
|
| |
the tp_name is not correct, but what's exposed to users is known visibly as
"StringIO", not "StringI" or "StringO".
|
| |
|
| |
|
|
|
|
| |
which can now take zero arguments.
|
| |
|
|
|
|
| |
Will also check in on the 2.3 branch.
|
|
|
|
|
|
|
|
| |
Fixed leak caused by switching from PyList_GetItem to PySequence_GetItem.
Added missing NULL check.
Clarified code by converting an "if" to an "else if".
Will backport to 2.3.
|
| |
|
|
|
|
|
| |
Trivial patch, and the alternative is to guess at the right values
based on platform...
|
|
|
|
|
| |
Our saved locale was not being freed. Also check correct variable for
NULL.
|
|
|
|
|
|
|
|
|
| |
arbitrary bytes before the actual zip compatible archive. Zipfiles
containing comments at the end of the file are still not supported.
Add a testcase to test_zipimport, and update NEWS.
This closes sf #775637 and sf #669036.
|
| |
|
|
|
|
|
| |
This patch was provided by Jeremy Kloth, and corresponds to pyexpat.c
1.77 in the PyXML CVS.
|
|
|
|
|
|
| |
New Plan (releases to be made off the head, ongoing random 2.4 stuff
to be done on a short-lived branch, provided anyone is motivated enough
to create one).
|
|
|
|
|
|
| |
I don't think the fix here is very good, but I'm not sure what would
be better. In particular, we should not be defining _SGIAPI, but lots
of things break if we remove it.
|
|
|
|
|
|
| |
PyOS_InputHook and PyOS_ReadlineFunctionPointer).
The inaccuracies were causing problems in framework builds on Mac OS X.
|
| |
|
| |
|
|
|
|
| |
file, not a character or block device.
|
|
|
|
| |
(Contributed by Andrew I MacIntyre.)
|
| |
|
|
|
|
|
| |
Use Py_AtExit instead of atexit so we are called during Py_Finalize()
rather than during DLL teardown.
|
|
|
|
|
|
|
|
|
|
|
| |
* Extended DB & DBEnv set_get_returns_none functionality to take a
"level" instead of a boolean flag. The boolean 0 and 1 values still
have the same effect. A value of 2 extends the "return None instead
of raising an exception" behaviour to the DBCursor set methods.
This will become the default behaviour in pybsddb 4.2.
* Fixed a typo in DBCursor.join_item method that made it crash instead
of returning a value. Obviously nobody uses it. Wrote a test case
for join and join_item.
|
| |
|
|
|
|
|
| |
return a tuple. (this also implies that nobody uses this method; the
bug has been here for a long time)
|
| |
|
|
|
|
| |
Flesh out docs to better explain time.strptime (closes bug #697990).
|
|
|
|
| |
Also fix a memory leak.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
after running the script so that a program could do something like:
os.environ['PYTHONINSPECT'] = 1
to programmatically enter a prompt at the end.
(After a patch by Skip Montanaro w/ proposal by Troy Melhase
|
|
|
|
|
|
|
|
|
| |
(Contributed by Bob Halley)
Added a new exception, socket.timeout so that timeouts can be differentiated
from other socket exceptions.
Docs, more tests, and newsitem to follow.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the callback raised an exception but did not set curexc_traceback,
the trace function was called with PyTrace_RETURN. That is, the trace
function was called with an exception set. The main loop detected the
exception when the trace function returned; it complained and disabled
tracing.
Fix the logic error so that PyTrace_RETURN only occurs if the callback
returned normally.
The trace function must be called for exceptions, too. So we had
to add new functionality to call with PyTrace_EXCEPTION. (Leads to a
rather ugly ifdef / else block that contains only a '}'.)
Reverse the logic and name of NOFIX_TRACE to FIX_TRACE.
Joint work with Fred.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The interning of short strings violates the refcnt==1 assumption for
_PyString_Resize().
A simple fix is to boost the initial value of "totalnew" by 1.
Combined with an NULL argument to PyString_FromStringAndSize(),
this assures that resulting format string is not interned.
This will remain true even if the implementation of
PyString_FromStringAndSize() changes because only the uninitialized
strings that can be interned are those of zero length.
Added a test case.
|
|
|
|
| |
due to a corrupted end pointer.
|
|
|
|
|
|
| |
* Updated comment on design of imap()
* Added untraversed object in izip() structure
* Replaced the pairwise() example with a more general window() example
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
SF bug [ 751276 ] cPickle doesn't raise error, pickle does (recursiondepth)
Most of the calls to PyErr_Clear() were intended to catch & clear an
attribute error and try something different. Guard all those cases
with a PyErr_ExceptionMatches() and fail if some other error
occurred. The other error is likely a bug in the user code.
This is basically the C equivalent of changing "except:" to
"except AttributeError:"
|
| |
|
|
|
|
| |
follow-up to #621891.
|
| |
|
| |
|