[issue3602] Move test.test_suport.catch_warning() to the 'warnings' module

Brett Cannon <[EMAIL PROTECTED]> added the comment: New patch is up with a minor change from Benjamin's review. My explicit comments on the suggestions are on Rietveld. ___ Python tracker <[EMAIL PROTECTED]> _

[issue3602] Move test.test_suport.catch_warning() to the 'warnings' module

Changes by Brett Cannon <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file11227/move_catch_warnings.diff ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3566] httplib persistent connections violate MUST in RFC2616 sec 8.1.4.

Changes by Mark Hammond <[EMAIL PROTECTED]>: -- nosy: +mhammond ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing

[issue3602] Move test.test_suport.catch_warning() to the 'warnings' module

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: See my comments on Rietveld. http://codereview.appspot.com/3255 ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3640] test_cpickle crash on AMD64 Windows build

Mark Hammond <[EMAIL PROTECTED]> added the comment: Sorry for the initial noise - your analysis is correct, mine was flawed :) Simple recursion to a depth of 1000 does work fine on a 64bit build. cpickle.patch does make test_cpickle pass for me. FWIW, find_recursionlimit.py now causes a segfau

[issue3602] Move test.test_suport.catch_warning() to the 'warnings' module

Brett Cannon <[EMAIL PROTECTED]> added the comment: The patch does a couple of things. It moves test.test_support.catch_warning() to warnings.catch_warnings() and leaves a stub behind. WarningsRecorder becomes a subclass of list to make it easier to work with. The uses of catch_warnings() in the

[issue3652] Remove DeprecationWarning in _warnings about 'line'

New submission from Brett Cannon <[EMAIL PROTECTED]>: The DeprecationWarning introduced in Python 2.6/3.0 about the 'line' argument for showwarning() can be removed in 2.7/3.1. -- assignee: brett.cannon components: Library (Lib) messages: 71797 nosy: brett.cannon priority: normal severit

[issue3625] test issues on 64bit windows

Mark Hammond <[EMAIL PROTECTED]> added the comment: Thanks. Checked into the trunk in r65986 -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3651] eval() leaks 1 reference every time

Changes by Amaury Forgeot d'Arc <[EMAIL PROTECTED]>: -- assignee: -> loewis nosy: +loewis ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3651] eval() leaks 1 reference every time

Changes by Amaury Forgeot d'Arc <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11224/buffer-leak.patch ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3651] eval() leaks 1 reference every time

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Of course, I forgot PyObject_AsWriteBuffer in my patch. I wonder if turning view.obj into an owned reference was a good idea. There are more calls to bf_getbuffer (in getarg.c), they leak too: test_struct leaked [5, 5, 5, 5] reference

[issue3611] invalid exception context

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: I can't reproduce it either. I suspect that I removed the wrong lines initially and caused other problems. :) Sorry for the false alarm. ___ Python tracker <[EMAIL PROTECTED]>

[issue3611] invalid exception context

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Benjamin, I am testing the patch proposed earlier by Victor in http://bugs.python.org/msg71579 (who might be the correct one, after all), and I don't see the problems you mentioned. I run the test suite without problem, on winXP & Linu

[issue3651] eval() leaks 1 reference every time

Changes by Amaury Forgeot d'Arc <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11223/buffer-leak.patch ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3651] eval() leaks 1 reference every time

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: PyObject_AsCharBuffer is affected as well. This fixes for me the last refleak in test_bytes. Added file: http://bugs.python.org/file11224/buffer-leak.patch ___ Python tracker <[EMAIL PROTECTED]>

[issue3651] eval() leaks 1 reference every time

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: The attached patch corrects the eval() and compile() reference leak. The problem is in PyObject_AsReadBuffer. Needs review: view->obj seems to own the reference, but object.h say the opposite. -- keywords: +needs review, patch

[issue3651] eval() leaks 1 reference every time

Christian Heimes <[EMAIL PROTECTED]> added the comment: I was already up to date. r65985 leaks 195 references in each run on my box. ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3651] eval() leaks 1 reference every time

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Benjamin: yes, test_bytes calls eval() 128 times. Christian: please "svn up", I just corrected another leak in bytesobject.c ___ Python tracker <[EMAIL PROTECTED]> _

[issue3651] eval() leaks 1 reference every time

Christian Heimes <[EMAIL PROTECTED]> added the comment: Good point! It's leaking even more on my 64bit machine: test_bytes leaked [195, 195, 195, 195] references, sum=780 ___ Python tracker <[EMAIL PROTECTED]> __

