[PATCH STABLE] windows: make win32 mandatory (issue1922)

Adrian Buehlmann adrian at cadifra.com
Fri Feb 4 12:01:05 CST 2011


On 2011-01-22 22:53, Adrian Buehlmann wrote:
> On 2011-01-22 20:06, Patrick Mézard wrote:
>> Le 20/01/11 20:04, Adrian Buehlmann a écrit :
>>> On 2011-01-20 19:59, Aaron Cohen wrote:
>>>> Would using ctypes directly help?
>>>
>>> Yeah. ctypes are cool. But they require python 2.5.
>>
>> Still, requiring python 2.5 on Windows might not be such a big deal considering the advantages it might bring:
>> - It's standard
>> - In theory, with some work, it may replace pywin32 completely. I don't know if there are any issues with 32bits vs 64 bits OS.
>> - Who knows, it may improve the situation with pure module
> 
> I was thinking the same about replacing pywin32, but:
> 
> - How mature is this ctypes thing?
> - Is it used? = Does it work as expected? (in my experience,
>   things which are not used by lots of people tend to have more
>   bugs)
> - What about speed? Isn't there a lot of forth and back
>   going on between the types inside the dll's and the
>   Python objects?
> 
> I must say though I have absolutely no experience with ctypes,
> so this might be pure FUD and ctypes are just fine.

Just spotted these two examples:

http://bugs.python.org/issue9266 - 
  (ctypes "ValueError: NULL pointer access" on Win7 x64)

http://bugs.python.org/issue11048 -
  ("import ctypes" causes segfault on read-only filesystem)

Hmmm.


More information about the Mercurial-devel mailing list