Extensions on Windows, questions for experts.

[Chris Liechti]

Michel Van den Bergh <vdbergh at luc.ac.be> wrote in 
news:3C43EA4B.92029F2 at luc.ac.be:
> Hello,
> 
> This is a followup on the recent trend on extensions on Windows.
> 
> The problem is that extensions on Windows depend on the Python
> version. This is because references to pythonxx.dll need to be resolved
> at compile time (through the import library).
> 
> However Windows also has a mechanism for resolving references
> to dll's at runtime (through LoadLibrary and GetProcAddress).
> 
> Has anybody used this to produce Python-version independent
> extensions? The steps one would need to take are:
> 
> (1) Find current version of Python in registry.
> (2) Perform LoadLibrary("pythonxx.dll")
> (3) Resolve reference to functions in the C-extension API through
> GetProcAddress.
[...]

not quite sure if it works for you, but the WinCVS 1.3beta6 has scripting 
support for python.
i have installed it long before 2.2 was out but it detected it and presents 
a python 2.2 prompt. (at home it finds 2.1).

http://www.cvsgui.org/download.html
(important to take the latest 1.3 beta, V1.2 hadn't had py support)

it's gpl so you can browse through their code and find some hints.

HTH chris
-- 
Chris <cliechti at gmx.net>