[issue3863] 2.6rc1: test_threading hangs on FreeBSD 6.3 i386

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: instrumenting Python/thread_pthread.h and turning on thread debugging in Python/thread.c, FreeBSD raises the Fatal error within pthread_create(). I'm inclined to say that this is a FreeBSD 6.3 bug. The fbsd_thr_crash.py test case is a good

[issue3863] 2.6rc1: test_threading hangs on FreeBSD 6.3 i386

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: attaching a stand alone script to exercise the bug. based on the prints, the error appears to happen during the t.start() call to launch the joiningfunc() thread from the child processes worker thread (its the main/only thread in the child

[issue3863] 2.6rc1: test_threading hangs on FreeBSD 6.3 i386

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: and as expected, also happens with py3k. -- versions: +Python 3.0 ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3871] cross building python for mingw32 with distutils

Roumen Petrov <[EMAIL PROTECTED]> added the comment: P.S.: this patch cover changes in the python C-code proposed in issue 1412448 as include only necessary modifications. ___ Python tracker <[EMAIL PROTECTED]> __

[issue3870] Parser/asdl_c.py requires python in order to build python

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Yes, that's why what it builds is included in the svn repo by default. You can avoid the build problems by touching Include/Python-ast.h and Python/Python-ast.c. -- nosy: +benjamin.peterson resolution: -> invalid status: open -> c

[issue3871] cross building python for mingw32 with distutils

New submission from Roumen Petrov <[EMAIL PROTECTED]>: This is a completely new patch against trunk that try to resolve mingw32 build. The first version to show problems with current python builds system, to propose solutions/work-arounds and to be stating point for discussion. Also I prefer some

[issue3870] Parser/asdl_c.py requires python in order to build python

Changes by Gregory P. Smith <[EMAIL PROTECTED]>: -- title: Parser/adsl_c.py requires python in order to build python -> Parser/asdl_c.py requires python in order to build python ___ Python tracker <[EMAIL PROTECTED]>

[issue3870] Parser/adsl_c.py requires python in order to build python

New submission from Gregory P. Smith <[EMAIL PROTECTED]>: Parser/asdl_c.py starts with "#! /usr/bin/env python" and is required when building python. The prevents python from being built on systems without an existing python interpreter installed. Which came first, the python or the egg? fou

[issue3863] 2.6rc1: test_threading hangs on FreeBSD 6.3 i386

Changes by Gregory P. Smith <[EMAIL PROTECTED]>: -- nosy: +gregory.p.smith ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-li

[issue3869] Arrow keys not working with Python 2.6rc1

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- resolution: -> invalid status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3869] Arrow keys not working with Python 2.6rc1

