Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #10620

Re: Could somebody change the alioth documentation, have a buster roadmap and know what's missing to move to python 3 entirely.

Path csiph.com!feeder.erje.net!2.eu.feeder.erje.net!news2.arglkargh.de!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From shirish शिरीष <shirishag75@gmail.com>
Newsgroups linux.debian.maint.python
Subject Re: Could somebody change the alioth documentation, have a buster roadmap and know what's missing to move to python 3 entirely.
Date Wed, 06 Jun 2018 19:00:01 +0200
Message-ID <vXJWV-5dH-3@gated-at.bofh.it> (permalink)
References <vXIeu-4lA-15@gated-at.bofh.it>
X-Original-To debian-python <debian-python@lists.debian.org>
X-Mailbox-Line From debian-python-request@lists.debian.org Wed Jun 6 16:50:34 2018
Old-Return-Path <shirishag75@gmail.com>
X-Amavis-Spam-Status No, score=-4.37 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, BODY_8BITS=1.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FROM_EXCESS_BASE64=0.979, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
X-Policyd-Weight using cached result; rate:hard: -7
Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=O/QbX4VYHmLu0iv3SItohCgiTb7421ftQ0A92GReWsw=; b=bdHvppTJh21UHhHBXr0VFMY73+Lb+ncrDChSSfiMhRDtngJLk1aHA2lE96mrNjuZx1 LT9QdQxqZN0dWIixhYg2i9WSeVuC7fcF2Zeud4tDOtnoCDNFSdjGmikeAkn6XMKgXxsO f01oP1D48V/63VN6RvAzIJL+DE6+P11lmtJbFmCIcfHHRe+AO7fbbpiti6BQNYZb4f28 kb0ouKdWc+4h0UrSCt7HzYqKZMe/qFqP0yh1reQpRQxd1YdZ6mhgKW1R6NmOhA4lT+vr aR5LK5ZkJ10ZyfitkTLNHHErtjfxcAm0Vwe9g6hrxg7YBw7kmi6AXcPiusF2K7A6a2qF U/cQ==
X-Google-Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=O/QbX4VYHmLu0iv3SItohCgiTb7421ftQ0A92GReWsw=; b=XXdKAbimfi7t0Ba9m/9ZOJ68+4F7vsMzWJHV1+R11F/j8rux1CHOTveAYsxHK578Rs P7orrI/l9jWFEHcLo1UivnhA5r7SSEhdkDnN42k2qtp8owEKt23zcQmg/PC1ojXPDprN 2hDoduXKLVFr+DSqeyMam7mycmmIuWJzuSA9+/Bn9TD3ZY4c8fXypc9szqU64Q+z8MRY ElYTZyu6+fDZFO3+KD8F8eHlDXtZIe905jpZVXCGFddaJztXbZoDkTnVz72T0GwGJdIy /clRZV0W/smlj9ciLYjarnfex+zwPrd5Hqgl6SdSTsmPigt0prw5AQYL5U3cDRImCa58 SmLQ==
X-Gm-Message-State APt69E3l0lR6ISSqetV6rySyv91gBulun7rF7MxPfVzdOrCWQ2OMkcXM 8Fo221CTgRRi76Sq7BOPD+uQUm/sV/6xnPbavPoebQ==
X-Google-SMTP-Source ADUXVKK7iFBg8Br7x9TJm0CZYTI68JQ8JXLHO+b03vTSOZVkv1WvmqtLdMSxALTb8wpRO5xPnRx9XR9m3C4XCU0Rz1g=
X-Received by 2002:a0d:c601:: with SMTP id i1-v6mr1741724ywd.495.1528303815348; Wed, 06 Jun 2018 09:50:15 -0700 (PDT)
MIME-Version 1.0
Content-Type text/plain; charset="UTF-8"
Content-Transfer-Encoding quoted-printable
X-Mailing-List <debian-python@lists.debian.org> archive/latest/16029
List-ID <debian-python.lists.debian.org>
List-URL <https://lists.debian.org/debian-python/>
List-Archive https://lists.debian.org/msgid-search/CADdDZR=s=8VAApy5UH8F0YwJz-kJtvFnXz7ktc3WMZenTuZLYg@mail.gmail.com
Approved robomod@news.nic.it
Lines 73
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Date Wed, 6 Jun 2018 22:20:13 +0530
X-Original-Message-ID <CADdDZR=s=8VAApy5UH8F0YwJz-kJtvFnXz7ktc3WMZenTuZLYg@mail.gmail.com>
X-Original-References <CADdDZRntSyvtWmEKwXMMZkbnr=Vg=O-BHxD3k=_mkH8n+DUkUg@mail.gmail.com>
Xref csiph.com linux.debian.maint.python:10620

