Brian May writes:
> I just noticed that Ubuntu plan to drop Python 2.7 completely - from
> default installs at least
That's a pretty important modifier!
Ubuntu does not yet plan to drop Python 2.7 completely. Rather, the
current plan is to ensure no *dependencies on* Python 2.7 in the default
On Apr 04, 2017, at 09:49 AM, Brian May wrote:
> I just noticed that Ubuntu plan to drop Python 2.7 completely - from
>default installs at least - for the 18.04 release:
That's not the same as dropping Python 2.7 from the archive, which we're no
where near close to doing.
It's really just an ex
On 2017-04-04 08:21, Brian May wrote:
> I would suggest that Buster have Python 2.7, however we only support 3rd
> party libraries where it is practical to do so. Any library that has
> dropped Python 2.7 support upstream, is not practical for us to support
> in Python2. Anything that depends on s
Brian May writes:
> It is perhaps worth noting that Django 2.0 is due to be released in
> December:
>
> https://www.djangoproject.com/weblog/2015/jun/25/roadmap/
Yes. More directly, Django 1.11 is planned to be the final
Python-2-compatible release. From the above URL:
As a final heads up,
Vincent Bernat writes:
> On the current subject, I also agree we should not drop prematurely
> packages targeted to Python 2. It is likely the support will be extended
> past 2020, at least by distributions with a 10-year support.
RHEL 7 will be supported until 2024.
https://en.wikipedia.org/wik
Barry Warsaw writes:
> For libraries that already support 2 and 3, I don't think we necessarily need
> to actively drop Python 2 yet. We have great tools, so it's usually just as
> easy to continue supporting both. I'm on the fence for new library packages,
> but I suppose if it's also just as
On Apr 01, 2017, at 05:12 PM, Ghislain Vaillant wrote:
>Pasting the relevant quotes below:
>
>"The 2.x series of Python is due for deprecation and will not be maintained
>past 2020 so it is recommended that Python 2 modules are not packaged unless
>necessary."
It's true that upstream will almost
❦ 2 avril 2017 09:45 +0100, Ghislain Vaillant :
>>> it's just a few lines down in the changelog:
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829744 (it is kinda
>>> sad that there was no discussion with the python team from the lintian
>>> maintainer before accepting and merging it, e
❦ 2 avril 2017 10:21 +0100, Chris Lamb :
>> > On the current subject, I also agree we should not drop prematurely
>> > packages targeted to Python 2.
>
> The Lintian tag in question does not suggest maintainers should be
> removing existing Python 2 support from packages.
>
> It merely suggests
Ghislain Vaillant wrote:
> > On the current subject, I also agree we should not drop prematurely
> > packages targeted to Python 2.
The Lintian tag in question does not suggest maintainers should be
removing existing Python 2 support from packages.
It merely suggests that you should think twice
On 02/04/17 08:39, Vincent Bernat wrote:
❦ 1 avril 2017 19:42 -0400, Sandro Tosi :
It's not at all clear where [1] came from. The lintian changelog [3] does not
give a bug reference and I couldn't find a bug.
it's just a few lines down in the changelog:
https://bugs.debian.org/cgi-bin/bug
❦ 1 avril 2017 19:42 -0400, Sandro Tosi :
>> It's not at all clear where [1] came from. The lintian changelog [3] does
>> not
>> give a bug reference and I couldn't find a bug.
>
> it's just a few lines down in the changelog:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829744 (it is k
On Sat, Apr 1, 2017 at 4:03 PM, Scott Kitterman wrote:
> On Saturday, April 01, 2017 05:12:38 PM Ghislain Vaillant wrote:
>> On Sat, 2017-04-01 at 15:55 +, Scott Kitterman wrote:
>> > On April 1, 2017 3:42:50 AM EDT, Ghislain Vaillant
> wrote:
>> > > ...
>> > >
>> > > How so? Buster will not
On Saturday, April 01, 2017 05:12:38 PM Ghislain Vaillant wrote:
> On Sat, 2017-04-01 at 15:55 +, Scott Kitterman wrote:
> > On April 1, 2017 3:42:50 AM EDT, Ghislain Vaillant
wrote:
> > > ...
> > >
> > > How so? Buster will not be supporting Python 2, so the narrative of
> > > having new so
On Sat, 2017-04-01 at 15:55 +, Scott Kitterman wrote:
>
> On April 1, 2017 3:42:50 AM EDT, Ghislain Vaillant wrote:
> > ...
> >
> > How so? Buster will not be supporting Python 2, so the narrative of
> > having new source packages only provide Python 3 binary packages is
> > totally justifie
On April 1, 2017 3:42:50 AM EDT, Ghislain Vaillant wrote:
>...
>
>How so? Buster will not be supporting Python 2, so the narrative of
>having new source packages only provide Python 3 binary packages is
>totally justified.
What makes you think this is true?
As far as I know, Python 2 will be a
cc'd to debian-python
Forwarded Message
Subject: next version of csvkit
Date: Fri, 31 Mar 2017 22:26:27 +0100
From: Ghislain Vaillant
To: Sandro Tosi , 857...@bugs.debian.org
CC: python-modules-t...@lists.alioth.debian.org
On Fri, 2017-03-31 at 16:53 -0400, Sandro
17 matches
Mail list logo
