On Wed, Feb 27, 2013 at 1:28 PM, Paul Moore <p.f.mo...@gmail.com> wrote:
> 27 February 2013 18:24, Paul Moore <p.f.mo...@gmail.com> wrote: > > On 27 February 2013 11:53, Maciej Fijalkowski <fij...@gmail.com> wrote: > >> I think it means you can't use the ABI version and specify the calling > >> convention. It's a reasonable bug report (the calling convention on > >> API version works though) > > > > That would be a deal-breaker for my use case of quick scripts working > > with the Windows API on a machine with no C compiler. I'd have to use > > ctypes in that case until cffi had this feature. > > One other use case for the ABI level over the API level - the ABI > level (no C extension) can be used across Python versions, where the > API level needs a separate compiled extension per Python version. This > can be a big deal on Windows at least, where users (not developers) > with no compilers on their systems are common. > > Is that still true for Windows even with the stable ABI and the dropping of narrow/wide Unicode builds?
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
