Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail From: "Ginga, Dick" Newsgroups: comp.lang.python Subject: RE: wrappers for C/C++ Date: Fri, 11 Dec 2015 18:40:24 +0000 Lines: 37 Message-ID: References: <6C6EE445A6F6CE4E8A0FFB51B071A4E2D869B96D@AMERMBX02.PERKINELMER.NET> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Trace: news.uni-berlin.de w9z4JtpK/uANnL0tXK0q2QKnoRaCRFbs1MPkvqKQcseA== Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.004 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'binary': 0.05; 'friday,': 0.07; 'wrapper': 0.07; 'cc:addr:python-list': 0.09; 'c/c++': 0.09; 'inherited': 0.09; 'python': 0.10; '2.7': 0.13; 'message-----': 0.15; '3.2.': 0.16; 'binary.': 0.16; 'creates.': 0.16; 'received:io': 0.16; 'received:psf.io': 0.16; 'skip:[ 60': 0.16; 'wrappers': 0.16; 'wrote:': 0.16; 'project,': 0.18; 'versions': 0.20; '2015': 0.20; 'cc:2**0': 0.20; 'cc:addr:python.org': 0.20; 'saying': 0.22; 'libraries': 0.22; 'noted': 0.22; 'am,': 0.23; 'code.': 0.23; '(or': 0.23; '(you': 0.23; 'dec': 0.23; "python's": 0.23; 'sat,': 0.23; "haven't": 0.24; 'unix': 0.24; 'header:In- Reply-To:1': 0.24; 'chris': 0.26; 'supported': 0.27; 'separate': 0.27; '3.1': 0.29; 'for,': 0.29; "i'm": 0.30; 'subject:/': 0.30; 'url:mailman': 0.30; 'work.': 0.30; 'code': 0.30; 'probably': 0.31; 'december': 0.32; 'posting': 0.32; 'maybe': 0.33; 'source': 0.33; 'url:python': 0.33; 'builds': 0.33; 'skip:- 10': 0.34; 'url:listinfo': 0.34; 'sent:': 0.35; 'could': 0.35; 'cc:': 0.35; 'subject:': 0.35; 'but': 0.36; 'should': 0.36; 'there': 0.36; 'url:org': 0.36; 'possible': 0.36; 'email addr:python.org': 0.36; 'subject:: ': 0.37; 'two': 0.37; 'being': 0.37; '12,': 0.37; 'charset:us-ascii': 0.37; 'version': 0.38; 'building': 0.38; 'thank': 0.38; 'mean': 0.38; 'sure': 0.39; 'from:': 0.39; 'url:mail': 0.40; 'build': 0.40; 'still': 0.40; 'some': 0.40; 'future': 0.60; 'save': 0.60; 'your': 0.60; 'our': 0.64; 'python- list': 0.66; 'email name:python-list': 0.67; 'answer.': 0.72; 'yourself': 0.73; '3.6': 0.84; 'chrisa': 0.84; 'received:67.231': 0.84; 'received:(may be forged)': 0.91 Thread-Topic: wrappers for C/C++ Thread-Index: AdE0OFRZmolwdw5FQYe4N84IoMoa8wAM2cAAAApQdjA= In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [165.88.255.167] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2015-12-11_11:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 kscore.is_bulkscore=0 kscore.compositescore=1 compositescore=0.9 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 kscore.is_spamscore=0 rbsscore=0.9 spamscore=0 urlsuspectscore=0.9 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1507310007 definitions=main-1512110332 X-Mailman-Approved-At: Fri, 11 Dec 2015 15:27:50 -0500 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.20+ Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com comp.lang.python:100302 Thank you Chris for this answer. These are the _only_ versions the build c= reates. Are you saying that wrappers for 3.5 "may" continue to support futu= re versions? -----Original Message----- From: Python-list [mailto:python-list-bounces+dick.ginga=3Dperkinelmer.com@= python.org] On Behalf Of Chris Angelico Sent: Friday, December 11, 2015 1:29 PM Cc: python-list@python.org Subject: Re: wrappers for C/C++ On Sat, Dec 12, 2015 at 4:21 AM, Ginga, Dick w= rote: > I have inherited a product build that uses SWIG to product wrapper librar= ies for our C/C++ code. It currently builds these wrappers for 2.5, 2.6, 3.= 1 and 3.2. > > Is it necessary to have version specific wrappers? Yes, it is, because of the way Python's internals work. But you can probabl= y build them all from the same source code. I'm not sure whether you mean that those four are the _only_ versions it's = building for, or if you noted them as being particularly old versions still= being built for. Either way, you should be in full control of your version= support; if this is an internal project, you could simply stipulate that o= nly one version of Python is supported (or maybe two - 2.7 and one 3.x), an= d save yourself some build hassles. If you're posting it on PyPI, you can p= ut the source code out there and let Unix users build their own, and then y= ou need only worry about Windows; I haven't seen confirmation yet (as there= 's no official 3.6 builds), but supporting "3.5+" should be possible from a single binary.= (You would still need a separate binary for 2.7, though.) ChrisA -- https://mail.python.org/mailman/listinfo/python-list