On Thu, Jan 26, 2017 at 09:10:30AM +1000, Peter Hutterer wrote: > Before I start hacking up something nasty I figured it's better to ask: how > do I build both py2 and py3 bindings from a package using autotools (i.e. > AM_PATH_PYTHON)? > > So far my idea revolves around installing both python-devel packages and > overriding PYTHON in each %build <packagename>, etc. But maybe there's a > simpler solution? > > Package in question is evemu and yes, we are also the upstream maintainers > so if there's a more sensible solution we can move that into upstream. I'd suggest splitting the bindings out into a completely independant source package and uploading that to PyPi. That facilitates people using python virtualenvs to easily build the binding against arbitrary python versions as many times as they like, as well as packaging it against both py2+3 concurrently in Fedora. Bonus points if you can make the python binding able to dynamically build against multiple different versions of the C library. This is the approach we took for libvirt when adding py3 support, rather than try to hack something up with python in-tree to the main C library. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :| _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
