Sorry if i'm pushy
Would it worth me to send a patch with the changes? (i mean, would it bring
value to the product? were there requests for ctypes on WinIA64 ?)
If the answer to the above question is not No, since the changes are in
libffi should i send patches to you or libffi guys? (i'm
On 8 April 2015 at 20:36, Maciej Fijalkowski fij...@gmail.com wrote:
I presume the reason was that noone wants to maintain code for the
case where there are no buildbots available and there is no
development time available. You are free to put back in the files and
see if they work (they might
I presume the reason was that noone wants to maintain code for the
case where there are no buildbots available and there is no
development time available. You are free to put back in the files and
see if they work (they might not), but such things are usually removed
if they're a maintenance
for the record libffi supports itanium officially (but as usual I'm
very skeptical how well it works on less used platforms)
https://sourceware.org/libffi/
On Wed, Apr 8, 2015 at 1:32 PM, Nick Coghlan ncogh...@gmail.com wrote:
On 8 April 2015 at 20:36, Maciej Fijalkowski fij...@gmail.com wrote:
Hi all, thank you for your responses. Apparently i was wrong in my previous
email, ctypes (1.0.1 or 1.0.2) didn't have support for WinIA64 (libffi),
there was an in-house implementation. However we are using the IA64 module
extensively (including to successfully call LsaLogonUser).
a much simpler
Hi all,
Not sure whether you got this question, or this is the right distribution
list:
Intel has deprecated Itanium architecture, and Windows also deprecated its
versions(currently 2003 and 2008) that run on IA64.
However Python (2.7.3) is compilable on Windows IA64, but ctypes module
(1.1.0)
