[issue29423] using concurrent.futures.ProcessPoolExecutor in class giving 'TypeError: can't pickle _thread.RLock objects' in 3.6, but not 3.5

[spencera]

New submission from spencera:

I'm unable to use concurrent.futures.ProcessPoolExecutor within a class in 3.6 
the way I can in 3.5.x. I get the following in 3.6 (python3.6 test.py):

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/multiprocessing/queues.py", line 241, in _feed
obj = _ForkingPickler.dumps(obj)
  File "/usr/local/lib/python3.6/multiprocessing/reduction.py", line 51, in 
dumps
cls(buf, protocol).dump(obj)
TypeError: can't pickle _thread.RLock objects

-

No issues in 3.5.x:
0
1
2
3
4
5
6
7
8
9
0
...

--
components: Library (Lib)
files: test.py
messages: 286825
nosy: spencera
priority: normal
severity: normal
status: open
title: using concurrent.futures.ProcessPoolExecutor in class giving 'TypeError: 
can't pickle _thread.RLock objects' in 3.6, but not 3.5
type: behavior
versions: Python 3.6
Added file: http://bugs.python.org/file46496/test.py

___
Python tracker 
<http://bugs.python.org/issue29423>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue29423] using concurrent.futures.ProcessPoolExecutor in class giving 'TypeError: can't pickle _thread.RLock objects' in 3.6, but not 3.5

[spencera]

spencera added the comment:

Interesting. So, out of curiosity, what has changed from 3.5.2 to 3.6.0 that 
causes this new behavior? Was an instance associated with an instance method 
that was passed to submit not implicitly pickled before 3.6.0? Is it from the 
changes to the pickle module in 3.6? Something else?

--

___
Python tracker 
<http://bugs.python.org/issue29423>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com