From: "Andrew Ammerlaan" <andrewammerlaan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: dev-python/fslpy/
Date: Tue, 11 Oct 2022 19:20:32 +0000 (UTC) [thread overview]
Message-ID: <1665514872.6df21099f76d9c9f49670a3bf61b12fc0edb4762.andrewammerlaan@gentoo> (raw)
commit: 6df21099f76d9c9f49670a3bf61b12fc0edb4762
Author: Andrew Ammerlaan <andrewammerlaan <AT> gentoo <DOT> org>
AuthorDate: Tue Oct 11 19:01:12 2022 +0000
Commit: Andrew Ammerlaan <andrewammerlaan <AT> gentoo <DOT> org>
CommitDate: Tue Oct 11 19:01:12 2022 +0000
URL: https://gitweb.gentoo.org/proj/sci.git/commit/?id=6df21099
dev-python/fslpy: add 3.10.0
Signed-off-by: Andrew Ammerlaan <andrewammerlaan <AT> gentoo.org>
dev-python/fslpy/fslpy-3.10.0.ebuild | 47 ++++++++++++++++++++++++++++++++++++
1 file changed, 47 insertions(+)
diff --git a/dev-python/fslpy/fslpy-3.10.0.ebuild b/dev-python/fslpy/fslpy-3.10.0.ebuild
new file mode 100644
index 000000000..7140be033
--- /dev/null
+++ b/dev-python/fslpy/fslpy-3.10.0.ebuild
@@ -0,0 +1,47 @@
+# Copyright 1999-2022 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+PYTHON_COMPAT=( python3_{8..10} )
+DISTUTILS_USE_PEP517=setuptools
+inherit distutils-r1 virtualx
+
+DESCRIPTION="The FSL Python Library"
+HOMEPAGE="https://git.fmrib.ox.ac.uk/fsl/fslpy"
+SRC_URI="https://git.fmrib.ox.ac.uk/fsl/${PN}/-/archive/${PV}/${P}.tar.gz"
+
+LICENSE="BSD"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+
+RDEPEND="
+ dev-python/dill[${PYTHON_USEDEP}]
+ >=dev-python/h5py-2.9[${PYTHON_USEDEP}]
+ >=dev-python/indexed_gzip-0.7.0[${PYTHON_USEDEP}]
+ >=dev-python/numpy-1[${PYTHON_USEDEP}]
+ >=dev-python/pillow-3.2.0[${PYTHON_USEDEP}]
+ >=dev-python/trimesh-2.37.29[${PYTHON_USEDEP}]
+ =dev-python/wxpython-4*[${PYTHON_USEDEP}]
+ >=sci-libs/rtree-0.8.3[${PYTHON_USEDEP}]
+ >=sci-libs/nibabel-2.4[${PYTHON_USEDEP}]
+ >=dev-python/scipy-0.18[${PYTHON_USEDEP}]
+"
+
+distutils_enable_tests pytest
+distutils_enable_sphinx doc dev-python/sphinx_rtd_theme
+
+python_prepare_all() {
+ # Do not depend on coverage
+ sed -i -e 's/--cov=fsl//g' setup.cfg || die
+
+ distutils-r1_python_prepare_all
+}
+
+src_test() {
+ virtx distutils-r1_src_test
+}
+
+python_test() {
+ epytest -m "not (dicomtest or longtest or fsltest)" || die "Tests failed with ${EPYTHON}"
+}
next reply other threads:[~2022-10-11 19:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 19:20 Andrew Ammerlaan [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-23 14:22 [gentoo-commits] proj/sci:master commit in: dev-python/fslpy/ Andrew Ammerlaan
2024-09-23 14:22 Andrew Ammerlaan
2023-07-26 22:14 Alexander Puck Neuwirth
2023-05-03 0:14 Horea Christian
2023-02-16 7:38 Horea Christian
2022-10-11 19:20 Andrew Ammerlaan
2022-07-07 4:54 Sam James
2022-01-23 13:06 Andrew Ammerlaan
2022-01-14 20:36 Andrew Ammerlaan
2021-10-10 22:05 Horea Christian
2021-09-30 10:59 Horea Christian
2021-03-15 8:30 Andrew Ammerlaan
2021-02-01 1:27 Horea Christian
2021-01-20 12:29 Andrew Ammerlaan
2020-12-23 8:38 Horea Christian
2020-10-22 6:11 Horea Christian
2020-10-22 6:11 Horea Christian
2020-10-19 21:55 Horea Christian
2020-03-16 20:05 Horea Christian
2019-11-08 6:25 Horea Christian
2019-11-08 6:17 Horea Christian
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=1665514872.6df21099f76d9c9f49670a3bf61b12fc0edb4762.andrewammerlaan@gentoo \
--to=andrewammerlaan@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