Re: runzeo.py exit with unexpected exit code
Etienne Robillard <[email protected]>
| Newsgroups | gmane.comp.web.zope.zodb |
|---|---|
| Message-ID | <[email protected]> |
I think it's the ZEO server which needs cooperativity. Le 2017-04-07 à 07:33, Jason Madden a écrit : > When we were doing that, we did not monkey-patch the ZEO server. In fact we had to take care *not* to monkey-patch if we happened to be imported in the server during conflict resolution (patching that late will certainly break things). > > >> I created a new repository for tracking my experimental ZODB changes: >> >> https://bitbucket.org/tkadm30/zodb-gevent > I doubt that hacking on such an old, outdated ZEO is going to gain you very much (when it looks like focusing on connection management issues is the way to go) or find many people interested in helping. > I'm aiming for a proof-of-concept first, then I'll upgrade to ZODB 4/5. > > [1] http://www.gevent.org/gevent.monkey.html#gevent.monkey.patch_select > [2] You could also try to disable patching of threads, but ZEO<5 uses a lot of threads and presumably that's why you're interested in monkey-patching in the first place. Indeed. I need/want a gevent-aware ZEO server. Regards, E -- Etienne Robillard [email protected] http://www.isotopesoftware.ca/ -- You received this message because you are subscribed to the Google Groups "zodb" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.