On Sat, 28 Jan 2017 13:10:15 +0100 Irmen de Jong <[email protected]> wrote:
> I'm not sure what the best course of action is here, but I strongly suggest > to re-open > the bug for now and not have the patch as it is right now. I think I have a proper solution in place for the next Pyro4 release (4.54). You can view the relevant commit here: https://github.com/irmen/Pyro4/commit/edfdbb2ce4279d929b306d00ac8fbc6543a0807b It avoids the immediate crash when importing Pyro4 and only raises a (meaningful) error when the user attempts to create a multiplex server, without the selectors34 module installed. My suggestion is to use this change, instead of the broken (IMO) import select as selectors patch. Even better is of course to package selectors34, but I understand that is not easily done. Irmen de Jong (Pyro4)
