Main Pages
Home
Win32 Extensions
Microsoft .NET
Mozilla
Windows CE
 
Python.org
Python Home
Official Windows Home
Python documentation
Search
 
Starship Windows Links
Roger Burnham
Gordon McMillan/Win32 Installer
Ken Seehof
mxTools/mxDateTime
Bill Wilkinson/MSAccess and Python
 
Other Links
Python and ADO
Paul Boddie's Python COM tutorial
Chris Phoenix's Pythonwin tutorial
win32com script collection
Pythonware/PIL
 
Email me
mhammond@skippinet.com.au

 

PyWin32 Frequently Asked Questions


Please mail Mark with ideas for new items, corrections, etc.

How do I report a bug?

Visit the bug page at sourceforge.  Please include as much information as possible, including a short script that demonstrates the problem and is able to be executed by others (ie, there is no point attaching a script that depends on other modules of yours, on a specific database driver, or even on a hard-coded filename.)  To request a new feature, visit the feature request page at sourceforge.

How do I get help on a problem, or request a new feature?

You should try the mailing list resources available via mail.python.org - specifically, check out python-list for general Python discussions, or python-win32 for a Windows specific mailing list.

How do I use the exposed Win32 functions to do xyz?

In general, the trick is to not consider it a Python/PyWin32 question at all, but to search for documentation or examples of your problem, regardless of the language.  This will generally give you the information you need to perform the same operations using these extensions.  The included documentation will tell you the arguments and return types of the functions so you can easily determine the correct way to "spell" things in Python.

Can multiple builds exist on the same machine?

Multiple major Python builds (1.6, 2.0, etc) and it's associated PyWin32 build should co-exist perfectly on the same machine. The only things to be aware of are:

  • Only one of the 2 versions can be associated automatically with ".py" files. When you double-click on a .py file, it will be run by whatever version of Python you installed last. Similarly for Pythonwin (although its install program allows you to choose if Pythonwin should be set to edit .py files - if you say "no", the previous Pythonwin (or whatever) will remain the default .py editor).
  • Only one of the 2 versions can be used for a single COM server at any given time. The version of Python used to register the COM object is the version that will be used to run the object. It is not possible to have a 1.5 and 1.6 version of the same COM object on your machine at the same time - but you can toggle between which of the 2 versions is currently hosting the object. By association, this also applies to ActiveScripting - you can only have one version of ActiveScripting registered on your machine at one time, not both.
  • One Python version can not use COM objects implemented in another Python version. For example, if you register a Python COM object with Python 2.0, it cannot be used by Python 2.2. You will need to re-register the COM object using the Python version that will be using it.

[Wed Jul 27 08:02:53 2005 GMT+10]