[Python-Dev] Asking for reversion

Davin Potts python+python_dev at discontinuity.net
Sat Feb 23 23:09:03 EST 2019

I have done what I was asked to do:  I added tests and docs in a new
PR (GH-11816) as of Feb 10.

Since that time, the API has matured thanks to thoughtful feedback
from a number of active reviewers.  At present, we appear to have
stabilized around an API and code that deserves to be exercised
further.  To get that exercise and because there are currently no
outstanding objections, I am merging the PR to get it into the second
alpha.  There will undoubtedly be further revisions and adjustments.

During this effort, I have received a surprising number of personal
emails expressing support and encouragement from people, most of whom
I have never met.  Your kindness has been wonderful.


On Wed, Feb 6, 2019 at 10:58 AM Giampaolo Rodola' <g.rodola at gmail.com> wrote:
> On Wed, Feb 6, 2019 at 12:51 PM Giampaolo Rodola' <g.rodola at gmail.com> wrote:
>> Unless they are already there (I don't know) it would be good to have a full set of unit-tests for all the register()ed types and test them against SyncManager and SharedMemoryManager. That would give an idea on the real interchangeability of these 2 classes and would also help writing a comprehensive doc.
> In order to speed up the alpha2 inclusion process I created a PR which implements what said above:
> https://github.com/python/cpython/pull/11772
> https://bugs.python.org/issue35917
> Apparently SharedMemoryManager works out of the box and presents no differences with SyncManager, but the list type is not using ShareableList. When I attempted to register it with "SharedMemoryManager.register('list', list, ShareableList)" I got the following error:
> Traceback (most recent call last):
>   File "foo.py", line 137, in test_list
>     o = self.manager.list()
>   File "/home/giampaolo/svn/cpython/Lib/multiprocessing/managers.py", line 702, in temp
>     proxy = proxytype(
> TypeError: __init__() got an unexpected keyword argument 'manager'
> I am not sure how to fix that (I'll leave it up to Davin). The tests as-is are independent from PR-11772 so I suppose they can be reviewed/checked-in regardless of the changes which will affect shared_memory.py.
> --
> Giampaolo - http://grodola.blogspot.com

More information about the Python-Dev mailing list