Hi, First of all, let me apologize for the delay (real life has been a little bit of a struggle lately, leaving me little or no free time for pyev).
On Thu, 30 Apr 2009 19:56:14 +0200 "[email protected]" <[email protected]> wrote: > Malek Hadj-Ali wrote: > > Hi, > > > > Pyev (http://code.google.com/p/pyev/) is a python extension wrapper > > around libev. > > As I had issues compiling/installing it ... I took some > countermeasures. > > As I doubt its usefull to ship the binding with libev itself, I > decided to make it use a local libev installation. I can't really agree on this. You see, libev api evolves and pyev tries to follow it, so it makes sense to ship pyev with a matching libev version (of course there's always a better approach, but I'll stick with the easiest for the time being). Oh yeah (almost forgot this one), and I have to embed libev to have large file support in ev_stat watchers (python being mostly built with LFS, see http://lists.schmorp.de/pipermail/libev/2008q1/000232.html and http://lists.schmorp.de/pipermail/libev/2008q2/000381.html). > The code to detect python 3.1 did not work with python 3.1a+ as the > version numbers are strings instead of ints. Yeah. Pyev 0.4.0-3.53 was released on 03/12. On 03/26 platform.py was changed (see http://svn.python.org/view?view=rev&revision=70628 and http://bugs.python.org/issue5561), that's the price to pay for working with an alpha release :-). This is going to be fixed in the next release. Is this the only compiling/installing issue you had? > > I wrapped the setup.py thing into an automake container, which > creates setup.py from setup.py.in, filling the pathes for libev > library and header, including python version detection. > > > The LIBEV_VERSION you grabbed from libevs configure.ac is the only > problem, as I can't get that information. > > I'd really appreciate if you could apply these changes to pyev, as > they make it work. > > to use: > autoreconf -vi > ./configure --help > make install > make dist > > for me: > autoreconf -vi; ./configure --with-ev-include=/opt/libev/include > --with-ev-lib=/opt/libev/lib/ --with-python=/usr/bin/python3.1; make > install; make dist > > -Wl,rpath is set, so the library is linked correctly. > > A real great feature: > if you embed python into your libev powered application, you can use > these bindings to insert watchers into your applications > ev_default_loop from python, great work! That is a great feature, and I'll keep that in mind for another project that I have going, but for now I think I'm gonna stick with the more traditional way of distributing python extension modules (that is one that only requires a 'sudo python3 setup.py install' and you should be done). > > > As a diff is larger than the whole thing packed, there is a tar > attached. > > > Markus _______________________________________________ libev mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
