[issue15542] Documentation incorrectly suggests __init__ called after direct __new__ call

2012-08-02 Thread Aaron Staley
New submission from Aaron Staley: The documentation for __new__ at http://docs.python.org/reference/datamodel.html#object.__new__ is: """ object.__new__(cls[, ...]) Called to create a new instance of class cls. __new__() is a static method (special-cased so you need not dec

[issue14877] No option to run bdist_wininst against newer msvc versions on non-windows systems

2012-05-23 Thread Aaron Staley
Aaron Staley added the comment: Hi Eric, Quick rundown: There are template 'exe' inside distutils/command. bdist_wininst appends to the template to build a customized installer. First the 64 bit bug: http://bugs.python.org/issue6792 With that bug active, I must be able to m

[issue8954] wininst regression: errors when building on linux

2012-05-21 Thread Aaron Staley
Aaron Staley added the comment: I was looking over this patch (as it relates to my bug report: http://bugs.python.org/issue14877?@ok_message=msg%20161314%20created%3Cbr%3Eissue%2014877%20message_count%2C%20messages%20edited%20ok&@template=item) and noticed that this line: +if

[issue14877] No option to run bdist_wininst against newer msvc versions on non-windows systems

2012-05-21 Thread Aaron Staley
Aaron Staley added the comment: Sorry, minor correction: We could just rely on plat_name for 64bit. All that is needed is for this table: if self.target_version < "2.4": bv = 6.0 else: bv = 7.1 to

[issue14877] No option to run bdist_wininst against newer msvc versions on non-windows systems

2012-05-21 Thread Aaron Staley
New submission from Aaron Staley : On a *nix system, bdist_wininst.get_exe_bytes will always return an open wininst-6.0.exe. However, Windows python2.7 is compiled against msvc 9.0 and ideally would take an installer based on wininst-9.0.exe. Windows-64bit needs an installer based on

[issue14573] json iterencode can not handle general iterators

2012-04-13 Thread Aaron Staley
New submission from Aaron Staley : The json library's encoder includes a function called 'iterencode'. iterencode allows for encoding to be streamed; as tokens are produced they are yielded. This allows for the encoded object to be streamed to a file, over a socket, etc. witho

[issue13992] Segfault in PyTrash_destroy_chain

2012-02-13 Thread Aaron Staley
Aaron Staley added the comment: BTW, I take back what I said about using PyThreadState_SetAsyncExc. Turns out I had a bug where this function would never succeed (was always returning 0). -- ___ Python tracker <http://bugs.python.org/issue13

[issue13992] Segfault in PyTrash_destroy_chain

2012-02-13 Thread Aaron Staley
Aaron Staley added the comment: I see no invalid read/write. Only warnings are some conditional jump depends on uninitialized value in pycrypto's libraries very early on though. The link seems to be a different bug from mine. I did test in python 2.6.7 and the crash still occurs. (I

[issue13992] Segfault in PyTrash_destroy_chain

2012-02-13 Thread Aaron Staley
Aaron Staley added the comment: Unfortunately, my application is running so slow under valgrind that behavior is changing, namely the sockets are all timing out. -- ___ Python tracker <http://bugs.python.org/issue13

[issue13992] Segfault in PyTrash_destroy_chain

2012-02-12 Thread Aaron Staley
Aaron Staley added the comment: Also, the only particular things by code does is have a lot of threads (100+), holds open many ssh connections (with paramiko) and I do occasionally use PyThreadState_SetAsyncExc to asynchronously terminate threads

[issue13992] Segfault in PyTrash_destroy_chain

2012-02-12 Thread Aaron Staley
Aaron Staley added the comment: Used latest mercurial 2.7 branch and segfault still occurs. -- ___ Python tracker <http://bugs.python.org/issue13992> ___ ___

[issue13992] Segfault in PyTrash_destroy_chain

2012-02-12 Thread Aaron Staley
Aaron Staley added the comment: I should note that my program is also affected by this bug: http://bugs.python.org/issue13817 (couldn't isolate it until I used the pydebug configure info). -- ___ Python tracker <http://bugs.python.org/is

[issue13992] Segfault in PyTrash_destroy_chain

2012-02-12 Thread Aaron Staley
Aaron Staley added the comment: As far as I can tell, no other thread is active. Their backtraces are all either: #0 0x7f283dedd300 in sem_wait () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00519295 in PyThread_acquire_lock (lock=0xe7dd50, waitflag=1) at Python

[issue13992] Segfault in PyTrash_destroy_chain

2012-02-12 Thread Aaron Staley
Aaron Staley added the comment: Active extension modules are MySQL-python, numpy, and crypto. Here is the output from the non-optimized debug build. Slightly different trace, but still some sort of deallocator crashing AFAIK: #0 0x0046247c in _Py_ForgetReference (op= , _pipe

[issue13992] Segfault in PyTrash_destroy_chain

2012-02-11 Thread Aaron Staley
Aaron Staley added the comment: For some more context: Python 2.7.2 Running on Amazon EC2 Linux 3.0.0-14-virtual x86_64 in ubuntu 11.10 170 threads in this particular core dump (another similar crash has 135) -- ___ Python tracker <h

[issue13992] Segfault in PyTrash_destroy_chain

2012-02-11 Thread Aaron Staley
New submission from Aaron Staley : Am frequently getting segmentation faults with my python program. I am utilizing heavy use of threading and sockets. All sorts of ones are showing in syslog: kernel: [7763578.475590] python[10097]: segfault at 88e5a0 ip 0088e5a0 sp 7f640efd4028

[issue13106] Incorrect pool.py distributed with Python 2.7 windows 32bit

2011-10-05 Thread Aaron Staley
Aaron Staley added the comment: Never mind; looks like this functionality was moved to handle_workers. I had inadvertently been testing under a modified pool.py. Sorry for the inconvenience! -- resolution: -> invalid status: open ->

[issue13106] Incorrect pool.py distributed with Python 2.7 windows 32bit

2011-10-04 Thread Aaron Staley
New submission from Aaron Staley : The multiprocess/pool.py distributed with the Python 2.7.2 Windows Installer is different from the one distributed with the 64 bit windows installer or source tarball - and is buggy. Specifically, see Pool._terminate_pool: def _terminate_pool(cls