From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] About adding a *warning* to remind maintainers to check for new PYTHON_COMPAT values
Date: Mon, 10 Jul 2017 13:04:10 +0200 [thread overview]
Message-ID: <1499684650.24824.6.camel@gentoo.org> (raw)
Hello
Looking to the list of packages still not supporting python 3.5:
https://qa-reports.gentoo.org/output/gpyutils/34-to-35.txt
and considering that we should even start testing python 3.6, I think it would
be nice if we could make portage to warn when PYTHON_COMPAT value is not
updated. It's really frustrating to still see new ebuilds being added with
obsolete values for PYTHON_COMPAT and relying on a few people looking to update
this. This is also causing huge delays to migrate to newer python versions and I
think it's responsibility of the maintainer to ensure his/her package is
supported on newer versions or, at least, have a bug and ping upstream for the
cases they need further fixing.
Of course, this wouldn't be a fatal check preventing you from committing a
package with outdated PYTHON_COMPAT, it would be a warning to remind you to
update it as soon as possible.
Any issues on trying to go further into implementing this warning?
Thanks a lot
next reply other threads:[~2017-07-10 11:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 11:04 Pacho Ramos [this message]
2017-07-10 11:12 ` [gentoo-dev] About adding a *warning* to remind maintainers to check for new PYTHON_COMPAT values 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 ` [gentoo-dev] " M. J. Everitt
2017-07-10 13:49 ` 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=1499684650.24824.6.camel@gentoo.org \
--to=pacho@gentoo.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