Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #100294 > unrolled thread

Re: wrappers for C/C++

Started byChris Angelico <rosuav@gmail.com>
First post2015-12-12 05:53 +1100
Last post2015-12-12 05:53 +1100
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: wrappers for C/C++ Chris Angelico <rosuav@gmail.com> - 2015-12-12 05:53 +1100

#100294 — Re: wrappers for C/C++

FromChris Angelico <rosuav@gmail.com>
Date2015-12-12 05:53 +1100
SubjectRe: wrappers for C/C++
Message-ID<mailman.156.1449860003.12405.python-list@python.org>
On Sat, Dec 12, 2015 at 5:40 AM, Ginga, Dick <Dick.Ginga@perkinelmer.com> wrote:
> Thank you Chris for this answer.  These are the _only_ versions the build creates. Are you saying that wrappers for 3.5 "may" continue to support future versions?

That's a Windows-specific concern; there've been changes made to how
the Windows build process works, starting with 3.5. It's usually
easiest to build against the exact Python that you want to run
against; in the case of binaries downloaded from python.org, that
basically means having one build for each version (major.minor) you
want to support. (I'm not sure about other build concerns - you
possibly need 32-bit and 64-bit builds for each version. Others will
know more than I do on that.)

For non-Windows platforms, it's usually easiest to punt on the whole
build process and just distribute source code. C compilers are more
generally available on people's Linux systems than on their Windowses.

ChrisA

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web