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

Re: svn.collab.net scheduled maintenance downtime

From: Greg Stein <gstein_at_gmail.com>
Date: Tue, 24 Feb 2009 18:22:24 +0100

On Tue, Feb 24, 2009 at 18:17, Mark Phippard <markphip_at_gmail.com> wrote:
> On Tue, Feb 24, 2009 at 12:13 PM, Greg Stein <gstein_at_gmail.com> wrote:
>> On Tue, Feb 24, 2009 at 18:06, Mark Phippard <markphip_at_gmail.com> wrote:
>>> On Sat, Feb 21, 2009 at 8:27 PM, Greg Stein <gstein_at_gmail.com> wrote:
>>>> Some of the commit-hook scripts now require Python 2.4. It isn't
>>>> needed for end-user building from tarballs. Just for some of the
>>>> auxilliary tools that we ship.
>>>> Core svn doesn't need python at all, tho it does need sqlite 3.4 or newer.
>>> We have confirmed that you CANNOT build SVN bindings with Python >
>>> 2.4.  Here is quote from my build engineer:
>> Later than 2.4? Or versions prior?
> Sorry, I mean Python 2.2.
>> *Core svn* doesn't need Python. If you want to build Python bindings,
>> then yah... you're gonna need Python. As far as the *version* of
>> Python... different question. And it looks like the general answer is
>> "you need Python 2.4 or later."
> Yes, we can build core fine.  I am talking about the Python bindings.
> We currently support ViewVC on RHEL and of course people want to write
> hooks etc. and need bindings.

"Three options: run subversion 1.6; upgrade your Python; upgrade your OS."


>> Did you get your greater/lesser symbol mixed up, above? It is
>> *expected* that we're now generally requiring Python 2.4 or later. I
>> hadn't thought about the bindings, but it appears they need 2.4 or
>> later, too.
> I'd like to be able to support RHEL 4, if not RHEL 3, with the bindings.

Dunno what to say other than have somebody dig into the bindings to
make them work with Python 2.2.

Personally, I would prefer that our dev-build-time and test suite
require Python 2.4 or later. As devs, we should have access to that
very easily, and we shouldn't be wasting our time with tweaking
support for different Python versions.

For the runtime stuff (scripts, tools, and bindings): I think we
can/should support any version that people want to expend effort on.


Received on 2009-02-24 18:22:42 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.