Show key headers only | View raw


at bottom :-

On 06/06/2018, shirish शिरीष <shirishag75@gmail.com> wrote:
> Dear Friends,
>
> I was just looking for documentation about what's keeping us from
> getting to python 3 but couldn't find anything which I could lay my
> finger on.
>
> I did find some obsolete documentation though on the wiki. The entries
> can be seen at -
>
> https://wiki.debian.org/Python
>
> and
>
> https://wiki.debian.org/Python/Python3Port
>
> The list addresses are of alioth glven therein. I am guessing most of
> those mails have been submerged in debian-python debian mailing list
> (i.e. here) probably.
>
> I was also looking for a BusterRoadmap on lines of the Stretch roadmap
> and the Jessie roadmap from before but didn't find anything :(
>
> https://wiki.debian.org/Python/StretchRoadmap
> https://wiki.debian.org/Python/JessieRoadmap
>
> I have also been trying to understand which packages/modules are
> remaining for python 3 to be the default-python
>
> $ apt-cache policy python
> python:
>   Installed: 2.7.15~rc1-1
>   Candidate: 2.7.15~rc1-1
>   Version table:
>  *** 2.7.15~rc1-1 500
>         500 http://cdn-fastly.deb.debian.org/debian buster/main amd64
> Packages
>         100 http://cdn-fastly.deb.debian.org/debian unstable/main amd64
> Packages
>         100 /var/lib/dpkg/status
>
> Look forward to answers. I do remember of times reading documentation
> when the stdlib did not have all the libraries of a particular 3.x
> version. I also remember reading somewhere that we still used lot of
> python 2 scripts. Another could be that 2.7 will have support till
> 2020.
>
> In either way having a roadmap would be nice.
>

I just read Andrey's mail at
https://lists.debian.org/debian-python/2018/06/msg00024.html . Please
CC me if somebody replies.

Maybe it would have been better to say that right now python gives

$ python --version
Python 2.7.15

To be more precise,  I meant to know if 'Bullseye' i.e Debian 11 would
have python 3.0 as default or not.

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Could somebody change the alioth documentation, have a buster roadmap  and know what's missing to move to python 3 entirely. shirish शिरीष <shirishag75@gmail.com> - 2018-06-06 17:10 +0200
  Re: Could somebody change the alioth documentation, have a buster  roadmap and know what's missing to move to python 3 entirely. Andrey Rahmatullin <wrar@debian.org> - 2018-06-06 17:30 +0200
  Re: Could somebody change the alioth documentation, have a buster  roadmap and know what's missing to move to python 3 entirely. shirish शिरीष <shirishag75@gmail.com> - 2018-06-06 19:00 +0200
    Re: Could somebody change the alioth documentation, have a buster  roadmap and know what's missing to move to python 3 entirely. Andrey Rahmatullin <wrar@debian.org> - 2018-06-06 20:10 +0200
    Re: Could somebody change the alioth documentation, have a buster roadmap and know what's missing to move to python 3 entirely. Ben Finney <bignose@debian.org> - 2018-06-07 11:10 +0200
      Re: Could somebody change the alioth documentation, have a buster  roadmap and know what's missing to move to python 3 entirely. Ondrej Novy <novy@ondrej.org> - 2018-06-07 12:00 +0200
        Re: Could somebody change the alioth documentation, have a buster roadmap and know what's missing to move to python 3 entirely. Ben Finney <bignose@debian.org> - 2018-06-08 00:10 +0200

csiph-web