From: R0b0t1 <r030t1@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Python 3.5
Date: Sat, 28 Oct 2017 20:22:31 -0500 [thread overview]
Message-ID: <CAAD4mYhgSnghSvfk6W6eFqrD8sgXVtb5sH+_Sv3GrXEdYE5_nw@mail.gmail.com> (raw)
In-Reply-To: <20171029011743.GL1962@ca.inter.net>
On Sat, Oct 28, 2017 at 8:17 PM, Philip Webb <purslow@ca.inter.net> wrote:
> Python 3.5 has become stable : what are the pro/cons of updating to it ?
> I have in make.conf :
>
> USE_PYTHON="2.7 3.4"
> PYTHON_TARGETS="python2_7 python3_4"
> PYTHON_SINGLE_TARGET="python3_4"
>
> Is it advisable to replace '3_4' '3.4' with '3_5' '3.5' ?
>
Python 3.5 adds some very novel language features that new projects
have already started to depend on. In fact, some packages (such as
qutebrowser) are soon to require Python 3.6, which provides some
extremely useful extensions to the extremely useful extensions.
If you have nothing that requires it at this moment it is unlikely you
have any need to update, but it is a good practice to track stable.
Cheers,
R0b0t1.
next prev parent reply other threads:[~2017-10-29 1:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 1:17 [gentoo-user] Python 3.5 Philip Webb
2017-10-29 1:22 ` R0b0t1 [this message]
2017-10-29 8:24 ` Adam Carter
2017-10-29 8:31 ` Adam Carter
2017-10-29 9:11 ` Peter Humphrey
2017-10-29 11:15 ` Alan McKinnon
2017-10-29 16:32 ` R0b0t1
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAD4mYhgSnghSvfk6W6eFqrD8sgXVtb5sH+_Sv3GrXEdYE5_nw@mail.gmail.com \
--to=r030t1@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox