Message 126868 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	naguilera
Recipients	benjamin.peterson, georg.brandl, loewis, michael.foord, naguilera, ned.deily, rhettinger, ronaldoussoren, vstinner
Date	2011-01-23.01:10:06
SpamBayes Score	1.1542906e-10
Marked as misclassified	No
Message-id	<01D58F80-5837-4BD0-86D1-15C2B87C884D@gmail.com>
In-reply-to	<1295735396.78.0.871019955973.issue10973@psf.upfronthosting.co.za>

Content
Thanks Ned for thinking of ways out. - If I had a choice, I would agree with Georg's choice (Ned's option 1): most users will not use the composite characters and need not go through complications, or worse, cannibalization of the distribution (3a and 3b are unacceptable). Perhaps the existence of the bug could be documented together with the need of a proper Tcl/Tk version. - My experience with python 3.1.3 with OS 10.6 is that when starting IDLE I always get several messages of the sort: Python(1305,0xa0a5c540) malloc: * error for object 0x1a277738: pointer being freed was not allocated * set a breakpoint in malloc_error_break to debug possibly leading to memory leaks. Thus, I am not happy with 4. - As for 5a, perhaps with the warnings of Tcl/Tk and composite crashes, one could announce this alternative installation. 5b doesn't seem to be worth the trouble, given the existence of the MacPorts version. My 2 cents. Néstor

Thanks Ned for thinking of ways out.

- If I had a choice, I would agree with Georg's choice (Ned's option 1): most users will not use the composite characters and need not go through complications, or worse, cannibalization of the distribution (3a and 3b are unacceptable).

Perhaps the existence of the bug could be documented together with the need of a proper Tcl/Tk version.

- My experience with python 3.1.3 with OS 10.6 is that when starting IDLE I always get several messages of the sort:

      Python(1305,0xa0a5c540) malloc: *** error for object
      0x1a277738: pointer being freed was not allocated
      *** set a breakpoint in malloc_error_break to debug

possibly leading to memory leaks. Thus, I am not happy with 4.

- As for 5a, perhaps with the warnings of Tcl/Tk and composite crashes, one could announce this alternative installation. 5b doesn't seem to be worth the trouble, given the existence of the MacPorts version.

My 2 cents.

Néstor

History
Date	User	Action	Args
2011-01-23 01:10:09	naguilera	set	recipients: + naguilera, loewis, georg.brandl, rhettinger, ronaldoussoren, vstinner, benjamin.peterson, ned.deily, michael.foord
2011-01-23 01:10:07	naguilera	link	issue10973 messages
2011-01-23 01:10:06	naguilera	create