Re: Upgrading from PackageManager installed PyDS to 0.7.1/CVS

Hi!

> The limtations in picture handling in 0.6.3 annoy me (since I started
> posting smaller pictures, none are showing up in
> <http://njr.pycs.net/pictures/>), and I'm interested to see how the

Hmm. That sounds more like some problem with publishing. Nothing I ever
heard of before, though. You did remember to set the publish state of
your pictures to "yes"? Because if you set it to yes, even if the
imaging stuff breaks, you should at least get the rendered HTML pages.
Any signs of problems in your eventlog?

The PictureTool actually isn't really great. I am not very happy with it
in it's current state and think that some time in the future I will
replace it with a different tool. I have some ideas on this, but not
enough to start hacking.

> speed improvements work; on my desktop Mac (dual G4/533) PyDS is
> pretty slow.

Actually PyDS didn't get faster, but more responsive. 0.6 versions still
have far too much locks in place and lock all access to databases, even
read only access. 0.7 only locks write access and let's read access work
in parallel. This reduces most of the blocking situations.

There still are problems with the aggregator with respect to locking, as
there are far too much write access situations in the aggreagator (for
example the overviews need to write to the database and so consequently
lock the database) that still block the interface from time to time.

> What would be the best way to see what changes you've made to 0.6.3?
> Do you have a patch you apply to the sources, or something similar?

I think Bob sent in a patch some time ago, maybe it's in the list
archive. The main problem I see is that PyDS uses distutils to setup
stuff and so with Python 2.3 on OS X 10.3 you need to patch the setup.py
so packages end up in the right place. The other patch I remember was to
PyDS itself so data files end up in a different path
(~/Library/Application Support/PyDS/ instead of ~/.PyDS/ if I recall
correctly).

A totally different option would be to just do the standard installation
from source stuff - you end up with a unix python installed to /opt/pyds
and all relevant modules in that place. Of course this takes up much
more discspace. The unix python build won't be able to access any of the
cool OS X stuff, though, as you would need a framework build for that.

Anyway you go, data files should be compatible between different
versions and builds of python.

bye, Georg