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: More correctly unbundle flexcache
Date: Sat, 12 Sep 2026 10:21:53 GMT [thread overview]
Message-ID: <178920851344.1.14057160767025872933.rpms-python-pint-799b93479ac7@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-pint
Branch : rpmlint-etc
Commit : 799b93479ac79a9829fec2dd81f6b2e13e170709
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date : 2023-10-31T16:53:57-04:00
Stats : +3/-2 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/python-pint/c/799b93479ac79a9829fec2dd81f6b2e13e170709?branch=rpmlint-etc
Log:
More correctly unbundle flexcache
The old approach works, but the exact replacement for
pint._vendor.flexcache should be flexcache.flexcache, not just
flexcache.
Furthermore, this correctly replaces “from pint._vendor” if that appears
in the test suite.
---
diff --git a/python-pint.spec b/python-pint.spec
index f4d8ce5..a1cc74b 100644
--- a/python-pint.spec
+++ b/python-pint.spec
@@ -74,10 +74,11 @@ sed -r -i 's/^setup_requires/install_requires = appdirs; flexcache\n&/' \
# The find-then-modify pattern keeps us from discarding mtimes on sources that
# do not need modification.
find pint -type f -exec \
- gawk '/^from \.+_vendor import (appdirs|flexcache)/ {
+ gawk '/^from (\.*|pint)\._vendor import (appdirs|flexcache)/ {
print FILENAME; nextfile }' '{}' '+' |
xargs -r -t sed -r -i \
- 's/^from \.+_vendor (import (appdirs|flexcache))/\1/'
+ -e 's/^from (\.*|pint)\._vendor (import (appdirs))/\2/' \
+ -e 's/^(from )(\.*|pint)\._vendor( import (flexcache))/\1\4\3/'
%generate_buildrequires
# We omit the “uncertainties” extra because python-uncertainties is not yet
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=178920851344.1.14057160767025872933.rpms-python-pint-799b93479ac7@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