public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alessandro Barbieri" <lssndrbarbieri@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-python/schedule/
Date: Mon, 14 Jun 2021 23:09:46 +0000 (UTC)	[thread overview]
Message-ID: <1623712182.41847e9e7efd657d527a5a14c013e870083c0031.Alessandro-Barbieri@gentoo> (raw)

commit:     41847e9e7efd657d527a5a14c013e870083c0031
Author:     Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
AuthorDate: Mon Jun 14 22:47:24 2021 +0000
Commit:     Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
CommitDate: Mon Jun 14 23:09:42 2021 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=41847e9e

dev-python/schedule: drop 1.0.0

Signed-off-by: Alessandro Barbieri <lssndrbarbieri <AT> gmail.com>

 dev-python/schedule/Manifest              |  1 -
 dev-python/schedule/schedule-1.0.0.ebuild | 28 ----------------------------
 2 files changed, 29 deletions(-)

diff --git a/dev-python/schedule/Manifest b/dev-python/schedule/Manifest
index 1b6aaab6a..e7435225e 100644
--- a/dev-python/schedule/Manifest
+++ b/dev-python/schedule/Manifest
@@ -1,2 +1 @@
-DIST schedule-1.0.0.tar.gz 27992 BLAKE2B 620afa1d78065f189799e4deaae8a627d1698292cf885acdacdfd6688b8774ed155a13c8213bb0f6dfd70dec5e17ea317658f5d78e6cbdc87d670003c218e154 SHA512 79e350d5e5083bb6da70bbd12f4e8895a08fc79088f042fa9171aec48b8a45985f1638511136be2ee8f4aa92d6992978f8c85560867b6fa88a07383e952c8c4b
 DIST schedule-1.1.0.tar.gz 31873 BLAKE2B 6e33e862f94c72f32ae3bba566ad4a64428cc90f80ed6ff8d577a29717b3cc5f3c91195742cedfedbcc4090d955f343097f53ed69e9922775969c854780798ce SHA512 3fe06e334ed532f013aeb806b7beacd9418c4dbbcb80d4b27090c08178f1874694ecfced24eeddc8450e99a80831d68b34a4a3b2638a870f30f53f570650795c

diff --git a/dev-python/schedule/schedule-1.0.0.ebuild b/dev-python/schedule/schedule-1.0.0.ebuild
deleted file mode 100644
index 2ddaa3244..000000000
--- a/dev-python/schedule/schedule-1.0.0.ebuild
+++ /dev/null
@@ -1,28 +0,0 @@
-# Copyright 1999-2021 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=7
-
-#pypy3 fails tests
-PYTHON_COMPAT=( python3_{7,8,9} )
-
-inherit distutils-r1
-
-DESCRIPTION="Python job scheduling for humans"
-HOMEPAGE="https://github.com/dbader/schedule"
-
-SRC_URI="https://github.com/dbader/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
-KEYWORDS="~amd64 ~arm ~arm64 ~x86"
-
-LICENSE="MIT"
-SLOT="0"
-
-RDEPEND=""
-DEPEND="
-	test? (
-		dev-python/mock[${PYTHON_USEDEP}]
-	)
-"
-
-distutils_enable_tests pytest
-distutils_enable_sphinx docs dev-python/pygments


             reply	other threads:[~2021-06-14 23:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 23:09 Alessandro Barbieri [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-29 21:04 [gentoo-commits] repo/proj/guru:dev commit in: dev-python/schedule/ Alessandro Barbieri
2021-05-09  0:35 Alessandro Barbieri
2021-03-28  9:55 Andrew Ammerlaan
2021-03-27 18:35 Alessandro Barbieri
2021-03-27 18:35 Alessandro Barbieri
2020-04-07  1:22 Alessandro Barbieri
2020-04-07  1:22 Alessandro Barbieri

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=1623712182.41847e9e7efd657d527a5a14c013e870083c0031.Alessandro-Barbieri@gentoo \
    --to=lssndrbarbieri@gmail.com \
    --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