From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: signatures@kernel.org
Subject: [PATCH 3/3] Loosen compatible release identifiers for install_requires
Date: Tue, 4 May 2021 17:46:58 -0400 [thread overview]
Message-ID: <20210504214658.295563-4-konstantin@linuxfoundation.org> (raw)
In-Reply-To: <20210504214658.295563-1-konstantin@linuxfoundation.org>
From: Kyle Meyer <kyle@kyleam.com>
The install_requires entries use a compatible release operator. As an
example, "requests~=2.24.0" maps to a requirement of ">= 2.24.0 and ==
2.24.*". With the current version of requests (2.25.1), this leads to
a ContextualVersionConflict failure at runtime.
Allowing only Z to tick in version X.Y.Z seems unnecessarily strict
unless there are known problems with a particular release, and it
makes it more difficult for distributions to package b4. Drop the
trailing digit from all of the version identifiers, allowing both Y
and Z to increase.
Signed-off-by: Kyle Meyer <kyle@kyleam.com>
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
---
setup.py | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/setup.py b/setup.py
index 358e6a7..a21ec76 100644
--- a/setup.py
+++ b/setup.py
@@ -41,9 +41,9 @@ setup(
data_files = [('share/man/man5', ['man/b4.5'])],
keywords=['git', 'lore.kernel.org', 'patches'],
install_requires=[
- 'requests~=2.24.0',
- 'dkimpy~=1.0.5',
- 'dnspython~=2.0.0',
+ 'requests~=2.24',
+ 'dkimpy~=1.0',
+ 'dnspython~=2.0',
],
python_requires='>=3.6',
entry_points={
--
2.30.2
next prev parent reply other threads:[~2021-05-04 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 21:46 [PATCH 0/3] Refactored code roundtrip via signatures Konstantin Ryabitsev
2021-05-04 21:46 ` [PATCH 1/3] Add -f to "b4 mbox" to filter dupes Konstantin Ryabitsev
2021-05-04 21:46 ` [PATCH 2/3] Save to/cc headers as-is for tracking Konstantin Ryabitsev
2021-05-04 21:46 ` Konstantin Ryabitsev [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-03 21:53 [PATCH 0/3] One more test with openpgp-sha256 Konstantin Ryabitsev
2021-05-03 21:53 ` [PATCH 3/3] Loosen compatible release identifiers for install_requires Konstantin Ryabitsev
2021-05-03 15:48 [PATCH 0/3] Another test, with ed25519-sha256 Konstantin Ryabitsev
2021-05-03 15:48 ` [PATCH 3/3] Loosen compatible release identifiers for install_requires Konstantin Ryabitsev
2021-05-03 15:37 [PATCH 0/3] Test with new signature scheme Konstantin Ryabitsev
2021-05-03 15:37 ` [PATCH 3/3] Loosen compatible release identifiers for install_requires Konstantin Ryabitsev
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=20210504214658.295563-4-konstantin@linuxfoundation.org \
--to=konstantin@linuxfoundation.org \
--cc=signatures@kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).