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

Re: svn commit: r12717 - in trunk: . build/ac-macros build/generatorsubversion/bindings/swigsubversion/bindings/swig/perl/libsvn_swig_perlsubversion/bindings/swig/perl/native subversion/bindings/sw

From: Max Bowsher <maxb_at_ukf.net>
Date: 2005-01-15 22:42:58 CET

David Summers wrote:
> On Fri, 14 Jan 2005, Justin Erenkrantz wrote:
>> --On Friday, January 14, 2005 6:33 PM +0000 Philip Martin
>> <philip@codematters.co.uk> wrote:
>>> It appears that SWIG 1.3.24 is not compatible with Python2.1, I get a
>>> runtime error:
>> IIRC, we were previously ensuring that Python 1.5 worked with the SWIG
>> bindings. Do we mean to bump everyone up to Python 2.2 as well? --
>> justin
> Note: If this were to happen it would leave the RedHat 7.3 users
> behind without upgrading the python packages which are normally deeply
> intertwined with other packages. RedHat 7.3 uses python 1.5.2.

The bindings have been requiring 2.0 since before I joined the Subversion

Our testsuite requires 2.0.

Our INSTALL file documents that we require 2.0 to build from a svn checkout.
(Although, we do try to keep the build generator working with 1.5.2, but
haven't formally documented that we guarantee this).

http://www.swig.org/compat.html claims that it supports all the way back to
1.5, and there is no mention of dropped support in the SWIG changes, so if
SWIG 1.3.24 has really has inadvertently bound itself to 2.2+, then I
imagine the SWIG developers would like to know.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 15 22:50:46 2005

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.