[issue9207] multiprocessing occasionally spits out exception during shutdown (_handle_workers)
Matthew Walker added the comment: It looks to me as if this issue has already been pretty much sorted out already. Maybe all it lacks is to be officially closed, but just in case I just wanted to add that I too saw this bug (stock python 2.7, Ubuntu 10.04 64 bit). My example code was: #!/usr/bin/env python import multiprocessing import os import time def f(i): print "I am process number",os.getpid(),": i =",i time.sleep(10) return i*i pool = multiprocessing.Pool(maxtasksperchild=1) print pool.map(f, range(10)) -- nosy: +Matthew.Walker ___ Python tracker <http://bugs.python.org/issue9207> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9207] multiprocessing occasionally spits out exception during shutdown (_handle_workers)
Matthew Walker added the comment: Oh, and the stack trace was identical to Greg's: $ ./test.py I am process number 10378 : i = 0 [...] I am process number 10390 : i = 9 [0, 1, 4, 9, 16, 25, 36, 49, 64, 81] Exception in thread Thread-1 (most likely raised during interpreter shutdown): Traceback (most recent call last): File "/gel/usr/mawal32/system/lib/python2.7/threading.py", line 530, in __bootstrap_inner File "/gel/usr/mawal32/system/lib/python2.7/threading.py", line 483, in run File "/gel/usr/mawal32/system/lib/python2.7/multiprocessing/pool.py", line 272, in _handle_workers : 'NoneType' object is not callable -- ___ Python tracker <http://bugs.python.org/issue9207> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42633] Wave documentation doesn't mention signed/unsigned requirements
New submission from Matthew Walker : It would be very useful if the documentation for Python's Wave module mentioned that 8-bit samples must be unsigned while 16-bit samples must be signed. See the Wikipedia article on the WAV format: "There are some inconsistencies in the WAV format: for example, 8-bit data is unsigned while 16-bit data is signed" https://en.wikipedia.org/wiki/WAV Although I haven't contributed previously, I would be pleased to make such a contribution if it would be appreciated. -- assignee: docs@python components: Documentation messages: 382957 nosy: docs@python, mattgwwalker priority: normal severity: normal status: open title: Wave documentation doesn't mention signed/unsigned requirements type: enhancement versions: Python 3.10 ___ Python tracker <https://bugs.python.org/issue42633> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14756] Empty Dict in Initializer is Shared Betwean Objects
New submission from Matthew Walker : When initializing a class with an empty dict() object as a default initializer, if it is not overridden, multiple instances of the class will share the dictionary. IE: class test(object): def __init__(self, obj=dict()): self.obj = obj a = test() b = test() Then id(a.obj) points to the same location as id(b.obj). The behaviour I would expect would be that a.obj and b.obj would be unique instances. -- components: Interpreter Core messages: 160212 nosy: Matthew.Walker priority: normal severity: normal status: open title: Empty Dict in Initializer is Shared Betwean Objects versions: Python 2.7 ___ Python tracker <http://bugs.python.org/issue14756> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14756] Empty Dict in Initializer is Shared Betwean Objects
Changes by Matthew Walker : -- type: -> behavior ___ Python tracker <http://bugs.python.org/issue14756> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
