You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Brian Munroe <br...@gmail.com> on 2007/08/23 17:17:39 UTC
Anyone using SWIG 1.3.31 + Python 2.5 with Python bindings?
While compiling Subversion 1.4.4, I noticed a warning that Subversion
is known to work with SWIG 1.3.24 - .29. I am using Python 2.5.1 and
anything less then SWIG 1.3.30 won't work with it.
Has anyone blatantly ignored the subversion warnings and run this
configuration in production?
thanks!
-- brian
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Anyone using SWIG 1.3.31 + Python 2.5 with Python bindings?
Posted by Brian Munroe <br...@gmail.com>.
On 8/23/07, Olivier Delannoy <ol...@gmail.com> wrote:
> I have been using this version of swig and python 2.5 with no problem.
> I experience some random error with trac / svn / mod_python but I
> can't identify this problem as something related to svn binding.
>
> I hope it helps
>
Oliver:
Trac is one of the reasons I am setting up the Python bindings, I have
already started down the 1.3.31 and 2.5 path, so I glad that I am not
alone!
thanks
-- brian
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Anyone using SWIG 1.3.31 + Python 2.5 with Python bindings?
Posted by Brian Munroe <br...@gmail.com>.
On 8/23/07, Rainer Sokoll <R....@intershop.de> wrote:
>
> Not sure if I got you right, but I have svn 1.4.4 with swig 1.3.29
> running in production.
>
Hi Rainer:
I was asking if anyone was using SWIG 1.3.31 with the SVN Python
bindings. During the ./configure, Subversion emits a warning that it
has been known to work with 1.3.24 - 1.3.29 (see below for more
details).
I am hoping to use Python 2.5.1 but SWIG 1.3.29 does not seem to work
with that version, as it fails during 'make check'. According to the
internet, 1.3.29 and earlier have some problems with the Py_ssize_t
changes in Python 2.5.
I am heading down the path of empirically testing this configuration
(Python 2.5, SWIG 1.3.31 and SVN 1.4.4) myself, but was wondering if
anyone could confirm whether I am wasting my time or not.
-- brian
Output from ./configure with '--with-swig=/usr/local/swig-1.3.31'
checking swig version... 1.3.31
configure: WARNING: Detected SWIG version 1.3.31
configure: WARNING: Subversion requires 1.3.24 or later, and is known to work
configure: WARNING: with versions up to 1.3.29
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Anyone using SWIG 1.3.31 + Python 2.5 with Python bindings?
Posted by Rainer Sokoll <R....@intershop.de>.
On Thu, Aug 23, 2007 at 10:17:39AM -0700, Brian Munroe wrote:
> While compiling Subversion 1.4.4, I noticed a warning that Subversion
> is known to work with SWIG 1.3.24 - .29. I am using Python 2.5.1 and
> anything less then SWIG 1.3.30 won't work with it.
>
> Has anyone blatantly ignored the subversion warnings and run this
> configuration in production?
Not sure if I got you right, but I have svn 1.4.4 with swig 1.3.29
running in production.
BTW: You can pass an alternative swig installation to subversion's
configure.
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org