public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Pacho Ramos" <pacho@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/structlog/
Date: Tue, 26 Jun 2018 18:09:37 +0000 (UTC)	[thread overview]
Message-ID: <1530036567.66fe2fc8c2f1a33c83f46c99cf679dfca82fe86b.pacho@gentoo> (raw)

commit:     66fe2fc8c2f1a33c83f46c99cf679dfca82fe86b
Author:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
AuthorDate: Tue Jun 26 17:58:03 2018 +0000
Commit:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
CommitDate: Tue Jun 26 18:09:27 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=66fe2fc8

dev-python/structlog: Support python3.6

Package-Manager: Portage-2.3.40, Repoman-2.3.9

 dev-python/structlog/structlog-16.1.0.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-python/structlog/structlog-16.1.0.ebuild b/dev-python/structlog/structlog-16.1.0.ebuild
index 8b1255ed372..d4d703fd2c9 100644
--- a/dev-python/structlog/structlog-16.1.0.ebuild
+++ b/dev-python/structlog/structlog-16.1.0.ebuild
@@ -1,8 +1,8 @@
-# Copyright 1999-2016 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
-PYTHON_COMPAT=(python2_7 python3_{4,5} pypy)
+PYTHON_COMPAT=(python2_7 python3_{4,5,6} pypy)
 inherit distutils-r1
 
 DESCRIPTION="Structured Logging for Python"


             reply	other threads:[~2018-06-26 18:09 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26 18:09 Pacho Ramos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-13 18:36 [gentoo-commits] repo/gentoo:master commit in: dev-python/structlog/ Arthur Zamarin
2025-04-26  7:03 Michał Górny
2025-03-29 14:16 Michał Górny
2025-03-29 13:50 Arthur Zamarin
2025-03-29  7:59 Arthur Zamarin
2025-03-29  7:59 Arthur Zamarin
2025-03-29  7:45 Arthur Zamarin
2025-03-12  8:31 Michał Górny
2025-02-01 13:19 Michał Górny
2025-02-01 13:12 Arthur Zamarin
2025-02-01 12:17 Arthur Zamarin
2025-02-01  9:54 Arthur Zamarin
2025-02-01  9:53 Arthur Zamarin
2025-01-17  4:33 Michał Górny
2024-08-10 11:16 Michał Górny
2024-08-10 10:28 Michał Górny
2024-08-03 16:48 Jakov Smolić
2024-08-03  8:45 Michał Górny
2024-08-03  8:30 Jakov Smolić
2024-08-03  6:37 Michał Górny
2024-08-03  6:24 Michał Górny
2024-07-18  1:56 Michał Górny
2024-06-14  1:53 Michał Górny
2024-06-13 18:46 Arthur Zamarin
2024-06-12 10:29 Arthur Zamarin
2024-06-12  8:42 Jakov Smolić
2024-06-12  7:34 Arthur Zamarin
2024-06-12  7:00 Arthur Zamarin
2024-06-12  6:44 Arthur Zamarin
2024-05-28  4:27 Michał Górny
2024-05-18  9:41 Michał Górny
2024-01-25 11:37 Michał Górny
2024-01-25  5:48 Sam James
2024-01-24 20:34 Arthur Zamarin
2024-01-24 19:05 Michał Górny
2024-01-24 19:05 Michał Górny
2024-01-24 19:05 Michał Górny
2024-01-24 18:59 Michał Górny
2024-01-23 16:53 Michał Górny
2024-01-13 12:02 Sam James
2024-01-13 11:15 Sam James
2024-01-13  9:59 Arthur Zamarin
2024-01-13  9:29 Arthur Zamarin
2024-01-13  9:29 Arthur Zamarin
2024-01-09  7:02 Michał Górny
2023-12-29 17:08 Arthur Zamarin
2023-11-29  4:23 Sam James
2023-11-28  5:27 Arthur Zamarin
2023-11-28  5:27 Arthur Zamarin
2023-11-28  5:27 Arthur Zamarin
2023-11-01 16:05 Michał Górny
2023-11-01 12:23 Arthur Zamarin
2023-10-29 20:22 Sam James
2023-10-29 20:22 Sam James
2023-10-29 20:21 Sam James
2023-10-29 20:21 Sam James
2023-10-29 20:21 Sam James
2023-10-10  5:05 Michał Górny
2023-09-22  8:51 Arthur Zamarin
2023-09-09  9:35 WANG Xuerui
2023-08-24 18:04 Jakov Smolić
2023-08-22 20:19 Sam James
2023-08-22 17:06 Sam James
2023-06-01 14:59 Michał Górny
2023-04-08  6:08 Michał Górny
2023-04-07  4:19 Michał Górny
2023-02-10 11:53 Bernard Cafarelli
2023-02-10  8:15 Bernard Cafarelli
2023-02-09 23:27 Bernard Cafarelli
2019-04-09  3:14 Austin English
2016-06-08 19:02 Austin English

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=1530036567.66fe2fc8c2f1a33c83f46c99cf679dfca82fe86b.pacho@gentoo \
    --to=pacho@gentoo.org \
    --cc=gentoo-commits@lists.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