Comment 2 for bug 1827055

Quick update, just to keep this bug alive. We have a branch of Syrup functional on Python 3. It is currently entangled with all of our local customizations, and I can't provide at this point a solid ETA on getting that untangled, but mid-May would be a reasonable guess. (Many of those customizations probably deserve consideration for inclusion in mainline Syrup as well.) It should be noted that Syrup does not actually run Python OSRF services, so this does not mean that the full OpenSRF Python libraries (I don't like to call them bindings) are ready for Python 3. In fact, I do not recall OTTOMH whether getting Syrup to work required any changes to the Evergreen Python code at all. It certainly was not the majority of it.

It will probably make sense to split off the Syrup pieces to a new bug (if there isn't already one). I'll do that when the branch is ready to post. We might end up with a middle ground of saying we support Python as a consumer of OSRF messages, but not a producer.