mha@sollentuna.net ("Magnus Hagander") writes:
>> I suppose my first (lazy) question is, is there a Python 2.4
>> compatible plpython.dll available anywhere? Alternatively, is
>> there a way I can build one for myself? I'm happy enough
>> doing my own build (I have mingw and msys available), but I'd
>> rather not build the whole of postgresql if possible, just
>> for the sake of one DLL....
>
> Not that I know of. IFF the libraries export the same entrypoints
> without changing things, you could try just copying "python24.dll" to
> "python23.dll". I don't know how the Python guys are with binary
> compatibility, though. Might be worth a shot.
As per my earlier posting, I actually found that building postgresql
wasn't at all hard. Once I'd built with Python 2.4 support, I had a
compatible plpython.dll I could just copy in.
I'm not sure renaming the Python DLL would have worked - it's
definitely frowned on...
> On a different note, can't you have both python 2.3 *and* 2.4 on the
> asme system? Considering they put the version number in the filename, it
> seems this should be possible?
I could, but I try to avoid this, as it involves double installs of
any extensions I want to use, or incompatible environments. More
laziness on my part, really :-)
Thanks for the suggestions,
Paul.
PS Thanks to the developers who made building postgresql on Windows
such an easy job! I was very impressed - I genuinely didn't think
that building such a large piece of software would be so hassle-free.
--
Never keep up with the Joneses. Drag them down to your level. --
Quentin Crisp
