[Bug-gnubg] Win distribs - PythonLib stuff

[Massimiliano Maini]

Hi all,

up to now I was shipping in the windows installers a subset
of the Phyton library in order to allow gnubg users to use
the python interface without having to install python.

Now I'm realising that this is a mess: I have to select
what's necessary and what's not (e.g. module os and sqlite3
yes, others no), check dependencies and put the required
files in.

I guess it's just simpler and safer to require the users to
install python whenever they want to use the feature.

I see only a couple of issues:

- for Python2.5, I still have to provide the python25.dll
in my installer, since it's a special mingw one. using Python
25 default dll crashes. No big deal and sooner or later I'll
take the time to move to python 2.6 (which is mingw friendly).

- if I provide gnubg exes with python and the user hasn't got
python installed, starting the CLI they will get this:

  'import site' failed; use -v for traceback
  Traceback (most recent call last):
    File "gnubg.py", line 52, in <module>
      import os.path
  ImportError: No module named os.path

I don't know if we can do someting about the "import site"
warning, probably not. Would be nice to get rid of it.

For the other error, it's because of some code that is in
gnubg.py, itself loaded by PythonInitialise (in gnubgmodule.c).

As far as I can see, the code in gnubg.py is for example
purposes only, so it wold be good to move it to a separate
file (not loaded at startup).

So the questions are (for anyone with better python knowledge):

- OK if I stop providing pythonlib file sin the win installer
(and hence require users to install python, if they want to use
the feature) ?

- Anything we can do abut the "import site" warning ?

- Anything we can do about gnubg.py ?

MaX.