Re: Request Python3.4/python-pyrex back port

[Jakub Wilk <jwilk@debian.org>]

* Gary Preston <gary@mups.co.uk>, 2014-02-24, 23:24:
> I'm looking into the feasibility of a python-lxml3.3.1-1 back port to 
> Wheezy to resolve issues with another back port I'm maintaining 
> (https://packages.debian.org/jessie/python-lxml)
>
> I ran into the following unmet dependencies:
>
> pbuilder-satisfydepends-dummy :
> Depends: python3-all-dev (>= 3.3.3) but it is not going to be installed.
> Depends: python3-all-dbg but it is not going to be installed.
> Depends: python-pyrex (>= 0.9.4.1) but it is not going to be installed.
> Depends: libxml2-dev but it is not going to be installed.
> Depends: libxslt1-dev but it is not going to be installed.
> Depends: python-setuptools but it is not going to be installed.
> Depends: python3-setuptools (>= 0.6.29) but it is not going to be installed.
>
> Is anyone looking into a python3.4 back port or in the process doing 
> a back port?

Very unlikely.


Why do you want python3.4 anyway? lxml upstream supports Python 3.2, 
which is the default version in wheezy.

Now, it is true that you can't rebuild the current source package of 
lxml without source changes in wheezy. This is because it build-depends 
on python3-all-dev (>= 3.3.3), which transitively depends on python3.3 
and python3.4. Why does it need such a new version? The world wonders. 
The change was introduced in 3.3.0~beta2-1, but the changelog only says:

   * New upstream version 3.3.0 beta2.

And what's up with python-pyrex? The version required by lxml's 
Build-Depends is available in wheezy... (And anyway, this 
build-dependency is likely a bug, because lxml hasn't been using Pyrex 
for years.)

--
Jakub Wilk