[issue3651] eval() leaks 1 reference every time

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Could it be related to the fact that test_bytes is leaking? test_bytes leaked [129, 129, 129, 129] references, sum=516 -- nosy: +benjamin.peterson ___ Python tracker <[EMAIL PROTECTED]>

[issue3636] Managing dual 2.x and 3.0 installations on Windows

Changes by Terry J. Reedy <[EMAIL PROTECTED]>: -- nosy: +tjreedy ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing

[issue1396825] subprocess: wait for a period of time

gd2shoe <[EMAIL PROTECTED]> added the comment: This is just common sense. I'm trying to avoid a poll() busy-wait section of code. I'll figure it out, but it would be much, much easier if wait accepted a number of seconds, and returned None if the process was still going (cf. Popen.poll() ). I'

[issue3651] eval() leaks 1 reference every time

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: The leaked reference refers to the bytes object which encodes the code being compiled: >>> for x in range(1000): compile("1", "test", "eval") >>> sys.getrefcount(b'1') 1004 ___ Python tracker <[EMAIL

[issue3651] eval() leaks 1 reference every time

Christian Heimes <[EMAIL PROTECTED]> added the comment: The error is inside compile, not eval: >>> compile("1", "test", "eval") at 0x7ffe1ce2ed50, file "test", line 1> [43379 refs] >>> compile("1", "test", "eval") at 0x7ffe1ce2e3b0, file "test", line 1> [43380 refs] >>> compile("1", "test", "e

[issue3651] eval() leaks 1 reference every time

New submission from Amaury Forgeot d'Arc <[EMAIL PROTECTED]>: version 3.0, any call to eval() leaks one reference: >>> eval('1') 1 [42093 refs] >>> eval('1') 1 [42094 refs] >>> eval('1') 1 [42095 refs] >>> eval('1') 1 [42096 refs] -- components: Interpreter Core messages: 71783 nosy: am

[issue3650] Memory leak in bytes.split()

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Committed r65985 -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3579] SPAM

Changes by Terry J. Reedy <[EMAIL PROTECTED]>: -- title: Faites Attention en Utilisant Cette Merveille! -> SPAM ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3579] Faites Attention en Utilisant Cette Merveille!

Changes by Terry J. Reedy <[EMAIL PROTECTED]>: ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue3579] Faites Attention en Utilisant Cette Merveille!

Changes by Terry J. Reedy <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11139/unnamed ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3577] Interpreter name: python vs. python-3.0

Changes by Terry J. Reedy <[EMAIL PROTECTED]>: -- nosy: +tjreedy ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing

[issue3650] Memory leak in bytes.split()

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Go ahead. -- nosy: +benjamin.peterson ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3564] making partial functions comparable

