Re: [PyWrapper-devel] Libraries distribution in PyWrapper
Status: Alpha
Brought to you by:
jatorre
Menu
▾
▴
Re: [PyWrapper-devel] Libraries distribution in PyWrapper
|
From: <m.d...@BG...> - 2006-08-02 12:27:04
|
guessed right. its becoming like the gbif super-all-inclusive-installer then.=20 which noone uses because you cant adapt it to your system. -- Markus =20 > -----Urspr=FCngliche Nachricht----- > Von: pyw...@li...=20 > [mailto:pyw...@li...] Im=20 > Auftrag von Javier privat > Gesendet: Mittwoch, 2. August 2006 13:16 > An: D=F6ring, Markus > Cc: PyWrapper Developers mailing list > Betreff: Re: [PyWrapper-devel] Libraries distribution in PyWrapper >=20 > Yes, it works for me... >=20 > SOAPpy and biomoby are pure Python so we can bundle. >=20 > I think mxDateTime as you said is fine... the proble is if=20 > you use the odbc stuff if I remember... so this one can not=20 > even be distributed, it MUST be downloaded from their site...=20 > apart of this I think we can include all of them in PyWrapper=20 > and create an installer scripts that does the work for the user... >=20 > With this I will be satisfied... also we will have much more=20 > control over the libraries versions... >=20 > And now an even more dramatic suggestion... what about=20 > including Python itself also? So in Windows in easy, you just=20 > have to run the installer (PyWrapper) and everything,=20 > including Pthon is installed for you in a folder, we dont=20 > touch anything. > In Unix we can create an installer that installs python and=20 > all requiered libraries under our folder... >=20 > I know it is not the most common way of distributing=20 > applications, but if this is gonna get deploy in so many=20 > places this looks like it will save us some headaches... >=20 > Now Markus I know will not like the idea :D >=20 > Cheers. >=20 > On 8/2/06, "D=F6ring, Markus" <m.d...@bg...> wrote: > > Javi, > > you are perfectly right. its getting horrible. > > Actually Ive already bundled a library with pywrapper.=20 > Everything under lib which is not biocase/ is external stuff. > > So we should go through the required libs and if they do=20 > not need to be compiled, so if they are pure python, we can=20 > simply add them to our lib folder! > > > > But > > > 1)PyXML > > > 2)mxDateTime > > > 3)CherryPy > > need to be compiled for sure > > > > with > > > 4)elementtree > > > 5)kid > > and your additional ones we need to check. > > SOAPpy for example I think is pure python. > > > > > > In case users have these libraries installed in their=20 > system, we might get into trouble. > > But if we make sure (which I think is the case already!)=20 > that our lib path comes before the regular system lib path in=20 > sys.path, then our libs will be imported. > > > > For example: > > http://search.biocase.org/tapir/configtool/environment > > > > shows our loib folder before the others: > > ['/home/biocase/tapir/lib/biocase/..', '/home/biocase/tapir/lib',=20 > > '/home/biocase/tapir/webapp', '/usr/lib/python24.zip',=20 > > '/usr/lib/python2.4', '/usr/lib/python2.4/plat-linux2',=20 > > '/usr/lib/python2.4/lib-tk', '/usr/lib/python2.4/lib-dynload',=20 > > '/usr/local/lib/python2.4/site-packages',=20 > > '/usr/lib/python2.4/site-packages',=20 > > '/usr/lib/python2.4/site-packages/setuptools-0.6a7-py2.4.egg',=20 > > '/usr/lib/python2.4/site-packages/kid-0.9-py2.4.egg',=20 > > '/usr/lib/python2.4/site-packages/wsgiref-0.0.1-py2.4.egg'] > > > > > > For the compiled libs I would suggest: > > > > 1) create a compiled version for windows > > 2) include the source installers in our package, so people=20 > dont have to go and look for the right version. > > > > > > With mx.DateTime we need to get in touch with eGenix. I=20 > know they dont like the idea in general (they've been=20 > contacting me during biocase times). But if we dont use the=20 > entire mxEgenixBase package, but only mxDateTime, they might=20 > be OK. it comes with linux distributions anyways. > > > > Does this work for you? > > > > -- Markus > > > > > > > -----Urspr=FCngliche Nachricht----- > > > Von: pyw...@li... > > > [mailto:pyw...@li...] Im Auftrag=20 > > > von Javier privat > > > Gesendet: Mittwoch, 2. August 2006 12:24 > > > An: PyWrapper Developers mailing list > > > Betreff: [PyWrapper-devel] Libraries distribution in PyWrapper > > > > > > Hi, > > > > > > I was wondering if we could change a bit our strategy for=20 > deploying=20 > > > PyWrapper. Right now to install it you have to install: > > > > > > 1)PyXML > > > 2)mxDateTime > > > 3)CherryPy > > > 4)elementtree > > > 5)kid > > > > > > Then you probably will also need: > > > > > > 6) libxml2 > > > 7) a database module > > > > > > and finally if you want BioMOBY support now I will also=20 > be requiring: > > > > > > 8) fpconst > > > 9) SOAPpy > > > 10) BioMOBY Python > > > > > > This is getting a little bit horrible to install. I think most of=20 > > > these libraries, I think actually all, can be legally=20 > redistributed=20 > > > with other software so I was wondering if we could not embed=20 > > > everything into PyWrapper. > > > > > > Well, I know there are some problems. Some of these=20 > libraries need=20 > > > to be compiled in unix and therefore installation is=20 > needed. But in=20 > > > Windows we might be able to distribute them already=20 > compiled. In the=20 > > > case of unix we can at least include them in the package=20 > and provide=20 > > > an installer that install all of them into our external_lib=20 > > > directory. > > > > > > We can have something like /lib/external_lib folder where=20 > we include=20 > > > all this stuff. Do you know what happens if we install a certain=20 > > > version of a library there and the user has already the=20 > same library=20 > > > installed on his python? Which one will take preference? > > > > > > And there is still the open issue of which library to use=20 > for xslt... > > > we are not happy with none of them and they are all difficult to=20 > > > install in mac os x. Any ideas? > > > > > > Cheers. > > > > > > -------------------------------------------------------------- > > > ----------- > > > Take Surveys. Earn Cash. Influence the Future of IT Join=20 > > > SourceForge.net's Techsay panel and you'll get the chance=20 > to share=20 > > > your opinions on IT & business topics through brief=20 > surveys -- and=20 > > > earn cash=20 > > > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge > > &CID=3DDEVDEV > > > _______________________________________________ > > > PyWrapper-devel mailing list > > > PyW...@li... > > > https://lists.sourceforge.net/lists/listinfo/pywrapper-devel > > > > > >=20 > -------------------------------------------------------------- > ----------- > Take Surveys. Earn Cash. Influence the Future of IT Join=20 > SourceForge.net's Techsay panel and you'll get the chance to=20 > share your opinions on IT & business topics through brief=20 > surveys -- and earn cash=20 > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge &CID=3DDEVDEV > _______________________________________________ > PyWrapper-devel mailing list > PyW...@li... > https://lists.sourceforge.net/lists/listinfo/pywrapper-devel >=20 |
