Gevent is not Python3-compatible, but it would be a welcome
contribution if someone made it such.
Make sure you've seen this previous attempt:
http://groups.google.com/group/gevent/browse_thread/thread/c8abff976842bb71
http://bitbucket.org/jjonte/gevent/overview
Cheers,
Denis.
As I remember you have patch both *.py and *.c sources to get things
working.
--
Alexandre Kandalintsev
> I'm not sure what I'm doing is correct but I've started
> https://bitbucket.org/gevent/py31 and presumably I'll be able to load
> up what was in http://bitbucket.org/jjonte/gevent/ and then get
> started...
--
Alexandre Kandalintsev
I don't recall saying that, but yes, my opinion changed.
> Another question to Denis. I cloned https://bitbucket.org/denis/gevent
> and don't see for example 0.13.5 in "hg tags". Is it an actual repo?
0.13 is maintained here: https://bitbucket.org/denis/gevent-0.13
Almost all patches from it transplanted into https://bitbucket.org/denis/gevent
which is the main repo (version 0.14).
Tags require specific changeset and thus not transplanted.
> 2AnilG: I see in changelog about libev:
> "major change: use libev for an event loop, dns, http and wsgi modules
> currently don't work". Soo, now(or near feature) we'll be able to select
> between libevent and libev. However I don't expect visible changes :)
Only libev will be supported in 0.14. However, other than gevent.core
the interface of
gevent package is not changed, so transition should be smooth.
>> What's hanging me up immediately though is my unfamiliarity with the
>> build mechanisms.
>> I have actually (supposedly) built gevent but on import get: gevent/
>> core.so: Undefined symbol "ares_inet_net_pton"
Which OS?
If OS X, then try the patch from here:
http://code.google.com/p/gevent/issues/detail?id=76
> If you can give me some basic direction on the build process
Could you please provide access to your repo? I'll try to reproduce the
problem.