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

Re: svn commit: rev 5943 - in trunk/packages/rpm: redhat-7.x redhat-8.x

From: <kfogel_at_collab.net>
Date: 2003-05-15 23:31:14 CEST

kfogel@collab.net wrote:
> If we decide it's worth it, I can certainly install Python 1.x on my
> system, and make sure to use that for cvs2svn development, while still
> using 2.x for regression tests. It would only be an inconvenience for
> me. But people writing patches to cvs2svn would probably also get bit
> from time to time, adding extra cycles to the patch feedback loop.
> Maybe we should just decide that 2.1 is the minimum Python for
> Subversion? That would certainly simplify things for developers who
> work both on cvs2svn and Subversion itself (& hence the regression
> tests).

Well, Mike P. and I just talked with Greg on the phone about this, and
all felt that Python 2.0 compatibility is enough. Here's why:

   1. Python 2.0 has been out for 3 years or so.

   2. There are RPMs available for RedHat 7.x systems (RH 7.x shipped
      with Python 1.5.2, and that was our main reason for trying to
      stay 1.5.2-compatible, as that's such a big installed base).

   3. The target audience here is people doing repository conversions,
      that is, administrators of one sort or another. If they see a
      clear error message from cvs2svn.py indicating that they need to
      upgrade their Python, and telling them where to get it, they are
      unlikely to be daunted by this.

So assuming no objections, I'll add that Python version check to
cvs2svn.py, just like the one we already have in our regular
regression test suite.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 16 00:15:00 2003

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.