[PythonWin] VSS fix/workaround for database in non-standard locat ion

[Mike Fletcher]

Upgraded to build 128 today, realized that my SourceSafe integration was no
longer functional.  System kept complaining that the database did not exist.
On reading source of vss.py, discovered that it allows for a database =
"inifilename" key in the scc file, but that it ignores the value. I altered
vss.py to use the value, added the database key to the INI file, and was
able to continue working.

Background info: I do not use the default database location for visual
SourceSafe, which has in the past messed up vss.py (I don't actually recall
the fix  in that case (one of the reasons I'm posting)).

In case someone else needs it, find attached.
Enjoy all,
Mike

-------------- next part --------------
A non-text attachment was scrubbed...
Name: vss.py
Type: application/octet-stream
Size: 3092 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-list/attachments/20000427/773930ce/attachment.obj>