public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/zc-lockfile/
Date: Wed,  1 Mar 2023 06:16:30 +0000 (UTC)	[thread overview]
Message-ID: <1677651382.252bbc80f1f07745c052d685c36a6eed273af102.mgorny@gentoo> (raw)

commit:     252bbc80f1f07745c052d685c36a6eed273af102
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Wed Mar  1 06:10:56 2023 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Wed Mar  1 06:16:22 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=252bbc80

dev-python/zc-lockfile: Bump to 3.0_p1

Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>

 dev-python/zc-lockfile/Manifest                  |  1 +
 dev-python/zc-lockfile/zc-lockfile-3.0_p1.ebuild | 46 ++++++++++++++++++++++++
 2 files changed, 47 insertions(+)

diff --git a/dev-python/zc-lockfile/Manifest b/dev-python/zc-lockfile/Manifest
index 04626a0484a3..8436d1d679fa 100644
--- a/dev-python/zc-lockfile/Manifest
+++ b/dev-python/zc-lockfile/Manifest
@@ -1,2 +1,3 @@
 DIST zc.lockfile-2.0.tar.gz 11923 BLAKE2B 7609f64eef4521f0aa95dc899b253570a317bd997cced00665a2dbe22cf7f834ce75daaf4fdf79520157dee31742758aad1844d49c5eccb780e7d5fd2e8e5ac5 SHA512 2586bafacb12540383695a24cb01fd284e61bfa3fcb16431ed0e91278e547c68983363fb69c1ffbd54f7c22db43300ba018ccd2fb3e21666c98860415b7a3c3b
+DIST zc.lockfile-3.0.post1.tar.gz 10190 BLAKE2B 80f732b758581b25f7d45c843b73b35985ad24185a04d207b612b448e6a1c52e49103d214e9a8b1fa0c3965037c8bcd73c504c5e0e8267814a380e08dc6f1256 SHA512 180d167ffd5760d8f9de02fcbf8e715ad04382d530f3b2970b92e346a588bb3da16926871be944441b2c0d4c8501a9d59fed2dc3c0a733b6c4478b6571d4b911
 DIST zc.lockfile-3.0.tar.gz 10043 BLAKE2B 9435f9999f976e6bfd6302b3d24960e21992f54755c6dadd9f0392254ff89b474039d7502c81c9667b4bb741300ced33bca35634f8990840809692cb025cb7f5 SHA512 65662d03933b0e295d69971a74a1d1ddf67086287bd98752d6d23d793130b0c612413c0dba365f7fa2213a5ef0981fc20bccbde304dc36a4092ad1f702ee9429

diff --git a/dev-python/zc-lockfile/zc-lockfile-3.0_p1.ebuild b/dev-python/zc-lockfile/zc-lockfile-3.0_p1.ebuild
new file mode 100644
index 000000000000..db027ffcd598
--- /dev/null
+++ b/dev-python/zc-lockfile/zc-lockfile-3.0_p1.ebuild
@@ -0,0 +1,46 @@
+# Copyright 1999-2023 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+DISTUTILS_USE_PEP517=setuptools
+PYTHON_COMPAT=( python3_{9..11} pypy3 )
+
+inherit distutils-r1 pypi
+
+DESCRIPTION="Basic inter-process locks"
+HOMEPAGE="
+	https://github.com/zopefoundation/zc.lockfile/
+	https://pypi.org/project/zc.lockfile/
+"
+SRC_URI="$(pypi_sdist_url --no-normalize "${PN/-/.}")"
+S=${WORKDIR}/${PN/-/.}-${PV/_p/.post}
+
+LICENSE="ZPL"
+SLOT="0"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~ppc ~ppc64 ~riscv ~sparc ~x86"
+
+BDEPEND="
+	test? (
+		dev-python/zope-testing[${PYTHON_USEDEP}]
+	)
+"
+
+DOCS=( CHANGES.rst README.rst )
+
+distutils_enable_tests unittest
+
+python_prepare_all() {
+	# rdep is only needed for namespace
+	sed -i -e '/install_requires.*setuptools/d' setup.py || die
+	# use implicit namespace
+	sed -i -e '/namespace_packages/d' setup.py || die
+	# do not install README into site-packages
+	sed -e '/^    include_package_data/d' -i setup.py || die
+
+	distutils-r1_python_prepare_all
+}
+
+python_test() {
+	"${EPYTHON}" -m unittest zc.lockfile.tests -v || die
+}


             reply	other threads:[~2023-03-01  6:16 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01  6:16 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-01 19:01 [gentoo-commits] repo/gentoo:master commit in: dev-python/zc-lockfile/ Arthur Zamarin
2025-02-16 20:33 Michał Górny
2025-01-04 15:08 Sam James
2024-11-30 16:43 Michał Górny
2024-10-25 12:09 Arthur Zamarin
2024-07-11 20:55 James Le Cuirot
2024-06-15  4:22 Michał Górny
2023-10-20 14:49 Michał Górny
2023-03-28  4:26 Michał Górny
2023-03-27 19:31 Sam James
2023-03-27 19:31 Sam James
2023-03-27 17:58 Arthur Zamarin
2023-03-27 17:58 Arthur Zamarin
2023-03-27 17:58 Arthur Zamarin
2023-03-27 17:58 Arthur Zamarin
2023-03-21  6:49 Michał Górny
2023-03-01  6:16 Michał Górny
2023-02-24  6:00 Michał Górny
2023-01-03  2:53 WANG Xuerui
2022-10-22 14:54 Michał Górny
2022-06-22 12:01 Michał Górny
2022-06-22 10:16 Agostino Sarubbo
2022-06-22 10:13 Agostino Sarubbo
2022-06-22 10:10 Agostino Sarubbo
2022-06-21 19:26 Arthur Zamarin
2022-06-21 18:37 Arthur Zamarin
2022-05-22  9:25 Michał Górny
2022-05-22  9:25 Michał Górny
2021-09-02 22:57 Marek Szuba
2021-06-05 18:44 Michał Górny
2020-07-13 23:13 Sam James
2020-06-22 19:05 Mart Raudsepp
2020-06-21 11:18 Michał Górny
2020-06-21 11:18 Michał Górny
2020-06-20 14:20 Thomas Deutschmann
2020-05-30 20:33 Sergei Trofimovich
2020-05-30 16:20 Michał Górny
2020-05-16 11:25 Mikle Kolyada
2020-03-29 12:22 Michał Górny
2020-03-17  2:09 Matt Turner
2020-02-06  7:10 Michał Górny
2020-01-28 10:20 Agostino Sarubbo
2019-12-12  2:19 Georgy Yakovlev
2019-12-04 19:44 Sergei Trofimovich
2019-11-22  0:20 Patrick McLean
2019-04-17 18:07 Aaron Bauman
2019-03-10  2:38 William Hubbs
2019-03-08 22:05 William Hubbs

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=1677651382.252bbc80f1f07745c052d685c36a6eed273af102.mgorny@gentoo \
    --to=mgorny@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