all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: Multiple python-3 packages
Date: Fri, 27 Jan 2017 18:34:56 +0100	[thread overview]
Message-ID: <87bmus2ypr.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170127101225.GA28495@jasmine>

[-- Attachment #1: Type: text/plain, Size: 980 bytes --]

Leo Famulari <leo@famulari.name> writes:

> Currently we have Python 3.4 and 3.5. Python 3.6 was released recently.
>
> When we added 3.5, I thought it was a good idea to keep 3.4 around in
> case some packages need it. It turns out that nothing is using it in our
> tree.
>
> Do we want to keep 3.4 and 3.5 around? There is a maintenance cost
> incurred at each new release, because their shared patches tend to
> diverge each time.
>
> If we should keep them, how should the package inheritance go? Now, it's
> like this:
>
> 2.7 < 3.5 < 3.4
>
> If we kept them all, should 3.5 and 3.4 both inherit 3.6?

Hi Leo!

I think python 3.x releases should inherit from the latest indeed. That
way changes to lower 3.x releases are guaranteed not to affect the
newest one.

No preference for keeping older releases around either. Unless any
python folks wants to maintain them, I think they can be dropped.

Perhaps we can use python-3.6 as the basis for a new "python-updates"
branch?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      parent reply	other threads:[~2017-01-27 17:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27 10:12 Multiple python-3 packages Leo Famulari
2017-01-27 15:18 ` Benz Schenk
2017-01-27 17:34 ` Marius Bakke [this message]

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=87bmus2ypr.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mbakke@fastmail.com \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.