Terry J. Reedy <[EMAIL PROTECTED]> added the comment: The default equality comparison of Python objects is by id. Some classes override this, others, in particular, functions, do not. I also agree that partial functions should not either. However, you can subclass functools.partial (I checked in

[issue3650] Memory leak in bytes.split()

New submission from Amaury Forgeot d'Arc <[EMAIL PROTECTED]>: ./python Lib/test/regrtest.py -R:: test_bytes reveals a leak in py3k. This is exactly the same as the one corrected by r65785 to bytearray. (easy) patch attached, needs approval! -- files: bytes-split.patch keywords: needs re

[issue3602] Move test.test_suport.catch_warning() to the 'warnings' module

Brett Cannon <[EMAIL PROTECTED]> added the comment: I think I can clean up the code by shifting WarningMessage over to a subclass of namedtuple and moving WarningsRecorder over to a subclass of list. ___ Python tracker <[EMAIL PROTECTED]>

[issue3563] fix_idioms.py generates bad code

Terry J. Reedy <[EMAIL PROTECTED]> added the comment: Why is the statement, whatever it is, even being touched? Would not the same problem arise with any following outdented line? IOW, why not delete that pair of lines from fix_idioms.py? Does that break anything else in test_fixers? --

[issue3649] IA5 Encoding should be in the default encodings

Pascal Bach <[EMAIL PROTECTED]> added the comment: Well I have seen the problem. I'm willing to do this to improve python, but I don't know exactly how to do it. I looked at how utf-8 and utf-7 are done but I didn't exactly understand, are they based on C code? Is there an example how this ne

[issue2367] Fixer to handle new places where parentheses are needed

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Thanks for the work! I reviewed the code, added support for generator expressions, and wrote a few more tests. Committed in r65981. -- resolution: -> fixed status: open -> closed ___ Python tra

[issue3639] segfaults calling warnings.warn() with non-string message

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: On Fri, Aug 22, 2008 at 2:59 PM, Brett Cannon <[EMAIL PROTECTED]> wrote: > > Brett Cannon <[EMAIL PROTECTED]> added the comment: > > That's why the keyword is set. =) Ah. I missed that. :) The patch looks fine. > >

[issue3639] segfaults calling warnings.warn() with non-string message

Brett Cannon <[EMAIL PROTECTED]> added the comment: That's why the keyword is set. =) ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-

[issue3642] Objects/obmalloc.c:529: warning: comparison is always false due to limited range of data type

Christian Heimes <[EMAIL PROTECTED]> added the comment: The warning in obmalloc.c was silenced in r65975 (trunk) and r65976 (py3k) ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3649] IA5 Encoding should be in the default encodings

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: The provided file does not work for "EXTENSION" characters: >>> import ia5 >>> u"[a]".encode("ia5") Traceback (most recent call last): File "", line 1, in File "ia5.py", line 18, in encode return codecs.charmap_encode(input,err

[issue3643] Add more checks to testcapi

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Ok. I'll apply your patches when we get to 2.7. Do ping me if a forget, though. -- assignee: -> benjamin.peterson ___ Python tracker <[EMAIL PROTECTED]> _

[issue3187] os.listdir can return byte strings

Guido van Rossum <[EMAIL PROTECTED]> added the comment: See http://codereview.appspot.com/3055 for a code review of Victor's latest patches. ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3352] Deficiencies in multiprocessing/threading API

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Here's a patch. Added file: http://bugs.python.org/file11221/get_name.patch ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3352] Deficiencies in multiprocessing/threading API

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: There are still some instances of get_name() in threading.py itself, which gives errors like the following: Unhandled exception in thread started by > Traceback (most recent call last): File "/home/antoine/cpython/cpickle/Lib/threading.py"

[issue3639] segfaults calling warnings.warn() with non-string message

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Brett, is this patch ready for review? -- nosy: +benjamin.peterson ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3639] segfaults calling warnings.warn() with non-string message

Brett Cannon <[EMAIL PROTECTED]> added the comment: The patch doesn't actually bother with a translation as the code causing issue is only there to prevent infinite recursion. So if the object being used is not a string, then there is no need to worry as it is not part of the infinite recursion p

[issue3640] test_cpickle crash on AMD64 Windows build

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Here is an additional patch which adds a cpickle test to Misc/find_recursion_limit.py. It helps show that Amaury's patch does fix the issue. +1 for applying it. Added file: http://bugs.python.org/file11219/find_recursion_limit.patch

[issue3639] segfaults calling warnings.warn() with non-string message

Brett Cannon <[EMAIL PROTECTED]> added the comment: On Fri, Aug 22, 2008 at 8:03 AM, Daniel Diniz <[EMAIL PROTECTED]> wrote: > > Daniel Diniz <[EMAIL PROTECTED]> added the comment: > > Brett, > I don't think I know C (and CPython) enough to fix this. I was able to > get rid of this specific segfa

[issue3644] ``make htmlview`` for docs fails on OS X

Brett Cannon <[EMAIL PROTECTED]> added the comment: On Fri, Aug 22, 2008 at 6:12 AM, Benjamin Peterson <[EMAIL PROTECTED]> wrote: > > Benjamin Peterson <[EMAIL PROTECTED]> added the comment: > > This is probably actually a problem with the webbrowser module. Try > running "import webbrowser; webb

[issue3555] Regression: nested exceptions crash (Cannot recover from stack overflow)

Daniel Diniz <[EMAIL PROTECTED]> added the comment: Antoine, All the cases I could find would be more "test" than "use" cases. Given that most ways to abort I find in 3.0 are related to "undetected error"s in trunk, I'm almost convinced that 3.0 is right here :) My last worry is that it'd be kin

[issue3640] test_cpickle crash on AMD64 Windows build

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Attached patch removes the big array, items are saved when they are fetched from the container. I preserved the the special case when there is only one item. The patch does not merge cleanly into py3k, but the functions batch_list and b

[issue3595] Windows base64 Decode

