OK, here are my findings on some tests I just did on an independent Win98
machine, which previously did have neither WinCvs nor Python nor TCL
installed:
a) unsurprisingly, without Python installed no macros will be available at
all.
b) with Python installed, the Python macros all work as could be expected.
The TCL macros will become available but will not work (error message
"_cvsgui.LaunchTclMacro(self.m_file) SystemError: error return without
exception set").
c) with at least one of my Tkinter-enabled macros copied to the Macros
directory, the TCL macros will now all work, with the exception of the
Tk-enabled ones (i.e. "Change CVSRoot (GUI)"), which will throw the error
message, which Bo described in his initial post.
d) with the Python22\DLLs directory renamed to Python22\bin most of the
macros, both Python and TCL ones, do not work at all, although none of them
produce any error message. Judging by disk activity, some of them do appear
to do something, but none produce any output at all.
e) removing/renaming the Tkinter-enabled Python macros reliably returns the
system into state b) (Python22\bin renamed back to Python22\DLLs of course).
I don't want to download and install TCL here at home at the moment, so the
tests with a separately installed TCL will have to wait until monday.
> I am not sure how to check the Python version, I tried propereties on
> the various files in the Python22 directory but nothing shows.
Hmm. When I start up WinCvs, the first line of the console output reads:
Python 2.2.1 (#34, Apr 9 2002, 19:34:33) [MSC 32 bit (Intel)] on win32
You would get a similar output by simply invoking python.exe from a console
prompt.
> I guess I have a flavor of version 2.2 anyway.
Definitely. Otherwise the folder would be named differently. Just make sure
it's not one of the Alpha or Beta builds. Another interesting bit of
information would be whether you're using the ActiveState distribution or
the original from http://www.python.org .
One more thing: Did you try removing the Tkinter-enabled macros? As I said
before, I couldn't imagine how it would be possible for them to cause
anything permanent. If they really were the culprits in this, simply
removing them and restarting WinCvs should reverse the situation. As little
as this would help with your problem, I'd still be happy to hear that
removing them does _not_ have any effect on your issue...
I really hope we could get this one sorted out...
Oliver
------------------------
JID: ogiesen@xxxxxxxxxx
ICQ: 18777742
YIM: ogiesen
|
