[PyKDE] PyKDE-3.7-4 Release

[Gordon Tyler]

On August 15, 2003 06:56 pm, Jim Bublitz wrote:
> Otherwise it's necessary to modify sys.path first. That means a

Yes, that would be bad.

> I think it makes sense for build.py to search sys.path, but
> anyone smart enough to legitimately locate the modules outside
> of sys.path somewhere should be smart enough to hack build.py
> for their own system's config.  I'm not saying people shouldn't

Yup.

> It looks to me like the way you have python installed, it should
> find /usr/local/lib/python2.2/site-packages automatically
> without -d (as 'platPySiteDir' in build.py). Doesn't it do that?

Nope, my python2.2 is a Debian package installed into /usr which has 
/usr/lib/python2.2/site-packages as it's platPySiteDir but it also has 
/usr/local/lib/python2.2/site-packages in sys.path. I'm using /usr/local for 
sip, pyqt and pykde just for neatness' sake. So, using platPySiteDir won't 
work but searching sys.path should.

> 'initGlobals' - sys.prefix. You can also put all of the options
> in <file> (one per line) and use -z<file>, at least for PyKDE.

I've just got a build.sh for each of sip, pyqt pykde and eric. I learned that 
trick after the third compile or so ;)

> Anyway, I already modified build.py to search sys.path - I think
> that's a good idea regardless. It'll be in the next release - if
> you want a copy sooner I can mail it or post it on sourceforge.

Nope, I've got mine built and I hope I don't have to build it again... it 
takes a while ;)

Thanks,
Gordon