From: "M. J. Everitt" <m.j.everitt@iee.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] About adding a *warning* to remind maintainers to check for new PYTHON_COMPAT values
Date: Mon, 10 Jul 2017 15:59:38 +0100 [thread overview]
Message-ID: <ef507115-6c9b-09d8-622b-54335fb704a1@emjay-embedded.co.uk> (raw)
In-Reply-To: <1499687023.24824.12.camel@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 857 bytes --]
On 10/07/17 12:43, Pacho Ramos wrote:
> El lun, 10-07-2017 a las 13:12 +0200, Kristian Fiskerstrand escribió:
>> On 07/10/2017 01:04 PM, Pacho Ramos wrote:
>>> Any issues on trying to go further into implementing this warning?
>> Not an issue per se, but it should be pointed out that python 3.5 only
>> has a testing visibility, so this at the very least requires maintainers
>> to potentially have a separate testing chroot/VM to test when adding the
>> compat.
>>
> Yes, but it's similar as the cases when we need to fix our packages to work with
> a newer library they depend on. In this case it would be even easier as we can
> have multiple python versions and switch to the newer one for testing while
> going back to the stable one (if preferred) later.
>
Is this something that could be aided any by the tinderbox'ing project?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 874 bytes --]
next prev parent reply other threads:[~2017-07-10 15:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 11:04 [gentoo-dev] About adding a *warning* to remind maintainers to check for new PYTHON_COMPAT values Pacho Ramos
2017-07-10 11:12 ` Kristian Fiskerstrand
2017-07-10 11:43 ` Pacho Ramos
2017-07-10 13:35 ` Kent Fredric
2017-07-10 13:41 ` Kristian Fiskerstrand
2017-07-11 4:24 ` Brian Dolbec
2017-07-10 14:22 ` [gentoo-dev] " Michael Palimaka
2017-07-10 14:59 ` M. J. Everitt [this message]
2017-07-10 13:49 ` [gentoo-dev] " Rich Freeman
2017-07-10 16:55 ` William Hubbs
2017-07-10 17:25 ` Alexis Ballier
2017-07-11 11:21 ` Pacho Ramos
-- strict thread matches above, loose matches on Subject: below --
2017-07-10 17:37 Kent Fredric
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=ef507115-6c9b-09d8-622b-54335fb704a1@emjay-embedded.co.uk \
--to=m.j.everitt@iee.org \
--cc=gentoo-dev@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