[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Bump SWIG requirements from 1.3.31

From: Arfrever Frehtes Taifersar Arahesis <Arfrever.FTA_at_GMail.Com>
Date: Sun, 1 Mar 2009 01:16:17 +0100

2009-03-01 01:13:20 anatoly techtonik napisaƂ(a):
> On Sat, Feb 28, 2009 at 7:07 PM, Arfrever Frehtes Taifersar Arahesis
> <arfrever.fta_at_gmail.com> wrote:
> >>
> >> A lot of releases happened in SWIG world http://www.swig.org/ since
> >> last update of ./subversion/swig/INSTALL that lists 1.3.31 version as
> >> latest recommended. Are there any good reasons to stick to 1.3.31 when
> >> there is a queue of bugfixes up to 1.3.38 ?
> >
> > Python bindings generated by SWIG 1.3.38 don't work with Python 2.6.
>
> That's bug definitely. In SWIG or in binding definition. I bet SWIG
> 1.3.31 won't work either, because 1.3.31 was released on 2006/11/20
> while Python 2.6 appeared two years later on 01-Oct-2008
>
> Even if bindings are in fact generated - I doubt they are optimized
> for Python 2.6 or will work correctly.

All tests of Python bindings pass with Python 2.6 when these bindings have been
generated by SWIG 1.3.36.

-- 
Arfrever Frehtes Taifersar Arahesis

Received on 2009-03-01 01:18:17 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.