From: Marius Bakke <mbakke@fastmail.com>
To: Hartmut Goebel <hartmut@goebel-consult.de>, guix-devel@gnu.org
Subject: Re: gnu: python: Update to 3.8.0.
Date: Wed, 23 Oct 2019 19:48:19 +0200 [thread overview]
Message-ID: <87o8y7wdy4.fsf@devup.no> (raw)
In-Reply-To: <2b50f965-cbb2-d476-ceaf-2f00323fb50f@goebel-consult.de>
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
Hartmut Goebel <hartmut@goebel-consult.de> writes:
> Am 23.10.19 um 11:11 schrieb Tanguy Le Carrour:
>> Python 3.8.0 was released on October the 14th [1].
>> What would be the proper way to package it for Guix?! Add a new public
>> variable `python-3.8` and make `python-3` and `python` point to it? Would
>> `python-3.7` go away?!
>
> I'm not convinced to make Python 3.8 the default Python3 (and the
> default Python) yet. Many packages might not yet support Python 3.8.
Do you think we should stick with 3.7.x for this next 'core-updates'
round?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-10-23 17:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 9:11 gnu: python: Update to 3.8.0 Tanguy Le Carrour
2019-10-23 11:42 ` Hartmut Goebel
2019-10-23 12:51 ` Tanguy Le Carrour
2019-10-23 13:16 ` Hartmut Goebel
2019-10-30 16:04 ` Tanguy Le Carrour
2019-10-30 18:01 ` Tanguy Le Carrour
2019-10-31 23:08 ` Marius Bakke
2019-11-04 9:15 ` Tanguy Le Carrour
2019-11-04 9:19 ` Gábor Boskovits
2019-11-04 10:50 ` Tanguy Le Carrour
2019-11-04 12:31 ` Gábor Boskovits
2019-11-13 8:03 ` Tanguy Le Carrour
2019-11-13 11:29 ` Tobias Geerinckx-Rice
2019-11-13 13:25 ` Tanguy Le Carrour
2019-11-13 11:34 ` Gábor Boskovits
2019-11-13 13:23 ` Tanguy Le Carrour
2019-11-13 13:27 ` Gábor Boskovits
2019-11-14 8:48 ` Tanguy Le Carrour
2019-11-10 23:02 ` Marius Bakke
2019-10-23 17:48 ` Marius Bakke [this message]
2019-10-24 8:03 ` Hartmut Goebel
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8y7wdy4.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=hartmut@goebel-consult.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).