Mark
Started again from the top by first downloading the pywin32 tarball to a
Windows 7/8 64-bit machine with Python 2.7.4 64-bit installed system-wide.
The MS SDK v7.0 has been installed and initiated for 64-bit compiler
support. No virtualenv during this phase. The following is the output
This has also been discussed in the GUID thread, but I am bringing it back
to this one...
I have basically completed the work of breaking adodbapi up into a package
of smaller modules. It has really helped to make the code more readable.
There is now a remote module, so that a programmer (on
Dinesh:
Unless you plan on modifying the C language code of pywin32, or need to
add C language routines of your own, there is absolutely no advantage in
building pywin32 from source. In almost all cases you are better off
downloading the pre-built installers.
(( If you ARE one of those rare C
My apologies for publishing misinformation: Pyro4 does not *require*
Python 2.6, it simply does not go out of it's way to support 2.5. In fact,
it does work. I have discovered that the 2.6 dependencies were in my own
code for the server and remote modules fixed them. I had to write a main
Can't you just download and install the pre-built binaries? If you do
need to build from sources, I suspect the missing header is in the
platform SDK...
Mark
On 25/04/2013 7:59 PM, Dinesh B Vadhia wrote:
Mark
Started again from the top by first downloading the pywin32 tarball to a
Windows
