[python-win32] Re: Found how to use TLBs with py2exe,
jkreps at rev.state.ne.us
jkreps at rev.state.ne.us
Mon Mar 1 09:58:10 EST 2004
pyama at snafu.de
To: jkreps at rev.state.ne.us, python-win32 at python.org
03/01/2004 08:44 cc:
AM Subject: Re: [python-win32] Re: Found how to use TLBs with
>> >>All this properties -in our context- does have VSS also.
>> >>Is CVS also shipped with an COM Automation Library?
>> I use Boa_Constructor as my GUI RAD dev tool, which is built on pxPython
>> and wxWindows widgets and looks and runs the same on either platform.
>> apps made with it runs on either a Windows box or a Linux box, and if
>> is careful about the fonts that are used no code changes are necessary.
>> We are moving away from Microsoft's Common Object Model and dependence
>> Microsoft in general. In Windows I use CVSNT and TortoiseCVS. In
... cut ...
>IMHO we should change to other groups like alt.versioncontrol...
I don't believe I've seen those two newsgroups, ;-) but my IT department
won't let us connect to newsgroups for security reasons. :-(
>The reason why I've postet is, that the VSS TLB seems to be
>something special (*Maybe*. Any kinds of hints are welcome,
>something concerning this problem is even new for me and possibly
>other readers of the group may also learn something new to solve
>problems like this.)
>I've mentioned, the ClearCase TLB works very satisfying on
>WinNT/2k together with Python. I've written some cool tools
>in the past. Myself, I much more would like to work with CC,
>but now, I don't have it.
>The goal is, to help the creator of py2exe makeing py2exe more
>flexible, if -perhaps- other guys use some other funny TLBs.
>Subversion and other VC-Tools may be well, great and fine, but
>their existence don't help us to solve the problem and does not
>increase the power of the already powerfull py2exe tool.
Py2exe is a very neat tool but in certain circumstances it is not helpful.
For example: you have developed an Python based app that connects to an
Oracle backend via ODBC. Using py2exe works well to create a Windows
executable, but the IT department needs to install a user dns on each
workstation and the Oracle admin needs to add each user to the Oracle user
database. So, the only thing saved by using py2exe is not having to
install Python on each workstation. However, when IT sets up a
workstation, or rebuilds it after it corrupts itself, it has to install
several apps anyway (virus scanners, schedulers, QuickTime, Roxio, Network
clients and utilities, etc..., so Python can be just one more. Py2exe is,
however, a very nice way to insure that the user does not have the ability
to edit *.py files by allowing Python NOT to be installed.
More information about the Python-win32