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 chrysn
Recipients chrysn
Date 2011-01-07.00:32:52
SpamBayes Score 2.861853e-09
Marked as misclassified No
Message-id <>
The multiprocessing.manager.BaseManager class has a class property called _Server, defaulting to multiprocessing.manager.Server, that is used in the ._run_server method (typically invoked via .run()) to determine the class of the server that is to be created.

On the other hand, the .get_server() method creates an instance of Server independent of what is configured in ._Server. Thus, managers started via .run() behave slightly different than those started with .get_server().serve_forever(), and in a way that is hard to track.

I am aware that the ._Server property is undocumented, but it's quite useful when extending BaseManager in a way that it needs to be configured by the server.

I suggest to have .get_server() use ._Server instead of Server; I can't think of situations in which this does the wrong thing (rather, I assume that up to now, users of ._Server didn't try running with .get_server().serve_forever(); it seems ._Server is not used in the standard library).
Date User Action Args
2011-01-07 00:32:54chrysnsetrecipients: + chrysn
2011-01-07 00:32:54chrysnsetmessageid: <>
2011-01-07 00:32:52chrysnlinkissue10850 messages
2011-01-07 00:32:52chrysncreate