Showing content from http://mail.python.org/pipermail/python-dev/attachments/20150409/94a93c19/attachment-0001.html below:
<div dir="ltr">Sorry if i'm pushy....<div>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 ?)</div><div>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 unfamiliar with licensing terms).</div><div><br></div><div>Regards,</div><div>Cristi Fati.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 8, 2015 at 3:49 PM, Cristi Fati <span dir="ltr"><<a href="mailto:cristifati0@gmail.com" target="_blank">cristifati0@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>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).</div><div><br></div><div>a much simpler example:</div><div><br></div><div>Python 2.7.3 (default, Oct 22 2014, 12:21:16) [MSC v.1600 64 bit (Itanium)] on win32</div><div>Type "help", "copyright", "credits" or "license" for more information.</div><div>>>> import ctypes</div><div>>>> ctypes.cdll.kernel32.GetTickCount()</div><div>-79897956</div><div>>>></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 8, 2015 at 3:17 PM, Maciej Fijalkowski <span dir="ltr"><<a href="mailto:fijall@gmail.com" target="_blank">fijall@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">for the record libffi supports itanium officially (but as usual I'm<br>
very skeptical how well it works on less used platforms)<br>
<a href="https://sourceware.org/libffi/" target="_blank">https://sourceware.org/libffi/</a><br>
<div><div><br>
On Wed, Apr 8, 2015 at 1:32 PM, Nick Coghlan <<a href="mailto:ncoghlan@gmail.com" target="_blank">ncoghlan@gmail.com</a>> wrote:<br>
> On 8 April 2015 at 20:36, Maciej Fijalkowski <<a href="mailto:fijall@gmail.com" target="_blank">fijall@gmail.com</a>> wrote:<br>
>> I presume the reason was that noone wants to maintain code for the<br>
>> case where there are no buildbots available and there is no<br>
>> development time available. You are free to put back in the files and<br>
>> see if they work (they might not), but such things are usually removed<br>
>> if they're a maintenance burden. I would be happy to assist you with<br>
>> finding someone willing to do commercial maintenance of ctypes for<br>
>> itanium, but asking python devs to do it for free is a bit too much.<br>
><br>
> As a point of reference, even Red Hat dropped Itanium support for<br>
> RHEL6+ - you have to go all the way back to RHEL5 to find a version we<br>
> still support running on Itanium.<br>
><br>
> For most of CPython, keeping it running on arbitrary architectures<br>
> often isn't too difficult, as libc abstracts away a lot of the<br>
> hardware details. libffi (and hence ctypes) are notable exceptions to<br>
> that :)<br>
><br>
> Cheers,<br>
> Nick.<br>
><br>
> --<br>
> Nick Coghlan  |  <a href="mailto:ncoghlan@gmail.com" target="_blank">ncoghlan@gmail.com</a>  |  Brisbane, Australia<br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4