Bug#430847: Please rebuild so that python-subversion bindings with work with python-2.5)

[Peter Samuelson]

[Bill Gribble]
> All I know is, python-subversion is one of the few remaining major
> python packages that don't include support for python-2.5.  

With python module packages, the python policy allows maintainers to
make a decision whether to support only the default python version
(currently 2.4) or to support multiple python versions.  Now, most
module packages can be built for multiple python versions quite easily;
but for python-subversion, the process would be much more involved,
since the 'configure' process that configures the module also
configures the whole rest of Subversion, and the modules are built on
Subversion's C libraries.  Switching things around to configure and
build the python modules more than once, but only build the rest of
Subversion once, but still be able to run the _testsuite_ for each
version of the python modules, using the C libraries which were only
built once ... well, I decided that that was a lot of complexity for
very little gain.  I believe most potential users of python-subversion
(and note, this doesn't include users of the third-party 'python-svn'
bindings) want to use it with Debian's default python version anyway.

Ubuntu patched our package to support multiple python versions, but
their patch is ugly and intrusive, so I didn't really want to merge it
back to Debian without a good reason.  And I haven't heard anyone
clamoring for this feature until you mentioned it just now.  And given
that Debian will soon transition to python 2.5 anyway....

Thanks,
Peter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-subversion-maintainers/attachments/20070627/b79a6713/attachment.pgp