On 11/11/13 08:51, Mark Hammond wrote:
On 11/11/2013 10:23 AM, Christian Tismer wrote:
Hi Mark,
Yes, I understand very well, knowing the patching dance so much more
than I'd like to...
In fact, 'win32/lib' is a folder, actually the only one which is not
also a
package, and exactly this one d
On 11/11/2013 10:23 AM, Christian Tismer wrote:
Hi Mark,
Yes, I understand very well, knowing the patching dance so much more
than I'd like to...
In fact, 'win32/lib' is a folder, actually the only one which is not also a
package, and exactly this one does not show up in the install logs.
I ha
Hi Mark,
Yes, I understand very well, knowing the patching dance so much more
than I'd like to...
In fact, 'win32/lib' is a folder, actually the only one which is not also a
package, and exactly this one does not show up in the install logs.
I have the impression that setuptools changed policy
Hi Christian,
I'm a little reluctant to apply this patch as it stands - we rely on
setuptools doing the right thing for *all* "library" modules - eg, if we
need win32/lib/*.py, we presumably would need all other .py files not
listed here - eg, the entire win32com package, etc.
However, if y
Hi Mark and friends,
for a customer, I had to build pywin32 with VS2010, and when it finally
worked after some changes from https://wiki.python.org/moin/VS2010,
I still could not run
import win32con
I tried to find out why, to no success. I examined some older
installation logs
on my mach
