Re: [PyWrapper-devel] Libraries distribution in PyWrapper

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

theres make and ant. ant is newer and more powerful (I think).

the start_server.py script is like the shell script.
we can modify it to accept an optional port to run under, defaulting to =
8080 or so. good idea!

I still dont know how db_modules will work if they depend on the =
installation of the target system.
I hope we dont ned to build python for windows ourselves. thats =
horrible, it needs the commercial MS Visual C++ compiler.
http://uucode.com/texts/python-mingw/python-mingw.html

cherrypy is needed for all webapps!
but you can run it behind mod_python (maybe thats broken now, but you =
should be able to) if you like.

BTW, there a doc about embedding python in your application that I =
havent read:
http://docs.python.org/ext/ext.html

-- Markus
 =20

> -----Urspr=FCngliche Nachricht-----
> Von: pyw...@li...=20
> [mailto:pyw...@li...] Im=20
> Auftrag von Javier privat
> Gesendet: Donnerstag, 3. August 2006 12:38
> An: PyWrapper Developers mailing list
> Betreff: Re: [PyWrapper-devel] Libraries distribution in PyWrapper
>=20
> Ok, in Windows is clear, I think we should provide an=20
> installer that installs everything, python and all libraries.=20
> Aditionally will be nice to have a little interface to start=20
> and stop cherrypy server if they want to use it instead of=20
> their existing server. I like it because people can try=20
> things very fast without having to configure anything.
>=20
> For Mac I would treat it as Linux, it is enough to have to=20
> take care of two things! I was actually thinking on a=20
> configure file that looks for dependencies of the database=20
> modules and where you can pass as arguments the location of=20
> them. Then something like build that compiles python and all=20
> libraries in our own folder, not touching anything of the=20
> host machine. Me as a user I prefer to not have to touch my=20
> python to install pywrapper, I prefer that everything stays=20
> into one single folder that I can send to the trash when I=20
> want to uninstall.
>=20
> And then I would have a script to start cherrypy, like the=20
> start_server.py that we have but that is a shell script and=20
> that I can pass the port where I want the server to run in.
>=20
> Correct me, if I am wrong, will the config tool work outside=20
> of cherrypy?
>=20
> Cheers.
>=20
> PD: What is the difference/advantages of build and ant?
>=20
> On 8/3/06, "D=F6ring, Markus" <m.d...@bg...> wrote:
> > in java for sure. In python its modules. But I saw in=20
> CheeseShop that they call it packages as well. I will rename=20
> it, good choice!
> >
> > -- Markus
> >
> >
> > > -----Urspr=FCngliche Nachricht-----
> > > Von: pyw...@li...
> > > [mailto:pyw...@li...] Im Auftrag=20
> > > von Javier privat
> > > Gesendet: Mittwoch, 2. August 2006 21:56
> > > An: D=F6ring, Markus
> > > Cc: PyWrapper Developers mailing list
> > > Betreff: Re: [PyWrapper-devel] Libraries distribution in PyWrapper
> > >
> > > In other software I have seen calling it "packages"
> > >
> > > Cheer.s
> > >
> > > On 02/08/2006, at 14:40, D=F6ring, Markus wrote:
> > >
> > > > So lets include a new directory called "installer" in=20
> the project.
> > > > If we dont like the name we can change it later, but I cant
> > > think of
> > > > any better right now.
> > > > I will add some of the libs already. But remember to=20
> only use the=20
> > > > source installers, never the comiled stuff.
> > > >
> > > > -- Markus
> > > >
> > > >
> > > >> -----Urspr=FCngliche Nachricht-----
> > > >> Von: pyw...@li...
> > > >> [mailto:pyw...@li...] Im
> > > Auftrag von
> > > >> D=F6ring, Markus
> > > >> Gesendet: Mittwoch, 2. August 2006 14:31
> > > >> An: PyWrapper Developers mailing list; Javier privat
> > > >> Betreff: Re: [PyWrapper-devel] Libraries distribution in=20
> > > >> PyWrapper
> > > >>
> > > >> mx.DateTime alone is also open source.
> > > >> http://www.egenix.com/files/python/mxDateTime.html#Copyright
> > > >>
> > > >> their own kind of license, but I cant see any problem=20
> > > >> distributing
> > > >> it:
> > > >> http://www.egenix.com/files/python/mxLicense.html#Public
> > > >>
> > > >>
> > > >> -- Markus
> > > >>
> > > >>
> > > >>> -----Urspr=FCngliche Nachricht-----
> > > >>> Von: pyw...@li...
> > > >>> [mailto:pyw...@li...] Im
> > > >> Auftrag 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
> > > deploying
> > > >>> 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 be
> > > >> requiring:
> > > >>>
> > > >>> 8) fpconst
> > > >>> 9) SOAPpy
> > > >>> 10) BioMOBY Python
> > > >>>
> > > >>> This is getting a little bit horrible to install. I=20
> think most=20
> > > >>> of these libraries, I think actually all, can be legally
> > > redistributed
> > > >>> 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
> > > >> libraries need to
> > > >>> be compiled in unix and therefore installation is=20
> needed. But in=20
> > > >>> Windows we might be able to distribute them already
> > > >> compiled. In the
> > > >>> case of unix we can at least include them in the package
> > > >> and provide
> > > >>> an installer that install all of them into our external_lib
> > > >> directory.
> > > >>>
> > > >>> We can have something like /lib/external_lib folder where
> > > >> we include
> > > >>> all this stuff. Do you know what happens if we=20
> install a certain=20
> > > >>> version of a library there and the user has already the
> > > >> same library
> > > >>> installed on his python? Which one will take preference?
> > > >>>
> > > >>> And there is still the open issue of which library to use
> > > >> for xslt...
> > > >>> we are not happy with none of them and they are all=20
> 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
> > > to share
> > > >>> your opinions on IT & business topics through brief
> > > surveys -- and
> > > >>> earn cash
> > > >>> =
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
> > > >>>
> > > >>
> > > >> --------------------------------------------------------------
> > > >> -----------
> > > >> 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=20
> brief surveys=20
> > > >> -- 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
> > > >>
> > >
> > >
> > > --------------------------------------------------------------
> > > -----------
> > > 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 share=20
> > your opinions on IT & business topics through brief surveys -- and=20
> > earn cash=20
> >=20
> =
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEV
> > DEV _______________________________________________
> > 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