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-urllib3] f43: Use various long options
Date: Sat, 19 Sep 2026 07:36:39 GMT [thread overview]
Message-ID: <178980339932.1.10696477854668028901.rpms-python-urllib3-084834c314fe@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-urllib3
Branch : f43
Commit : 084834c314fe1c74521b32e27306b14d0eb61630
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date : 2026-09-19T08:31:02+01:00
Stats : +5/-4 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/python-urllib3/c/084834c314fe1c74521b32e27306b14d0eb61630?branch=f43
Log:
Use various long options
[skip changelog]
---
diff --git a/python-urllib3.spec b/python-urllib3.spec
index 6672efe..cab1ff5 100644
--- a/python-urllib3.spec
+++ b/python-urllib3.spec
@@ -88,7 +88,7 @@ Recommends: python3-urllib3+socks
# Allow setuptools-scm 10+
# Upstream PR pins to <11: https://github.com/urllib3/urllib3/pull/4954
# We don't pin if we don't have to -- the build should fail if it doesn't work with future versions.
-sed -i 's/setuptools-scm>=8,<10/setuptools-scm>=8/' pyproject.toml
+sed --in-place 's/setuptools-scm>=8,<10/setuptools-scm>=8/' pyproject.toml
# Make sure that the RECENT_DATE value doesn't get too far behind what the current date is.
# RECENT_DATE must not be older that 2 years from the build time, or else test_recent_date
@@ -106,7 +106,8 @@ sed -i 's/setuptools-scm>=8,<10/setuptools-scm>=8/' pyproject.toml
# set to some time in the past, but not to far away from the present).
# Next few lines update RECENT_DATE dynamically.
recent_date=$(date --date "7 month ago" +"%Y, %_m, %_d")
-sed -i "s/^RECENT_DATE = datetime.date(.*)/RECENT_DATE = datetime.date($recent_date)/" src/urllib3/connection.py
+sed --in-place "s/^RECENT_DATE = datetime.date(.*)/RECENT_DATE = datetime.date($recent_date)/" \
+ src/urllib3/connection.py
%if %{with tests}
# Possible improvements to dependency groups
@@ -183,8 +184,8 @@ export PYTHONPATH="${hypercorndir}:%{buildroot}%{python3_sitelib}"
# even when we export the CI environment variable to increase timeouts.
k="${k-}${k+ and }not (TestHTTPProxyManager and test_tunneling_proxy_request_timeout[https-https])"
-%pytest -v -rs ${ignore-} -k "${k-}"
-%pytest -v -rs ${ignore-} -k "${k-}" --integration
+%pytest --verbose -rs ${ignore-} -k "${k-}"
+%pytest --verbose -rs ${ignore-} -k "${k-}" --integration
%endif
reply other threads:[~2026-09-19 7:36 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=178980339932.1.10696477854668028901.rpms-python-urllib3-084834c314fe@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