Re: [PyWrapper-devel] Libraries distribution in PyWrapper

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

Ok, in Windows is clear, I think we should provide an installer that
installs everything, python and all libraries. Aditionally will be
nice to have a little interface to start and stop cherrypy server if
they want to use it instead of their existing server. I like it
because people can try things very fast without having to configure
anything.

For Mac I would treat it as Linux, it is enough to have to take care
of two things! I was actually thinking on a configure file that looks
for dependencies of the database modules and where you can pass as
arguments the location of them. Then something like build that
compiles python and all libraries in our own folder, not touching
anything of the host machine. Me as a user I prefer to not have to
touch my python to install pywrapper, I prefer that everything stays
into one single folder that I can send to the trash when I want to
uninstall.

And then I would have a script to start cherrypy, like the
start_server.py that we have but that is a shell script and that I can
pass the port where I want the server to run in.

Correct me, if I am wrong, will the config tool work outside of cherrypy?

Cheers.

PD: What is the difference/advantages of build and ant?

On 8/3/06, "D=F6ring, Markus" <m.d...@bg...> wrote:
> in java for sure. In python its modules. But I saw in CheeseShop that the=
y call it packages as well. I will rename it, good choice!
>
> -- Markus
>
>
> > -----Urspr=FCngliche Nachricht-----
> > Von: pyw...@li...
> > [mailto:pyw...@li...] Im
> > Auftrag 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 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 only use the
> > > 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 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 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 think most of
> > >>> these libraries, I think actually all, can be legally
> > redistributed
> > >>> with other software so I was wondering if we could not embed
> > >>> everything into PyWrapper.
> > >>>
> > >>> Well, I know there are some problems. Some of these
> > >> libraries need to
> > >>> be compiled in unix and therefore installation is needed. But in
> > >>> 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 install a certain
> > >>> 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 difficult to
> > >>> install in mac os x. Any ideas?
> > >>>
> > >>> Cheers.
> > >>>
> > >>> --------------------------------------------------------------
> > >>> -----------
> > >>> Take Surveys. Earn Cash. Influence the Future of IT Join
> > >>> 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
> > >> 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
> > 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 SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> PyWrapper-devel mailing list
> PyW...@li...
> https://lists.sourceforge.net/lists/listinfo/pywrapper-devel
>