Interesting and instructive discussion. I would favor including the Python bindings in the tarball along with a README in the python directory explaining how to use them. That way, people who are interested would at least have them available. After all, brltty does include bindings for several languages, or did, last time I looked. John On Mon, Jan 19, 2009 at 08:30:52AM +1000, James Teh wrote: > On 18/01/2009 10:01 PM, Eitan Isaacson wrote: > >When we have a Windows binary distribution of liblouis, won't it be > >installed into a system-wide path? > Probably not by default. The standard distribution probably won't have > an installer, given that it is all command line tools. > > >Sounds like some classic dll-hell, so maybe I should take back that idea. > Perhaps not. I guess we could probably get away with installing it to > site-packages; I notice that wxPython does this. Do you know if the > default bdist_wininst target can be made to include arbitrary files into > site-packages? Should be possible with a data_files parameter or some > such... > > >Does this mean we should put Makefile.am files in the python > >directory, and make sure it is included in the general liblouis > >tarball? > Any idea what other packages which include Python bindings do? I *think* > I've usually seen them included with the tarball, especially as the > tarball is a source tarball. Can we include them in dist_extras without > having them built? I"m assuming this isn't a problem. > > -- > James Teh > Email/MSN Messenger/Jabber: jamie@xxxxxxxxxxx > Web site: http://www.jantrid.net/ > For a description of the software and to download it go to > http://www.jjb-software.com -- My websites: http://www.godtouches.org http://www.jjb-software.com Location: Madison, WI, USA For a description of the software and to download it go to http://www.jjb-software.com