Re: PEP 453 affects Debian packaging of Python packages
Paul Tagliamonte <paultag@debian.org> wrote:
>On Wed, Sep 18, 2013 at 10:57:30PM +0200, Tshepang Lekhonkhobe wrote:
>> On Wed, Sep 18, 2013 at 3:36 PM, Paul Tagliamonte
><paultag@debian.org> wrote:
>> > 4) Python modules from dpkg are borderline useless for
>developers. We
>> > package modules so that apps can use them, not so that people
>can
>> > develop with them.
>>
>> Are they 'borderline useless' because they are normally much older
>> than upstream? I think most development work has no need for
>> latest-and-greatest.
>
>Well, sorta. The problem here is different major versions have
>different
>APIs. If I have to maintain my eons old Django 1.2 app on the same
>machine as a 1.4 app, I don't want to keep uninstalling and
>reinstalling
>packages. It's silly.
Sure. It'd be nice if upstreams cared more about API stability. In my experience it's not generally very difficult if developers pay attention to it.
>I wish we shipped wheel files so we can trust the pip installs, but
>meh.
>It seems like this, also, isn't something folks here care about for
>some
>reason.
>
>What's more, it's helpful to have a development env that can match the
>env that I test stuff in tox with.
It shows my background, but when I need older versions of things I fire up a chroot and work in that. I often do that even for the same distro release I'm running to keep things separated. It's quite possible to deal with multiple versions using Debian tools.
Scott K
Reply to: