Re: Local Python (2.3.3)?

Hi!

> I'm installing your PyDS on my SuSE 8.2. I've already local copies of=20
> Python (2.3.3 and 2.2.2). SuSE also offers Medusa 0.5.1 and PyXML. I=20
> guess, I can use all these (Python 2.3.3?).

The problem is that PyDS isn't officially "released" for Python 2.3,
yet. It's still Python 2.2 on all my systems, so I can't test with
Python 2.3 and can't guarantee that it works. I do know that people use
PyDS with Python 2.3 (the Mac OS X people using Bobs package installers
for example), but I do know of at least one user who had problems with
the aggregator (or actually with the downstreaming - the download
mechanism built into PyDS) under Python 2.3. So you might find weird
problems where I can't help much.

Another problem would be that you need to use Metakit from CVS, as only
that version works with Python 2.3. Other versions had a different
installation mechanism (the CVS of Metakit uses the distutils stuff)
that didn't work with Python 2.3.

So if you want to be sure, just follow the steps from
INSTALL-FROM-SOURCE and you will get a python 2.2 with all tools
installed that should work fine. It won't get in the way with other
python stuff, as it sits solely in the /opt/pyds/ path. You can change
that to /pyds, but you need to give that as prefix in two installation
steps as prefix - all other tools that use setup.py will automatically
be installed into your place if you run them with your /pyds/bin/ copy
of python.

> Do I need a symbolic link to the "application-private directory"=20
> /opt/pyds/bin/python - or rather ~/pyds/bin/python, where I would
prefer=20
> to hold the stuff?

No, if you use a preinstalled Python, you just use that python to do the
setup.py stuff. So you completely ignore the /opt/pyds stuff and all
packages will install into their usual places under /usr/lib/pythonX.X

> T=FCss from L=E6s=F8, Denmark

Any chance you are going to do a danish translation? :-)

bye, Georg