Daniel <[EMAIL PROTECTED]> added the comment: That was it. Needed to install libreadline5-dev. Then the default settings for readline in Modules/setup needs uncommented (line 165 in the current version) and it works. Thank you kindly. ___ Python tracker <[E

[issue3617] Add MS EULA to the list of third-party licenses in the Windows installer

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: This is now fixed in r66460 and r66462; the text that gets included is in Tools/msi/crtlicense.txt. -- keywords: -easy resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROT

[issue3869] Arrow keys not working with Python 2.6rc1

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: ubuntu? make sure you have the libreadline5-dev package installed. then make distclean && ./configure && make -- nosy: +gregory.p.smith priority: -> normal ___ Python tracker <[EMAIL PROTECTED

[issue3869] Arrow keys not working with Python 2.6rc1

Daniel <[EMAIL PROTECTED]> added the comment: Yes I did the configure / compile myself. After reading about readline in setup I am still unable to enable it but I guess it is not a bug in Python but more a user problem. I am quite puzzled as to why something like this would stop being enabled b

[issue1641] asyncore delayed calls feature

Changes by Giampaolo Rodola' <[EMAIL PROTECTED]>: -- components: +Library (Lib) -Installation versions: +Python 2.7, Python 3.1 -Python 2.6 ___ Python tracker <[EMAIL PROTECTED]> _

[issue1641] asyncore delayed calls feature

Changes by Giampaolo Rodola' <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file8977/asyncore.py ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue1641] asyncore delayed calls feature

Giampaolo Rodola' <[EMAIL PROTECTED]> added the comment: I try to revamp this issue by attaching a new patch which improves the work I did against asyncore last time. The approach proposed in this new patch is the same used in the upcoming pyftpdlib 0.5.0 version which has been largely tested and

[issue3825] Major reworking of Python 2.5.2 re module

Changes by Giampaolo Rodola' <[EMAIL PROTECTED]>: -- nosy: +giampaolo.rodola ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Guilherme Polo <[EMAIL PROTECTED]> added the comment: Can you check if it is not the itimer tests that are causing that ? I'm interested in gathering some more info about the problem and hopefully fixing it now. Take a look into issue2240 and verify if it is related to your problem, please.

[issue3869] Arrow keys not working with Python 2.6rc1

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: This probably has something to do with your readline build? Did you compile Python yourself? -- nosy: +benjamin.peterson ___ Python tracker <[EMAIL PROTECTED]>

[issue3869] Arrow keys not working with Python 2.6rc1

New submission from Daniel <[EMAIL PROTECTED]>: On Xubuntu 8.04. In Python2.5 arrow keys allowed you to scroll through previous lines typed but with 2.6rc1 this stopped working and it's now just typing the ^[[A^[[B^[[D^[[C characters. -- messages: 73229 nosy: Chewie severity: normal stat

[issue3690] sys.getsizeof wrong for Py3k bool objects

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: >> In any case, I also think this doesn't matter much either way. > Why do you think so? What's the actual difference that this change makes? At most 8 bytes per object, right? And for two objects in total. So if somebody would compute memo

[issue3866] int() doesn't 'guess'

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Thanks for the suggestion! Fixed in r66459. -- nosy: +benjamin.peterson resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3859] test_sys.Sizeof fails on win64

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Looks good to me. -- keywords: -needs review nosy: +benjamin.peterson ___ Python tracker <[EMAIL PROTECTED]> ___ _

[Wurfpost] Invitation to indoor coed tournament 'Schreeuw van de Meeuw'

Ladies and gentlemen, The indoor season starts again with an indoor coed tournament in Nijmegen. You can subscribe to this tournament by sending an e-mail to [EMAIL PROTECTED] Subscription to this tournament is open till 3th of October. Further information: a.. Date: 25th and 26th of October

[issue3862] test_array fails on FreeBSD7 amd64

Reed O'Brien <[EMAIL PROTECTED]> added the comment: 2.6rc2 and Python-3.0b3 test_array detail test_alloc_overflow (test.test_array.DoubleTest) ... Killed Fills swap space and dumps core. 2.5.2 test_list test_addmul (test.test_list.ListTest) ... ok test_append (test.test_list.ListTest) ...

[issue3868] patch for review: OS/2 EMX port fixes for 2.6

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: The patches look good to me. I first thought that there could be a difference between PyOS_strnicmp and PyOS_mystrnicmp, but both Microsoft's strnicmp and python's PyOS_mystrnicmp are sensitive to the current locale. Another unrelate

[issue3781] warnings.catch_warnings fails gracelessly when recording warnings but no warnings are emitted

Changes by Nick Coghlan <[EMAIL PROTECTED]>: -- keywords: +needs review ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list

[issue3781] warnings.catch_warnings fails gracelessly when recording warnings but no warnings are emitted

Nick Coghlan <[EMAIL PROTECTED]> added the comment: 3.0 version of the patch attached (it turned that it wasn't so much test_support itself that caused the forward port problems, as the fact that most of the tests that use this feature in 2.x are testing specifically for Py3k warnings, or for oth

[issue3680] Cycles with some iterator are leaking.

Robert Schuppenies <[EMAIL PROTECTED]> added the comment: > I think it's ok, since the underlying containers will get cleared, thus > breaking the cycle. What about the dictiter object which references a tuple (di_result)? Tuple does not implement tp_clear, but OTOH tuples are immutable and di_r

[issue3770] test_multiprocessing fails on systems with HAVE_SEM_OPEN=0

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: 2.6rc1 shows the same failure traceback on FreeBSD 6.3, which is covered by a section of setup.py the same as Damien added for OpenBSD. -- nosy: +aimacintyre ___ Python tracker <[EMAIL PROTECTE

[issue3861] distutils CCompiler._compile doesn't require lang keyword argument

Mike Auty <[EMAIL PROTECTED]> added the comment: You're absolutely right, it was a Gentoo patching issue. Thanks very much for the link to the bug, I would never have found it myself! 5:) I'm off to go try and convince them it's a bad idea to patch interfaces... __

[issue3861] distutils CCompiler._compile doesn't require lang keyword argument

Changes by Amaury Forgeot d'Arc <[EMAIL PROTECTED]>: -- resolution: -> invalid status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3861] distutils CCompiler._compile doesn't require lang keyword argument

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Your problem seems very similar to http://bugs.gentoo.org/219238 but it seems that the Gentoo installation uses a patched version of python. there is no "lang" parameter at all in the official version... Do you use a patched version of

[issue3861] distutils CCompiler._compile doesn't require lang keyword argument

Mike Auty <[EMAIL PROTECTED]> added the comment: Sorry, scratch that, it turned out to be a patch added by a local packager. I don't seem to be able to close my own bug, but for anyone who's triaging this, please mark this as CLOSED/INVALID or similar. Sorry for the inconvenience... __

[issue3868] patch for review: OS/2 EMX port fixes for 2.6

New submission from Andrew I MacIntyre <[EMAIL PROTECTED]>: The 2 attached patch files are patches required for the OS/2 EMX port to build and function: - build_os2emx.patch - updates to the Makefile and config files in PC/os2emx; - source_os2emx.patch - updates to various core/library/test files

[issue3865] explain that profilers should be used for profiling, not benchmarking

Fredrik Lundh <[EMAIL PROTECTED]> added the comment: (the reason this is extra bad for C modules is that the profilers introduce overhead for Python code, but not for C-level functions. For example, using the standard profiler to benchmark parser performance for xml.etree.ElementTree vs. xml.etr

[issue3868] patch for review: OS/2 EMX port fixes for 2.6

Changes by Andrew I MacIntyre <[EMAIL PROTECTED]>: -- components: Build, Interpreter Core, Library (Lib), Tests files: build_os2emx.patch keywords: patch, patch nosy: aimacintyre severity: normal status: open title: patch for review: OS/2 EMX port fixes for 2.6 versions: Python 2.6 Added

[issue3867] What's New in 2.6 doesn't mention stricter object.__init__

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- assignee: georg.brandl -> akuchling nosy: +akuchling ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3867] What's New in 2.6 doesn't mention stricter object.__init__

New submission from Andrew Bennetts <[EMAIL PROTECTED]>: http://bugs.python.org/issue1683368 changed object.__init__ so that rejects args/kwargs. This change should be mentioned in the "What's New in Python 2.6" document, probably under the "Porting to Python 2.6" heading. (I noticed this becau

[issue3866] int() doesn't 'guess'

New submission from Kent Johnson <[EMAIL PROTECTED]>: The library reference for int() says, "If radix is zero, the proper radix is guessed based on the contents of string; the interpretation is the same as for integer literals." The use of the word 'guess' implies that there is some heuristic use

[issue3865] explain that profilers should be used for profiling, not benchmarking

New submission from Fredrik Lundh <[EMAIL PROTECTED]>: You often see people using the profiler for benchmarking instead of profiling. I suggest adding a note that explains that the profiler modules are designed to provide an execution profile for a given program, not for benchmarking different l

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

Changes by Andrew I MacIntyre <[EMAIL PROTECTED]>: -- versions: +Python 2.6 ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-l

[issue3863] 2.6rc1: test_threading hangs on FreeBSD 6.3 i386

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: I should add that this is a regression of the trunk, as I built and tested the trunk from an SVN checkout (r63892) in early June and didn't encounter this issue. ___ Python tracker <[EMAIL PROTECTED]> <

[issue3862] test_array fails on FreeBSD7 amd64

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: 2.6rc1 test_array passes on FreeBSD 6.3 i386. I don't have a 7.0 box (either i386 or amd64) accessible at the moment to cross check. Can you run the test on its own in verbose mode to get a bit more of an idea where its blowing up? - ie:

[issue3690] sys.getsizeof wrong for Py3k bool objects

Robert Schuppenies <[EMAIL PROTECTED]> added the comment: As I understood the long object allocation it is implemented as "PyObject_MALLOC(sizeof(PyVarObject) + size*sizeof(digit))" to avoid this allocation of extra 2 bytes. So from my understanding, the number 0 allocates memory for the referenc

[issue3111] multiprocessing ppc Debian/ ia64 Ubuntu compilation error

Nick Coghlan <[EMAIL PROTECTED]> added the comment: Scratch that - it's more likely to be Neal's setup which is at fault, which I will be questioning on python-dev shortly (there are 3 other tests which are failing/getting skipped in Neal's regression test suite) -- priority: release blo

[issue3111] multiprocessing ppc Debian/ ia64 Ubuntu compilation error

Nick Coghlan <[EMAIL PROTECTED]> added the comment: Setting this to a release blocker, because it is affecting Neal's automated execution of the regression test suite with a debug build. -- nosy: +ncoghlan priority: -> release blocker ___ Python trac