public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pickleshare/
Date: Sat, 28 Nov 2015 17:33:18 +0000 (UTC)	[thread overview]
Message-ID: <1448638248.856f8100117098436871478e12603bfbc051d2f1.jlec@gentoo> (raw)

commit:     856f8100117098436871478e12603bfbc051d2f1
Author:     Marius Brehler <marbre <AT> linux <DOT> sungazer <DOT> de>
AuthorDate: Fri Nov 27 15:30:48 2015 +0000
Commit:     Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Fri Nov 27 15:30:48 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=856f8100

dev-python/pickleshare: Import from science overlay

Package-Manager: portage-2.2.20.1

 dev-python/pickleshare/Manifest               |  1 +
 dev-python/pickleshare/metadata.xml           | 18 ++++++++++++++
 dev-python/pickleshare/pickleshare-0.5.ebuild | 34 +++++++++++++++++++++++++++
 3 files changed, 53 insertions(+)

diff --git a/dev-python/pickleshare/Manifest b/dev-python/pickleshare/Manifest
new file mode 100644
index 0000000..79e862d
--- /dev/null
+++ b/dev-python/pickleshare/Manifest
@@ -0,0 +1 @@
+DIST pickleshare-0.5.tar.gz 4441 SHA256 c0be5745035d437dbf55a96f60b7712345b12423f7d0951bd7d8dc2141ca9286 SHA512 1021b76591b5b1d6c777e03c9544fea63602f719b786a2a2e73590f8e8275156fa69b336adf81a6e8abcaad2263eacd76ce4abf2ceff04126ff6b1ffd96cb4e3 WHIRLPOOL 07907feb8dab2dfbfc74e43d17cc076027ab450091a8dd4af197019c6c46e268eda1d5761ab22fc774e37090ab7d51212d82ba284d89018fbc0f52c38f235c62

diff --git a/dev-python/pickleshare/metadata.xml b/dev-python/pickleshare/metadata.xml
new file mode 100644
index 0000000..ea703f9
--- /dev/null
+++ b/dev-python/pickleshare/metadata.xml
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+  <herd>sci</herd>
+  <longdescription>
+    Like shelve, a PickleShareDB object acts like a normal dictionary.
+    Unlike shelve, many processes can access the database
+    simultaneously. Changing a value in database is immediately visible
+    to other processes accessing the same database.
+    Concurrency is possible because the values are stored in separate
+    files. Hence the "database" is a directory where all files are
+    governed by PickleShare.
+  </longdescription>
+  <upstream>
+    <remote-id type="pypi">pickleshare</remote-id>
+    <remote-id type="github">pickleshare/pickleshare</remote-id>
+  </upstream>
+</pkgmetadata>

diff --git a/dev-python/pickleshare/pickleshare-0.5.ebuild b/dev-python/pickleshare/pickleshare-0.5.ebuild
new file mode 100644
index 0000000..7fd09f4
--- /dev/null
+++ b/dev-python/pickleshare/pickleshare-0.5.ebuild
@@ -0,0 +1,34 @@
+# Copyright 1999-2015 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Id$
+
+EAPI=5
+
+PYTHON_COMPAT=( python2_7 python3_{3,4,5} )
+
+inherit distutils-r1
+
+DESCRIPTION="A small 'shelve' like datastore with concurrency support"
+HOMEPAGE="https://github.com/pickleshare/pickleshare"
+SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+IUSE="test"
+
+RDEPEND="
+	dev-python/path-py[${PYTHON_USEDEP}]"
+DEPEND="${RDEPEND}
+	test? ( dev-python/pytest[${PYTHON_USEDEP}] )"
+
+# test_pickleshare.py is not included in the pickleshare-0.5 source
+# we fetched from pipy
+RESTRICT="test"
+
+python_test() {
+	distutils_install_for_testing
+	cd "${TEST_DIR}"/lib || die
+	cp "${S}"/test_pickleshare.py "${TEST_DIR}"/lib/ || die
+	py.test || die
+}


             reply	other threads:[~2015-11-28 17:33 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-28 17:33 Justin Lecher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-01-21  8:33 [gentoo-commits] repo/gentoo:master commit in: dev-python/pickleshare/ Justin Lecher
2016-02-28  6:51 Matt Thode
2016-07-23 11:46 David Seifert
2016-07-30  8:28 David Seifert
2016-10-19 23:22 Patrice Clement
2016-10-19 23:22 Patrice Clement
2017-02-04 21:30 David Seifert
2017-03-12  6:19 Zac Medico
2017-05-22 16:41 Michał Górny
2018-03-04 22:40 Sergei Trofimovich
2018-03-12  0:51 Matt Turner
2018-03-21 20:24 Markus Meier
2018-05-16 12:28 Agostino Sarubbo
2018-05-27  8:44 Mart Raudsepp
2019-12-14  0:41 David Seifert
2020-01-26 17:11 Michał Górny
2020-03-01  4:12 Andrey Grozin
2020-03-28 11:59 Michał Górny
2020-06-02 22:21 Mart Raudsepp
2020-06-03 18:43 Agostino Sarubbo
2020-06-08 17:36 Michał Górny
2020-06-10  8:11 Michał Górny
2021-05-06 11:38 Michał Górny
2021-06-29  5:53 Yixun Lan
2021-09-08 16:19 Sam James
2021-09-26 17:52 Sam James
2021-11-01 15:46 Sam James
2022-01-30 11:33 James Le Cuirot
2022-02-14  8:35 Matt Turner
2022-05-16 14:43 Andrew Ammerlaan
2022-09-22  7:45 Michał Górny
2023-09-14 11:24 Andrew Ammerlaan
2023-10-14 16:52 Arthur Zamarin
2023-10-14 18:17 Arthur Zamarin
2023-10-14 18:17 Arthur Zamarin
2023-10-14 19:52 Arthur Zamarin
2023-10-15  7:38 Sam James
2023-10-15  8:00 Sam James
2023-10-27 12:17 Sam James
2023-10-27 14:04 Michał Górny
2023-11-16 19:43 Michał Górny
2023-11-16 19:43 Michał Górny
2024-05-18  6:58 Michał Górny

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=1448638248.856f8100117098436871478e12603bfbc051d2f1.jlec@gentoo \
    --to=jlec@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