Eric Smith <[EMAIL PROTECTED]> added the comment: Please upload your script, or (preferably) some small test code. I suspect the problem is related to line endings and binary versus text files. -- nosy: +eric.smith ___ Python tracker <[EMAIL PROTECTE

[issue3187] os.listdir can return byte strings

STINNER Victor <[EMAIL PROTECTED]> added the comment: To continue in the "accept bytes filenames" way, a new patch for fnmatch.filter(). Use sys.getfilesystemencoding() to convert the bytes. The patch contains a new unit test. Added file: http://bugs.python.org/file11215/fnmatch_bytes.patch _

[issue3640] test_cpickle crash on AMD64 Windows build

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: The problem comes from this local variable in batch_list() and batch_dict: PyObject *slice[BATCHSIZE]; and BATCHSIZE=1000... -- nosy: +amaury.forgeotdarc ___ Python tracker <[EMAIL PROTEC

[issue3187] os.listdir can return byte strings

STINNER Victor <[EMAIL PROTECTED]> added the comment: Patch glob.glob() to accept directory with invalid filename (invalid in the filesystem charset): just ignore bytes => str conversion error. Added file: http://bugs.python.org/file11216/glob1_bytes.patch _

[issue3649] IA5 Encoding should be in the default encodings

New submission from Pascal Bach <[EMAIL PROTECTED]>: This encoding is used in the GSM standard it is a 7-bit encoding similar to ASCII. The encoding definition is found in: Short Message Service Centre EMI - UCP Interface 4.6 Specification (p. 79) as well as in: [3GPP 23.038] 3GPP TS 23.038 Alp

[issue1777458] glob doesn't return unicode with unicode parameter

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Seems fixed on 2.6. Python 2.6b3+ (trunk, Aug 22 2008, 11:27:51) [MSC v.1500 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import glob >>> glob.glob("*.py") ['iocrash.py', 'setup.py'] >>>

[issue3648] 'ascii' shoud be range(256) or just set another default encoding

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: > Sometimes > encoding problems in Python are driving me mad. The thing is, they are not "encoding problems in Python", they are encoding problems in the outside world. Python cannot know magically which encoding is used in third-party data,

[issue3187] os.listdir can return byte strings

STINNER Victor <[EMAIL PROTECTED]> added the comment: My last patch (posix_join_bytes.patch) is also enough to fix the initial reported problem: error in posixpath.join() called by os.walk(). I tried os.walk() on a directory with invalid filenames and invalid directory name and it works well.

[issue3187] os.listdir can return byte strings

STINNER Victor <[EMAIL PROTECTED]> added the comment: @gvanrossum: os.unlink() and os.lstat() already accept byte filenames (but open() doesn't). Ok, here is very small patch for posixpath.join() to accept bytes strings. This patch is enough to fix my initial problem (#3616). Added file: http

[issue3639] segfaults calling warnings.warn() with non-string message

Daniel Diniz <[EMAIL PROTECTED]> added the comment: Brett, I don't think I know C (and CPython) enough to fix this. I was able to get rid of this specific segfault with this: -const char *text_char = _PyUnicode_AsString(text); +const char *text_char = _PyUnicode_AsString(

[issue3187] os.listdir can return byte strings

Guido van Rossum <[EMAIL PROTECTED]> added the comment: I'm not interested in the InvalidFilename class; it's an API complification that might seem right for your situation but will hinder most other people. However I *am* interested in a patch that makes os.unlink() (and as many other functions

[issue3187] os.listdir can return byte strings

STINNER Victor <[EMAIL PROTECTED]> added the comment: I implemented the "invalid filename" class feature: - by default, os.listdir() raise an error (UnicodeDecodeError) on invalid filename. The previous behaviour was to return bytes object instead of str. - if invalid_filename=True: create an

[issue3648] 'ascii' shoud be range(256) or just set another default encoding

New submission from electronixtar <[EMAIL PROTECTED]>: One of the MOST common scene for Python developers on CJK/Widecharacter is this error: 'ascii' codec can't decode byte 0xe5 in position 0: ordinal not in range (128) Why cann't Python just define ascii to range(256), or alternatively, ju

[issue1504] Add 2to3 fixer for (un)bound methods

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Must this still be open? -- nosy: +benjamin.peterson ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue2968] Test_imports takes a long time to run

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: This is no longer an issue. -- nosy: +benjamin.peterson resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3644] ``make htmlview`` for docs fails on OS X

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: This is probably actually a problem with the webbrowser module. Try running "import webbrowser; webbrowser.open('build/html/index.html')" on the plain Python shell. -- components: +Library (Lib) -Documentation nosy: +benjamin.peter

[issue3647] urlparse - relative url parsing and joins to be RFC3986 compliance

Changes by Senthil <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file11209/urlparse_rfc3986-py3k.diff ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3647] urlparse - relative url parsing and joins to be RFC3986 compliance

New submission from Senthil <[EMAIL PROTECTED]>: Attaching two patches to make the current urlparse library, especially the relative url parsing and urljoin to be RFC3986 compliance. I have included all the tests prescribed in RFC3986 and verified them to pass with the patches. Our parsing fu

[issue3493] No Backslash (\) in IDLE 1.2.2

mounty <[EMAIL PROTECTED]> added the comment: @ Terry J. Reedy If it is working for you it doesn't necessarily mean that it is working for mankind in general. I traced down the problem to the OS X- implementation of Idle in general and submitted an inquiry to the general python list as you sugg

[issue3611] invalid exception context

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Hmm, answering to myself, I don't think dropping exception normalization would solve the problem, it would just let it occur in a different place... ___ Python tracker <[EMAIL PROTECTED]>

[issue3611] invalid exception context

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Agreed with Amaury, it's not PyErr_SetObject's job to try to save/restore the tstate->exc_* variables. We'll probably have to live with the small context-losing glitches in 3.0. For 3.1, a radical solution would be to drop the "exception norm

[issue3611] invalid exception context

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Victor, your patch addresses the symptom of the problem, not the cause. The cause is that in some cases, the exception context chain is lost. Of course what could be a minor annoyance becomes dramatic when this precisely happens in code

[issue3101] global function _add_one_to_C

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: A sensible solution would be to put all the memoryview / buffer API stuff in the same standalone file (e.g. memoryobject.c), rather than having half of it dumped in abstract.c. ___ Python tracker <[EMAIL PR

[issue3101] global function _add_one_to_C

Changes by Antoine Pitrou <[EMAIL PROTECTED]>: -- nosy: +pitrou ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing

[issue2619] Document PEP 3118

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Should this be a release blocker? -- type: feature request -> behavior ___ Python tracker <[EMAIL PROTECTED]> ___

[issue2394] [Py3k] Finish the memoryview object implementation

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Guido, do we retarget the rest of this to 3.1? It sounds more reasonable to me. -- nosy: +gvanrossum ___ Python tracker <[EMAIL PROTECTED]> __

[issue3645] readline module Crashs on OpenBSD/amd64

Changes by Antoine Pitrou <[EMAIL PROTECTED]>: -- keywords: +needs review, patch priority: -> release blocker versions: +Python 2.6, Python 3.0 ___ Python tracker <[EMAIL PROTECTED]>

[issue3643] Add more checks to testcapi

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Unless someone thinks it's somehow release-critical, I'm retargetting this to 2.7/3.1. -- nosy: +pitrou versions: +Python 2.7, Python 3.1 -Python 2.6, Python 3.0 ___ Python tracker <[EMAIL PROTECTE

[issue3625] test issues on 64bit windows

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Mark, your patch is ok to me. You can check it in. ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3338] cPickle segfault with deep recursion

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: > Well, it's definitely a bug, or inconsistency, if you like, between > cPickle and pickle. There is clearly a problem with cPickle stack consumption and a new bug has been opened for this in #3640. What I don't agree with is your argument t

[issue3640] test_cpickle crash on AMD64 Windows build

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: In my opinion this is a bug in cPickle. It is completely wrong to consume more than 3KB of stack space for each recursion level, and it should be fixed. -- components: +Library (Lib) priority: -> release blocker

[issue3107] test_list uses unreasonable amounts of memory on 64-bit Linux

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Thanks, Tony! -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3643] Add more checks to testcapi

STINNER Victor <[EMAIL PROTECTED]> added the comment: @benjamin.peterson: I know but the module (installed in CPython default installation) is for testing purpose only, but invalid uses of its method would lead to inconsistent CPython internal state and that's bad :-) If you tried to say that

[issue1342811] Tkinter.Menu.delete doesn't delete command of entry

Robert Schuppenies <[EMAIL PROTECTED]> added the comment: Fixed in r65971. Backported to the release25-maint and merged into the py3k branch. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]>

[issue3646] MacOS X framework install to non-standard directory fails

New submission from Konrad Hinsen <[EMAIL PROTECTED]>: The file Mac/README in Python 2.6b3 says: Installing in another place, for instance $HOME/Library/Frameworks if you have no admin privileges on your machine, has only been tested very lightly. This can be done by configuring with --enable-

[issue648658] xmlrpc can't do proxied HTTP

Geoffrey Bache <[EMAIL PROTECTED]> added the comment: Well, strictly speaking, yes. It just feels like a rather major omission (when Python can do xmlrpc and handle proxies you hope it will handle the combination). "Desperate" doesn't really have a timeline, strangely enough :) I know I will be