This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steven.daprano
Recipients kyle.smith, steven.daprano
Date 2022-02-27.03:45:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1645933524.01.0.850759327543.issue46871@roundup.psfhosted.org>
In-reply-to
Content
Works for me in Python 3.10.0 on Linux.

After running your code, I get shared_dict is a DictProxy:

>>> shared_dict
<DictProxy object, typeid 'get_dict' at 0x7f092ccd6530>
>>> list(shared_dict.items())
[('number', 0), ('text', 'Hello World')]

and shared_lock an AcquirerProxy object.

Please double-check that the code you posted is the actual code that is failing, and copy and paste the full traceback you receive, not just a one-line summary.

Even if the error is reproducible, I doubt that the cause is what you state in the title of this issue:

BaseManager.register no longer supports lambda callable

Lambdas are just functions, they aren't a different type of callable. So the register method cannot distinguish between a lambda argument written directly in place, and a named def defined earlier then passed by name. So whatever error might be happening on your system, I doubt it has anything to do with the use of lambda syntax
History
Date User Action Args
2022-02-27 03:45:24steven.dapranosetrecipients: + steven.daprano, kyle.smith
2022-02-27 03:45:24steven.dapranosetmessageid: <1645933524.01.0.850759327543.issue46871@roundup.psfhosted.org>
2022-02-27 03:45:23steven.dapranolinkissue46871 messages
2022-02-27 03:45:23steven.dapranocreate