[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: PEP 453 affects Debian packaging of Python packages



[Thomas Kluyver, 2013-09-18]
> From a developer point of view: this leaves you dependent on other people
> to get the latest release of your software to users, which can be very
> frustrating. For instance, I'm a developer for IPython: we made a 1.0
> release over a month ago, and there's already been a 1.1 release since
> then, but Debian unstable still doesn't have either of these. This is not
> to criticise our packager, who we have a good relationship with, but simply
> to point out that this system is beyond our control. If we recommend that
> people use apt/yum/port/whatever to install IPython, they'll get an old
> package, with bugs that we've already fixed. By contrast, we update the
> packages on PyPI at release time, so users installing with pip will always
> get the current version.

I understand your point and I'm not saying PyPI is something bad,
I just wish these tools use their own namespace and leave system files
alone.
-- 
Piotr Ożarowski                         Debian GNU/Linux Developer
www.ozarowski.pl          www.griffith.cc           www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645

Attachment: signature.asc
Description: Digital signature


Reply to: