Path: g2news1.google.com!news3.google.com!news4.google.com!feeder.news-service.com!feeder.visyn.net!visyn.net!aioe.org!bofh.it!news.nic.it!robomod
From: Barry Warsaw <ba...@canonical.com>
Newsgroups: linux.debian.maint.python
Subject: Re: Is it worth back porting PEP 3147 to Python < 3.2?
Date: Tue, 20 Apr 2010 22:00:01 +0200
Message-ID: <eBrLX-6IH-7@gated-at.bofh.it>
References: <eB7ke-4U3-3@gated-at.bofh.it> <eBcMW-5C8-13@gated-at.bofh.it> <eBgQx-4yl-5@gated-at.bofh.it>
X-Original-To: Piotr =?utf-8?B?T8W8YXJvd3NraQ==?= <pi...@debian.org>
Old-Return-Path: <ba...@canonical.com>
X-Amavis-Spam-Status: No, score=-7 tagged_above=-10000 required=5.3
	tests=[BAYES_00=-2, PGPSIGNATURE=-5] autolearn=ham
X-Policyd-Weight: using cached result; rate: -5
X-Mailer: Claws Mail 3.7.4 (GTK+ 2.20.0; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA256;
 boundary="Sig_/ac7OC./Z0GiEfcXy0pouM9="; protocol="application/pgp-signature"
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/6668
List-ID: <debian-python.lists.debian.org>
Approved: robo...@news.nic.it
Lines: 75
Organization: linux.* mail to news gateway
Sender: robo...@news.nic.it
X-Original-Cc: debian-pyt...@lists.debian.org, ubuntu-de...@lists.ubuntu.com
X-Original-Date: Tue, 20 Apr 2010 15:50:17 -0400
X-Original-Message-ID: <20100420155017.6e336f97@heresy>
X-Original-References: <20100419175305.6e6ab5d5@heresy>
	<1271735426.4405.10.ca...@c2.home.zak.co.il>
	<20100420081453.GN6...@piotro.eu>

--Sig_/ac7OC./Z0GiEfcXy0pouM9=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Apr 20, 2010, at 10:14 AM, Piotr O=C5=BCarowski wrote:

>[Omer Zak, 2010-04-20]
>> My take of the situation:
>> Yes, please backport PEP 3147 to at least Python 2.7.
>> The rationale: we'll need to support both Python 2.x and Python 3.x for
>> several years, and it will be nice if the same library package can be
>> made to support both 2.x and 3.x.
>
>you cannot (in most cases) share 2.X and 3.X Python code, so adding it
>to 2.7 and not to 2.6 doesn't make sense

Just thinking out loud: How insane would it be to think of an import hook t=
hat
could do it at run time?  Or, a compilall switch that would do it when the =
pyc
file was generated?  You'd need some way to specify that a particular module
could/should not be auto-converted, or conversely if automatic support were
more the exception, some way to say it can be done.  I wonder if something =
in
the debian/[control|rules] file could trigger that.

>I doubt we'll touch 2.X packages in Debian Squeeze and in Squeeze+1
>we'll most probably have only 1 Python 2.X version (if any) so I don't
>see a point in backporting it in Debian.

Good to know, thanks.

>If you want to ship two 2.X Python versions in Ubuntu, you could use my
>new dh_python for that (I hope to finish it soon), but you'd have to
>convert *all* packages to it and lets face it, python2.5 and python2.6
>transitions in Ubuntu (at least in universe) were...  well not even
>close to Debian's quality and these transitions didn't require that much
>work...

Sorry, I don't really know the history of any of that so I can't comment.  =
But
I would like to know more about your new dh_python, what changes it would
require, etc.  Where can I find it, or information about it?

-Barry

--Sig_/ac7OC./Z0GiEfcXy0pouM9=
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJLzgV5AAoJEBJutWOnSwa/aLYP/jIvRcBmfjldlVwSnpMsWvJT
w3f9Fd0QQQY0DvttxSXRA+d+0ff0wBLU+3EWZSBmp5xCoN6Rn67A7FGR2N0CeG5X
BITE8xdusWKjXc4jYNnDjuknLqFIMI/VOLjhKilBQVWk6icgR6uVTuJmPF0954hj
9uRwtS1DnYkjAb/ucFCFbpNtv1P9UjTn2EK3jrC1a/pD0+86RLrFWrx4jHvXDWcQ
fWr7Zw9IV2rOnKv/ay5HhtGlhY2k1spZ7NX4I8vMzonKSfp7ANKMCQyWnVPnTbSx
cXse5WLPdUriSTGYRvxE0k3dAQ7++fpnRFiyEnzlnqeGDOoc2xhElPv54yhvDf5P
hDLkaNuciHxW8r4+g5vqpB1a2BGHiJsYXwC1qht2trQ3YG4lr61hg/1IbMoRwJa0
DOD3x8MJyekMVociPyB4iXfT7VyvDFbI2ZutiHcbws1GpWe9dcGq7q8lQeukU9+r
JV1+QP5cgAEl2+AIqJF2objAOFyCU6Q55LQg7+exvihg/6cczWDm0bFxG6+SY08w
cy9ZvyuL12lBasmxyhTwav3O+dqOv6R/Qchee3phk6ssZb/uO15p0Nk8mIYNCrNH
QQgJ47PSE1fwrBcmxu7hLkzxv1KQuQhZm3pzqXCVECmPDX78WpA5GuNnVfUAffGS
3mQS/Ta3xZ3t9KZ2aorl
=Trgd
-----END PGP SIGNATURE-----

--Sig_/ac7OC./Z0GiEfcXy0pouM9=--


-- 
To UNSUBSCRIBE, email to debian-python-REQU...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100420155017.6e336f97@heresy