public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Benjamin A. Beasley <code@musicinmybrain.net>
To: git-commits@fedoraproject.org
Subject: [rpms/python-pint] rpmlint-etc: Remove unused/disabled docs conditional
Date: Sat, 12 Sep 2026 10:21:47 GMT [thread overview]
Message-ID: <178920850782.1.4561842432645260609.rpms-python-pint-e9b556312f42@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-pint
Branch : rpmlint-etc
Commit : e9b556312f428a8bf12df0b2f5cbae92ddbe65df
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date : 2023-10-29T21:55:40-04:00
Stats : +0/-36 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/python-pint/c/e9b556312f428a8bf12df0b2f5cbae92ddbe65df?branch=rpmlint-etc
Log:
Remove unused/disabled docs conditional
Sphinx-generated HTML documentation is unsuitable for packaging; see
https://bugzilla.redhat.com/show_bug.cgi?id=2006555 and linked mailing
list threads.
It might be possible to generate a PDF with Sphinx; if so, the best way
would be to use the GitHub source archive if necessary to get
requirements_docs.txt and use it to generate BuildRequires. However, it
seems unlikely that this will be worthwhile.
---
diff --git a/python-pint.spec b/python-pint.spec
index 537a012..1b1c5ba 100644
--- a/python-pint.spec
+++ b/python-pint.spec
@@ -1,5 +1,4 @@
%global pypi_name Pint
-%bcond_with docs
Name: python-pint
Version: 0.17
@@ -38,27 +37,6 @@ to different units.
It is distributed with a comprehensive list of physical units, prefixes
and constants.
-%if %{with docs}
-%package -n python3-pint-doc
-Summary: Documentation for the pint module
-%{?python_provide:%python_provide python3-pint-doc}
-
-BuildRequires: pandoc
-BuildRequires: python3-graphviz
-BuildRequires: python3-ipykernel
-BuildRequires: python3-jupyter-client
-BuildRequires: python3-matplotlib
-BuildRequires: python3-nbsphinx
-BuildRequires: python3-pandas
-BuildRequires: python3-dask
-BuildRequires: python3-pygments
-BuildRequires: python3-sphinx
-BuildRequires: python3-xarray
-
-%description -n python3-pint-doc
-Documentation for the pint module
-%endif
-
%prep
%setup -q -n %{pypi_name}-%{version}
@@ -87,14 +65,6 @@ sed -i '/@helpers.requires_numpy_at_least("1.16")/d' pint/testsuite/test_quantit
%build
%pyproject_wheel
-%if %{with docs}
-export PYTHONPATH="$( pwd ):$PYTHONPATH"
-sphinx-build-3 docs html
-# remove the sphinx-build leftovers
-
-rm -rf html/.{doctrees,buildinfo}
-%endif
-
%install
%pyproject_install
@@ -107,11 +77,5 @@ rm -rf html/.{doctrees,buildinfo}
%{python3_sitelib}/pint
%{python3_sitelib}/Pint-%{version}.*
-%if %{with docs}
-%files -n python3-pint-doc
-%doc html
-%license docs/_themes/LICENSE
-%endif
-
%changelog
%autochangelog
reply other threads:[~2026-09-12 10:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178920850782.1.4561842432645260609.rpms-python-pint-e9b556312f42@fedoraproject.org \
--to=code@musicinmybrain.net \
--cc=git-commits@fedoraproject.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