New submission from Neal Norwitz [EMAIL PROTECTED]:
test_pickletools fails sporadically on at least two platforms I've seen.
http://www.python.org/dev/buildbot/all/x86%20gentoo%20trunk/builds/4120/step-test/0
Neal Norwitz [EMAIL PROTECTED] added the comment:
Committed revision 66009.
--
assignee: - nnorwitz
resolution: - fixed
status: open - closed
type: - security
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3627
Georg Brandl [EMAIL PROTECTED] added the comment:
PyErr_Format sets the new exception and returns NULL though.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3653
___
Changes by STINNER Victor [EMAIL PROTECTED]:
--
nosy: +haypo
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3653
___
___
Python-bugs-list mailing list
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
The main cause of these leaks is each time PyArg_ParseTuple(s#) is
passed a bytes object.
If FillInfo() increfs the given object, every object should have a
bf_releasebuffer that decrefs it.
___
Python
Changes by Amaury Forgeot d'Arc [EMAIL PROTECTED]:
--
resolution: - duplicate
status: open - closed
superseder: - eval() leaks 1 reference every time
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3656
Changes by Antoine Pitrou [EMAIL PROTECTED]:
--
priority: - normal
type: - behavior
versions: +Python 2.6, Python 3.0
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3654
___
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Le dimanche 24 août 2008 à 09:18 +, Amaury Forgeot d'Arc a écrit :
If FillInfo() increfs the given object, every object should have a
bf_releasebuffer that decrefs it.
There's no need for that, PyBuffer_Release() does the decref.
But
New submission from Skip Montanaro [EMAIL PROTECTED]:
Attached is a patch to fix some pychecker complaints Neal Norwitz
uncovered. All involved tests pass. Submitting patch simply because
we're past beta3.
--
assignee: nnorwitz
components: Library (Lib)
files: pychecker.diff
keywords:
Benjamin Peterson [EMAIL PROTECTED] added the comment:
It doubt many people are inheriting from the classes that are changed to
new-style in the patch, but I thought it was policy that we didn't
change that until 3.0 just in case.
--
nosy: +benjamin.peterson
Changes by Benjamin Peterson [EMAIL PROTECTED]:
Added file: http://bugs.python.org/file11234/use_unraiseable_better.patch
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3653
___
Skip Montanaro [EMAIL PROTECTED] added the comment:
I can see where that might be a problem. If that's the case I suspect
those property attributes should be changed. OTOH, do properties work on
classic classes?
___
Python tracker [EMAIL PROTECTED]
Georg Brandl [EMAIL PROTECTED] added the comment:
Read-only properties on old-style classes seem to work (though I don't
know if that is an implementation accident), insofar it seems harmless
not to apply this patch.
--
nosy: +georg.brandl
___
Python
New submission from Christian Heimes [EMAIL PROTECTED]:
I'm getting the compiler warning:
Modules/_sqlite/statement.c: In function
'pysqlite_statement_bind_parameter':
Modules/_sqlite/statement.c:133: warning: enumeration value
'TYPE_STRING' not handled in switch
I tried to make sense of the
Christian Heimes [EMAIL PROTECTED] added the comment:
No, they don't work correctly. Readonly properties in old style classes
aren't readonly:
class Example:
... @property
... def spam(self):
... return spam
...
example = Example()
example.spam
'spam'
example.spam = egg
Georg Brandl [EMAIL PROTECTED] added the comment:
Ah yes. But still, I'd call that harmless. Assigning to attributes
you're not supposed to assign to is detrimental in many cases.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3658
Christian Heimes [EMAIL PROTECTED] added the comment:
I've fixed both compiler warnings in trunk and py3k branch.
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3642
Benjamin Peterson [EMAIL PROTECTED] added the comment:
This also restores 2.5 compatibility.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3637
___
___
Pascal Bach [EMAIL PROTECTED] added the comment:
I have looked at utf_8.py and I think I know how to implement the
incremental de/encoder. But I don't understand the codecs.register()
function. Do I have to provide stateless, stateful and streamwriter at
the same time?
If I implement
Martin v. Löwis [EMAIL PROTECTED] added the comment:
Since this is marked release blocker, I'll provide a shallow comment:
I don't think it should be a release blocker. It's a bug in the compile
function, and there are various work-arounds (such as saving the bytes
to a temporary file and
Brett Cannon [EMAIL PROTECTED] added the comment:
On Sat, Aug 23, 2008 at 6:00 PM, Benjamin Peterson
[EMAIL PROTECTED] wrote:
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Those changes are great; thanks for the review! Are you happy enough
with it to let me apply?
Yep.
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Ok. Applied in r66013.
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2351
___
Georg Brandl [EMAIL PROTECTED] added the comment:
Fixed in r66014.
--
nosy: +georg.brandl
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3654
___
Brett Cannon [EMAIL PROTECTED] added the comment:
Actually, the tests don't have to change; if issue 3594 gets applied
then that change cascades into this issue and negates the need to change
the tests themselves.
As for treating Latin-1 as a raw encoding, how can that be theoretically
okay if
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
priority: critical - release blocker
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2744
___
___
Changes by Antoine Pitrou [EMAIL PROTECTED]:
--
priority: - normal
versions: +Python 2.7, Python 3.1 -Python 2.5
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3649
___
New submission from Neal Norwitz [EMAIL PROTECTED]:
Even after adding the current patch in http://bugs.python.org/issue3651
there are many reference leaks. This bug can be a placeholder for all
the reference leaks returned from:
./python ./Lib/test/regrtest.py -R 3:2 -uall,-bsddb
The
Martin v. Löwis [EMAIL PROTECTED] added the comment:
As for treating Latin-1 as a raw encoding, how can that be theoretically
okay if the parser assumes UTF-8 and Latin-1 is not a superset of Latin-1?
The parser doesn't assume UTF-8, but ascii+, i.e. it passes all
non-ASCII bytes on to the
New submission from Daniel Diniz [EMAIL PROTECTED]:
The following code causes a segfault for me:
import sys; sys.call_tracing(type,2)
Running on:
Python 3.0b3+ (py3k:66015, Aug 24 2008, 16:21:19)
[GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2
gdb output:
[New Thread
New submission from Daniel Diniz [EMAIL PROTECTED]:
This snippet causes a segfault from fileio_init calling PyMem_Free:
import _fileio; _fileio._FileIO(1,0, 0 )
Found using Fusil
[Switching to Thread -1210070848 (LWP 10184)]
0x0805f5ff in _PyObject_DebugCheckAddress (p=0xb7b2f0e8) at
Changes by Benjamin Peterson [EMAIL PROTECTED]:
--
versions: +Python 2.6
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3662
___
___
Python-bugs-list
Brett Cannon [EMAIL PROTECTED] added the comment:
The test_imp stuff has to do with PyTokenizer_FindEncoding().
imp.find_module() only opens the file, passes the file descriptor to
PyTokenizer_FindEncoding() and then returns a file object with the found
encoding.
Problem is that (as issue 3594
Christian Heimes [EMAIL PROTECTED] added the comment:
The function call fails much earlier in debug builds. sys_call_tracing()
doesn't check the type of the second argument. It must be a tuple
because it's directly passed to the PyObject_Call() API.
Suggestion: Add an explicit type check for
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Not applicable in 2.6:
Traceback (most recent call last):
File stdin, line 1, in module
TypeError: type() takes 1 or 3 arguments
--
nosy: +benjamin.peterson
versions: -Python 2.6
___
Python
Christian Heimes [EMAIL PROTECTED] added the comment:
The FileIO construct segfaults because PyArg_ParseTupleAndKeywords()
sets name to an invalid but non NULL value. PyMem_Free() tries to
deallocate name but fails.
Suggestion: Either appy this patch or change
PyArg_ParseTupleAndKeyword()'s
Changes by Christian Heimes [EMAIL PROTECTED]:
--
priority: - release blocker
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3662
___
___
New submission from Amaury Forgeot d'Arc [EMAIL PROTECTED]:
The following output is very suspect: the total number of references
decreases!
Python 3.0b3+ (py3k, Aug 24 2008, 21:56:40) [MSC v.1500 32 bit (Intel)]
on win32
Type help, copyright, credits or license for more information.
f(1=1)
Changes by Antoine Pitrou [EMAIL PROTECTED]:
--
nosy: +pitrou
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3663
___
___
Python-bugs-list mailing list
New submission from Daniel Diniz [EMAIL PROTECTED]:
This script segfaults:
##
import _pickle
obj = _pickle.Pickler(open(/bin/ls)) #can be open(__file__) for scripts
try: obj.__init__('pouet', 87)
except Exception as err: pass
obj.dump(0)
###
[Switching to Thread -1210775360 (LWP 19096)]
Changes by Benjamin Peterson [EMAIL PROTECTED]:
--
assignee: - alexandre.vassalotti
nosy: +alexandre.vassalotti
priority: - release blocker
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3664
New submission from Georg Brandl [EMAIL PROTECTED]:
Since \u and \U aren't interpolated in raw strings anymore, the re
module should support those escapes in addition to the \x and octal ones
it already does. Attached patch.
--
components: Library (Lib)
files: re_unicode_escapes.diff
New submission from Daniel Diniz [EMAIL PROTECTED]:
The following crashes the interpreter on exit:
import sys, atexit; atexit.register(lambda: 1, 0, 0, (x for x in (1,2)),
0, 0); sys.exit()
Found with Fusil.
--
messages: 71862
nosy: ajaksu2
severity: normal
status: open
title:
Christian Heimes [EMAIL PROTECTED] added the comment:
pickler_write() has no check for self-write_buf == NULL
Suggested patch:
===
--- Modules/_pickle.c (Revision 66010)
+++ Modules/_pickle.c (Arbeitskopie)
@@ -421,6 +421,10 @@
Changes by Christian Heimes [EMAIL PROTECTED]:
--
priority: - release blocker
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3666
___
___
Antoine Pitrou [EMAIL PROTECTED] added the comment:
- Check that it also works for chars 0x (even in UCS2 builds, at
least when the chars are not part of [character range])
- What does happen with e.g. [\U0001-\U00010001] on an UCS build?
--
nosy: +pitrou
Antoine Pitrou [EMAIL PROTECTED] added the comment:
(in the last sentence, I meant UCS2. Sorry)
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3665
___
___
Christian Heimes [EMAIL PROTECTED] added the comment:
I'm getting hundreds of lines
Fatal Python error: PyThreadState_Get: no current thread
The Python process segfaults in call_ll_exitfuncs - atexit_cleanup() -
atexit_clear() - atexit_delete_cb - Py_DECREF(cb-args)
--
nosy:
New submission from Amaury Forgeot d'Arc [EMAIL PROTECTED]:
With python2.6, reloading extension modules does not always leak memory:
Python 2.6b2+ (trunk, Aug 19 2008, 23:45:24) [MSC v.1500 32 bit (Intel)]
on win32
Type help, copyright, credits or license for more information.
import sys
Georg Brandl [EMAIL PROTECTED] added the comment:
These concerns indeed must be handled: On narrow unicode builds, chars
0x must be converted to surrogates. In ranges, they should raise an
error.
Additionally, this should at least raise an error too:
Neal Norwitz [EMAIL PROTECTED] added the comment:
I fixed some problems in r66016. This patch seems like it has other
things which might be useful, so I'll keep it open until it's handled.
--
nosy: +nnorwitz
___
Python tracker [EMAIL PROTECTED]
New submission from Amaury Forgeot d'Arc [EMAIL PROTECTED]:
When PyArg_ParseTuple correctly parses a s* format, but raises an
exception afterwards (for a subsequent parameter), the user code will
not call PyBuffer_Release() and memory will leak.
Seen by regrtest -R:: test_binascii
For example:
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
This new version of the patch modifies getargs.c and use
PyObject_GetBuffer and PyBuffer_Release in place of the raw bf_getbuffer
and bf_releasebuffer.
Also make sure that each GetBuffer is matched with a ReleaseBuffer
(except for s* and
Christian Heimes [EMAIL PROTECTED] added the comment:
I was able to trace the error to its apartment. During the cleanup
gen_del calls PyErr_Fetch() which fails in PyThreadState_GET().
Conclusion:
The atexit cleanup method must be called much earlier.
call_ll_exitfunc() is too late. I suggest a
Travis Oliphant [EMAIL PROTECTED] added the comment:
I'm sorry that I was unavailable for comment during July and August as
it looks like a lot of decisions were made that have changed the
semantics a bit. I'm still trying to figure out why the decisions were
made that were made.
I get the
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
The goto error is not necessary here. Nothing has been allocated at
this point, and return -1 is enough.
Index: Modules/_fileio.c
===
--- Modules/_fileio.c (revision
New submission from Robert Lehmann [EMAIL PROTECTED]:
The `sqlite3` docs are a little unpythonic. When using `str.join` on
`Connection.iterdump`, the example in the docs manually unpacks the
generator using a LC. I propose this'd be improved.
Patch attached. Same applies to the py3k docs, it's
Christian Heimes [EMAIL PROTECTED] added the comment:
You are right. But I'd rather keep the name = NULL assignment or add a
comment. In the future somebody may alter the function and resurrect the
bug accidentally.
___
Python tracker [EMAIL PROTECTED]
Benjamin Peterson [EMAIL PROTECTED] added the comment:
It won't be resurrected for long if we write a test. :)
--
nosy: +benjamin.peterson
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3662
___
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Hi Travis,
Glad you're back!
I'm not convinced that Py_buffer should have grown a link to an object.
I think this is a shortcut solution due to misuse of the protocol that
may have unfortunate consequences.
What consequences are you
Travis Oliphant [EMAIL PROTECTED] added the comment:
I've added comments in the code to document these functions. I have no
opinion where they live except they should probably be available to
extensions modules.
These routines increment an N-length counter representing a position in
an
Changes by Travis Oliphant [EMAIL PROTECTED]:
--
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3046
___
___
Python-bugs-list
Travis Oliphant [EMAIL PROTECTED] added the comment:
It would have been nice to finish the memoryview object for 3.0, but I
ran into time constraints. The pieces that are left can be pushed to 3.1
___
Python tracker [EMAIL PROTECTED]
Changes by Travis Oliphant [EMAIL PROTECTED]:
--
versions: +Python 3.1 -Python 3.0
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2394
___
___
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Great. It would be nice if you could at least do a quick review what has
been committed though.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2394
___
Travis Oliphant [EMAIL PROTECTED] added the comment:
This can be re-targeted to 3.1 as described.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3132
___
___
Neal Norwitz [EMAIL PROTECTED] added the comment:
Another PyBuffer_Release(pin); looks necessary at @@ -805,6 +807,7 @@.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3651
___
Neal Norwitz [EMAIL PROTECTED] added the comment:
In 3.0 the free is necessary, though see http://bugs.python.org/issue3662 .
--
nosy: +nnorwitz
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3304
New submission from Kent Johnson [EMAIL PROTECTED]:
The Reporting Bugs section of the Python 2.6b3 docs
http://docs.python.org/dev/bugs.html
says,
please use either the “Add a comment” or the “Suggest a change” features
of the relevant page in the most recent online documentation at
Benjamin Peterson [EMAIL PROTECTED] added the comment:
I'm not sure how we could implement a warning on import of exceptions
aside from implementing it in the compiler. I suppose 2to3 could just
remove the import...
--
nosy: +benjamin.peterson
___
Martin v. Löwis [EMAIL PROTECTED] added the comment:
I don't think this codec should be named IA-5. IA-5 is specified in
ITU-T Rec. T.50 (International Alphabet No. 5), recently renamed to
International Reference Alphabet, and it does *not* specify that the
characters 0..31 are printable.
New submission from Kent Johnson [EMAIL PROTECTED]:
These are minor corrections to the What's New in Python 2.6[b3] doc.
Note: the PEP references are to the headers in What's New, not the
actual PEPs
- PEP 371: The multiprocessing Package
- apply() or apply_async, adding a single
New submission from Adam Olsen [EMAIL PROTECTED]:
The Unicode FAQ makes it quite clear that any surrogates in UTF-8 or
UTF-32 should be treated as errors. Lone surrogates in UTF-16 should
probably be treated as errors too (but only during encoding/decoding;
unicode objects on UTF-16 builds
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Yeah. The comment system hasn't actually been implemented so I removed
the note about that in r66017.
--
nosy: +benjamin.peterson
resolution: - accepted
status: open - closed
___
Python tracker
Changes by Adam Olsen [EMAIL PROTECTED]:
--
components: +Unicode
type: - behavior
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3672
___
___
Nick Edds [EMAIL PROTECTED] added the comment:
How soon is this needed by? I probably won't have a chance to do it in
the next week, but it shouldn't take that long to make once I get a
chance to work on it.
___
Python tracker [EMAIL PROTECTED]
Changes by Georg Brandl [EMAIL PROTECTED]:
--
assignee: georg.brandl - akuchling
nosy: +akuchling
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3671
___
Neal Norwitz [EMAIL PROTECTED] added the comment:
Daniel, thanks for running the fuzzer! It would be great if you could
keep running it and find any more problems before releasing 2.6 and 3.0.
I agree with Benjamin and Amaury. PyArg_ParseTupleAndKeywords()
shouldn't update the pointer if it
Martin v. Löwis [EMAIL PROTECTED] added the comment:
I think the patch is fairly incomplete. i still stays at uint, so if
numarenas would ever overflow uint, the loop would never reach
numarenas, and all arenas would get discarded.
Likewise, maxarenas still stays at uint, so when numarenas
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
type: crash - behavior
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1375
___
___
Python-bugs-list
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
type: crash - feature request
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2456
___
___
Python-bugs-list
Neal Norwitz [EMAIL PROTECTED] added the comment:
Is this still a problem?
--
nosy: +nnorwitz
type: crash - behavior
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1210
___
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
type: crash - behavior
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1658
___
___
Python-bugs-list
Neal Norwitz [EMAIL PROTECTED] added the comment:
Is this still a problem?
--
nosy: +nnorwitz
type: crash - behavior
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1840
___
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
type: crash - behavior
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2747
___
___
Python-bugs-list
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
type: crash - behavior
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2562
___
___
Python-bugs-list
Georg Brandl [EMAIL PROTECTED] added the comment:
The culprit is Python/pythonrun.c:1245:
tb = tb ? tb : Py_None;
Py_None needs to be INCREF'd in the else case.
--
assignee: - pitrou
nosy: +georg.brandl
___
Python tracker [EMAIL PROTECTED]
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
assignee: - theller
components: +ctypes -Extension Modules
nosy: +theller
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1838
___
Neal Norwitz [EMAIL PROTECTED] added the comment:
The valgrind errors below are possibly related.
Conditional jump or move depends on uninitialised value(s)
PyUnicodeUCS2_EncodeUTF8 (unicodeobject.c:2216)
_PyUnicode_AsString (unicodeobject.c:1417)
save (_pickle.c:930)
Pickler_dump
Neal Norwitz [EMAIL PROTECTED] added the comment:
Also there should be a Misc/NEWS entry added. Also check the doc to see
it needs updating wrt ownership.
--
type: - resource usage
___
Python tracker [EMAIL PROTECTED]
Antoine Pitrou [EMAIL PROTECTED] added the comment:
I don't know the buffer code to know if this is the correct fix.
However, it fixes the problems and that's probably good enough for now.
If you can get someone familiar with the buffer code to review, that
would be great.
I don't know if
Brett Cannon [EMAIL PROTECTED] added the comment:
On Sun, Aug 24, 2008 at 2:51 PM, Benjamin Peterson
[EMAIL PROTECTED] wrote:
Benjamin Peterson [EMAIL PROTECTED] added the comment:
I'm not sure how we could implement a warning on import of exceptions
aside from implementing it in the
Brett Cannon [EMAIL PROTECTED] added the comment:
On Sun, Aug 24, 2008 at 3:00 PM, Nick Edds [EMAIL PROTECTED] wrote:
Nick Edds [EMAIL PROTECTED] added the comment:
How soon is this needed by? I probably won't have a chance to do it in
the next week, but it shouldn't take that long to make
Neal Norwitz [EMAIL PROTECTED] added the comment:
Indeed. The problem was an incorrect conversion of str - unicode,
instead of converting to bytes. On getting the buffer from unicode, it
tried to read data which was uninitialized.
Hmmm, this fix is for 3.0 only, but the problem is happening
Kent Johnson [EMAIL PROTECTED] added the comment:
You should add something like the old About this document footer.
AFAICT there is no information in the new docs about how to report a
problem with the docs.
___
Python tracker [EMAIL PROTECTED]
Benjamin Peterson [EMAIL PROTECTED] added the comment:
I suggest that this option (when it is implemented) can be a configure
switch.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2456
___
New submission from Neal Norwitz [EMAIL PROTECTED]:
The attached patch against 2.6 fixes the memory leaks reported against
the bsddb module. There are still (probably) reference leaks.
Jesus, it would be great if you can look at this before the release.
--
assignee: jcea
components:
New submission from Hirokazu Yamamoto [EMAIL PROTECTED]:
Currently, I get following messege.
E:\PYTHON~1\py3k\Lib\testpy3k regrtest.py test_dbm_ndbm.py
test_dbm_ndbm
test_dbm_ndbm skipped -- No module named _dbm
1 test skipped:
test_dbm_ndbm
1 skip unexpected on win32:
test_dbm_ndbm
I
Martin v. Löwis [EMAIL PROTECTED] added the comment:
In my humble opinion it should be safe to limit the amount of arenas to
UINT_MAX instead of PY_SIZE_MAX. 4,294,967,295 arenas should be more
than sufficient for the next decade or two. Do you concur?
It is certainly reasonable to limit
98 matches
Mail list logo
