[issue5228] multiprocessing not compatible with functools.partial

Changes by Jakub Wilk : -- nosy: +jwilk ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/m

[issue5228] multiprocessing not compatible with functools.partial

uptimebox added the comment: Unfortunately, upgrading to 2.7 is not an option for me, since my application works on Debian stable which only includes 2.6. For now I'm settled with the following workaround: http://paste.pocoo.org/show/351774/ -- ___

[issue5228] multiprocessing not compatible with functools.partial

Amaury Forgeot d'Arc added the comment: The bug was fixed in 2.7, and not backported to 2.6. 2.6 is now in security-fix-only mode, if possible you should upgrade to 2.7. -- nosy: +amaury.forgeotdarc ___ Python tracker

[issue5228] multiprocessing not compatible with functools.partial

uptimebox added the comment: The bug still exists in 2.6.6 Process PoolWorker-2: Traceback (most recent call last): Process PoolWorker-1: Traceback (most recent call last): File "/usr/lib/python2.6/multiprocessing/process.py", line 232, in _bootstrap File "/usr/lib/python2.6/multiprocessing

[issue5228] multiprocessing not compatible with functools.partial

joseph.h.garvin added the comment: I think this bug still exists in Python 2.6.4, and I haven't tested 2.6.5, but since 2.6.4 was released 6 months after this bug was closed I assume it's still an issue. Running ndbecker's test program as is produces the following output on Solaris 10: Proce

[issue5228] multiprocessing not compatible with functools.partial

Jack Diederich added the comment: Fixed rev 70931. Happy pickling! -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue5228] multiprocessing not compatible with functools.partial

Jesse Noller added the comment: Jack offered to take a peek -- assignee: jnoller -> jackdied nosy: +jackdied ___ Python tracker ___ __

[issue5228] multiprocessing not compatible with functools.partial

Jesse Noller added the comment: I agree that this is a nice feature, however it requires adding a getstate/setstate within the functools C code. I would need a patch which does this, and adds tests to the functools/pickle test suite for this. Also, the feature will only be accepted for py3k

[issue5228] multiprocessing not compatible with functools.partial

Changes by Jesse Noller : -- priority: -> low ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue5228] multiprocessing not compatible with functools.partial

Jesse Noller added the comment: > Antoine Pitrou added the comment: > > Rather than implement a multiprocessing-specific fix, it would certainly > be better to make functools.partial picklable, as pointed out in the ML > thread Jesse linked to. > I would tend to agree

[issue5228] multiprocessing not compatible with functools.partial

Antoine Pitrou added the comment: Rather than implement a multiprocessing-specific fix, it would certainly be better to make functools.partial picklable, as pointed out in the ML thread Jesse linked to. -- nosy: +pitrou ___ Python tracker

[issue5228] multiprocessing not compatible with functools.partial

Jesse Noller added the comment: See this mail thread: http://mail.python.org/pipermail/python-dev/2009-February/086034.html ___ Python tracker ___

[issue5228] multiprocessing not compatible with functools.partial

Changes by Jesse Noller : -- assignee: -> jnoller nosy: +christian.heimes ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue5228] multiprocessing not compatible with functools.partial

New submission from ndbecker : from multiprocessing import Pool def power (x, pwr=2): return x**pwr import functools run_test = functools.partial (power, pwr=3) if __name__ == "__main__": pool = Pool() cases = [3,4,5] results = pool.map (run_test, cases) TypeError: type 'part