| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Reviewer: Gregory P. Smith
|
|
|
|
|
|
| |
be compatible with Python 3.0, also.
http://www.jcea.es/programacion/pybsddb.htm#bsddb3-4.7.3
|
|
|
|
|
| |
TESTED=./python -E -tt ./Lib/test/regrtest.py test_fileio
R (approach from bug)=Amaury and Benjamin
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* crashes on memory allocation failure found with failmalloc
* memory leaks found with valgrind
* compiler warnings in opt mode which would lead to invalid memory reads
* problem using wrong name in decimal module reported by pychecker
Update the valgrind suppressions file with new leaks that are small/one-time
leaks we don't care about (ie, they are too hard to fix).
TBR=barry
TESTED=./python -E -tt ./Lib/test/regrtest.py -uall (both debug and opt modes)
in opt mode:
valgrind -q --leak-check=yes --suppressions=Misc/valgrind-python.supp \
./python -E -tt ./Lib/test/regrtest.py -uall,-bsddb,-compiler \
-x test_logging test_ssl test_multiprocessing
valgrind -q --leak-check=yes --suppressions=Misc/valgrind-python.supp \
./python -E -tt ./Lib/test/regrtest.py test_multiprocessing
for i in `seq 1 4000` ; do
LD_PRELOAD=~/local/lib/libfailmalloc.so FAILMALLOC_INTERVAL=$i \
./python -c pass
done
At least some of these fixes should probably be backported to 2.5.
|
|
|
|
|
| |
Author: Victor Stinner
Reviewer: Benjamin Peterson
|
| |
|
|
|
|
|
| |
Modules/_collectionsmodule.c:674: warning: format '%i' expects type 'int', but argument 2 has type 'Py_ssize_t'
Reviewed by Benjamin Peterson
|
|
|
|
|
| |
Modules/_sqlite/row.c:187: warning: suggest parentheses around && within ||
Reviewed by Benjamin Peterson
|
| |
|
| |
|
|
|
|
| |
that are COM methods must have a boolean True value.
|
| |
|
|
|
|
|
|
| |
- Fix broken functions
- Add (hopefully) extensive tests
- Modernize a little
|
|
|
|
| |
function now takes bytearray by using 's*' instead of 't#'.
|
|
|
|
| |
fails unicode conversion on 2nd parameter. (windows only)
|
| |
|
|
|
|
|
|
|
| |
by denying s# to parse objects that have a releasebuffer procedure,
and introducing s*.
More module might need to get converted to use s*.
|
|
|
|
| |
from usage under -3.
|
| |
|
|
|
|
| |
Add F_FULLFSYNC if it exists (OS X only so far).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a verifier for the binary code used by the _sre module (this
is often called bytecode, though to distinguish it from Python bytecode
I put it in quotes).
I wrote this for Google App Engine, and am making the patch available as
open source under the Apache 2 license. Below are the copyright
statement and license, for completeness.
# Copyright 2008 Google Inc.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
It's not necessary to include these copyrights and bytecode in the
source file. Google has signed a contributor's agreement with the PSF
already.
|
| |
|
| |
|
| |
|
|
|
|
| |
that were missed by r65308
|
| |
|
|
|
|
|
|
| |
Also minor cleanups to the code: fix tabbing, remove
trailing whitespace, and reformat to fit into 80
columns.
|
| |
|
| |
|
| |
|
|
|
|
| |
and length.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch publishes the work done until now
for Python 3.0 compatibility. Still a lot
to be done.
When possible, we use 3.0 features in Python 2.6,
easing development and testing, and exposing internal
changes to a wider audience, for better test coverage.
Some mode details:
http://www.jcea.es/programacion/pybsddb.htm#bsddb3-4.7.2
|
|
|
|
|
|
|
|
| |
was not always being done properly in some python types and extension
modules. PyMem_MALLOC, PyMem_REALLOC, PyMem_NEW and PyMem_RESIZE have
all been updated to perform better checks and places in the code that
would previously leak memory on the error path when such an allocation
failed have been fixed.
|
|
|
|
|
|
| |
CryptGenRandom.
Since python doesn't provide any particular random data, it seems more reasonable anyway.
|
| |
|
| |
|
|
|
|
| |
be NULL for the C functions.
|
| |
|
| |
|
| |
|
|
|
|
| |
always set a dlerror() message.
|
|
|
|
|
| |
release build) when the format string of a pointer to an incomplete
structure is created.
|
|
|
|
| |
be blocked explicitly so that collections.Hashable remains meaningful
|
|
|
|
|
|
|
|
| |
process rather than both parent and child.
Does anyone actually use fork1()? It appears to be a Solaris thing
but if Python is built with pthreads on Solaris, fork1() and fork()
should be the same.
|
|
|
|
| |
Changed statements of the form Py_DECREF(obj), obj = 0 to Py_CLEAR(obj).
|
|
|
|
| |
sys.getsizeof.
|
| |
|
| |
|
| |
|