public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/python-cffi] rawhide: Update to 2.1.1
Date: Wed, 12 Aug 2026 12:37:31 GMT	[thread overview]
Message-ID: <178653825193.1.5187154673126294298.rpms-python-cffi-c0e0c9e21e0c@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/python-cffi
            Branch : rawhide
            Commit : c0e0c9e21e0c07aec11ad22b6334b9af80f9a83c
            Author : Miro Hrončok <miro@hroncok.cz>
            Date   : 2026-08-11T13:36:13+02:00
            Stats  : +3/-127 in 3 file(s)
            URL    : https://src.fedoraproject.org/rpms/python-cffi/c/c0e0c9e21e0c07aec11ad22b6334b9af80f9a83c?branch=rawhide

            Log:
            Update to 2.1.1

- Fixes: rhbz#2510811

---
diff --git a/224.patch b/224.patch
deleted file mode 100644
index 51165f7..0000000
--- a/224.patch
+++ /dev/null
@@ -1,121 +0,0 @@
-From 615c2a47375bfebc388652691d7641ad610e183f Mon Sep 17 00:00:00 2001
-From: Eli Bendersky <eliben@gmail.com>
-Date: Sat, 24 Jan 2026 08:42:49 -0800
-Subject: [PATCH 1/2] Make test_parsing more resilient to changes in pycparser
-
-Several tests expect precise error messages from pycparser, which pycparser
-doesn't guarantee. While testing CFFI with pycparser 3.0, some tests needed
-to be made more resilient. I've used the .startswith() approach already used
-in this file, instead of exact string matching.
-
-Ref #223
----
- testing/cffi0/test_parsing.py | 18 +++++++++---------
- 1 file changed, 9 insertions(+), 9 deletions(-)
-
-diff --git a/testing/cffi0/test_parsing.py b/testing/cffi0/test_parsing.py
-index 8d4dd016..d0f466bd 100644
---- a/testing/cffi0/test_parsing.py
-+++ b/testing/cffi0/test_parsing.py
-@@ -197,7 +197,7 @@ def test_dont_remove_comment_in_line_directives():
- 
-         some syntax error here
-     """)
--    assert str(e.value) == "parse error\nbaz.c:9:14: before: syntax"
-+    assert str(e.value).startswith("parse error\nbaz.c:9:")
-     #
-     e = pytest.raises(CDefError, ffi.cdef, """
-         #line 7 "foo//bar.c"
-@@ -205,21 +205,21 @@ def test_dont_remove_comment_in_line_directives():
-         some syntax error here
-     """)
-     #
--    assert str(e.value) == "parse error\nfoo//bar.c:8:14: before: syntax"
-+    assert str(e.value).startswith("parse error\nfoo//bar.c:8:")
-     ffi = FFI(backend=FakeBackend())
-     e = pytest.raises(CDefError, ffi.cdef, """
-         \t # \t 8 \t "baz.c" \t
- 
-         some syntax error here
-     """)
--    assert str(e.value) == "parse error\nbaz.c:9:14: before: syntax"
-+    assert str(e.value).startswith("parse error\nbaz.c:9:")
-     #
-     e = pytest.raises(CDefError, ffi.cdef, """
-         # 7 "foo//bar.c"
- 
-         some syntax error here
-     """)
--    assert str(e.value) == "parse error\nfoo//bar.c:8:14: before: syntax"
-+    assert str(e.value).startswith("parse error\nfoo//bar.c:8:")
- 
- def test_multiple_line_directives():
-     ffi = FFI(backend=FakeBackend())
-@@ -233,7 +233,7 @@ def test_multiple_line_directives():
-         #line 8 "yadda.c"
-         extern int zz;
-     """)
--    assert str(e.value) == "parse error\nbaz.c:7:14: before: syntax"
-+    assert str(e.value).startswith("parse error\nbaz.c:7:")
-     #
-     e = pytest.raises(CDefError, ffi.cdef,
-     """ # 5 "foo.c"
-@@ -245,7 +245,7 @@ def test_multiple_line_directives():
-         # 8 "yadda.c"
-         extern int zz;
-     """)
--    assert str(e.value) == "parse error\nbaz.c:7:14: before: syntax"
-+    assert str(e.value).startswith("parse error\nbaz.c:7:")
- 
- def test_commented_line_directive():
-     ffi = FFI(backend=FakeBackend())
-@@ -262,7 +262,7 @@ def test_commented_line_directive():
-         some syntax error
-     """)
-     #
--    assert str(e.value) == "parse error\nbar.c:9:14: before: syntax"
-+    assert str(e.value).startswith("parse error\nbar.c:9:")
-     e = pytest.raises(CDefError, ffi.cdef, """
-         /*
-         # 5 "foo.c"
-@@ -275,7 +275,7 @@ def test_commented_line_directive():
-         */
-         some syntax error
-     """)
--    assert str(e.value) == "parse error\nbar.c:9:14: before: syntax"
-+    assert str(e.value).startswith("parse error\nbar.c:9:")
- 
- def test_line_continuation_in_defines():
-     ffi = FFI(backend=FakeBackend())
-@@ -365,7 +365,7 @@ def test_unknown_name():
-     e = pytest.raises(CDefError, ffi.cast, "foobarbazunknown*", 0)
-     assert str(e.value).startswith('cannot parse "foobarbazunknown*"')
-     e = pytest.raises(CDefError, ffi.cast, "int(*)(foobarbazunknown)", 0)
--    assert str(e.value).startswith('cannot parse "int(*)(foobarbazunknown)"')
-+    assert str(e.value).startswith("in expression arg 1: unknown type 'foobarbazunknown'")
- 
- def test_redefine_common_type():
-     prefix = "" if sys.version_info < (3,) else "b"
-
-From 02d4417c84229d2eab426b9ab755ac1c435a333e Mon Sep 17 00:00:00 2001
-From: Eli Bendersky <eliben@gmail.com>
-Date: Sat, 24 Jan 2026 14:51:01 -0800
-Subject: [PATCH 2/2] Loosen error message assertion even more
-
----
- testing/cffi0/test_parsing.py | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/testing/cffi0/test_parsing.py b/testing/cffi0/test_parsing.py
-index d0f466bd..3e47bcdd 100644
---- a/testing/cffi0/test_parsing.py
-+++ b/testing/cffi0/test_parsing.py
-@@ -365,7 +365,7 @@ def test_unknown_name():
-     e = pytest.raises(CDefError, ffi.cast, "foobarbazunknown*", 0)
-     assert str(e.value).startswith('cannot parse "foobarbazunknown*"')
-     e = pytest.raises(CDefError, ffi.cast, "int(*)(foobarbazunknown)", 0)
--    assert str(e.value).startswith("in expression arg 1: unknown type 'foobarbazunknown'")
-+    assert 'foobarbazunknown' in str(e.value)
- 
- def test_redefine_common_type():
-     prefix = "" if sys.version_info < (3,) else "b"

diff --git a/python-cffi.spec b/python-cffi.spec
index a61e2bc..bc992df 100644
--- a/python-cffi.spec
+++ b/python-cffi.spec
@@ -1,5 +1,5 @@
 Name:           python-cffi
-Version:        2.0.0
+Version:        2.1.1
 Release:        %autorelease
 Summary:        Foreign Function Interface for Python to call C code
 # cffi is MIT
@@ -8,10 +8,6 @@ License:        MIT AND PSF-2.0
 URL:            https://github.com/python-cffi/cffi
 Source:         %{url}/archive/v%{version}/cffi-%{version}.tar.gz
 
-# Make test_parsing more resilient to changes in pycparser
-# Fixes test failures with pycparser 3.00, merged upstream
-Patch:          https://github.com/python-cffi/cffi/pull/224.patch
-
 BuildRequires:  python3-devel
 BuildRequires:  python3-pytest
 BuildRequires:  make
@@ -72,6 +68,7 @@ rm build/html/.buildinfo
 
 %files -n python3-cffi -f %{pyproject_files}
 %doc README.md
+%{_bindir}/cffi-gen-src
 
 %files doc
 %license LICENSE

diff --git a/sources b/sources
index 38d8a90..f7c76b9 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (cffi-2.0.0.tar.gz) = a71b74e642e11eb50e9bb4ae0e7116bdb3c4a7c9622a3766d84506fa7994c02e09644b41b439b95ca99b0303e91891897cff38018d498eb087e0961f0ad4fb8b
+SHA512 (cffi-2.1.1.tar.gz) = 86af9771c4f8f0bfb129e63cb263dbaf2f32bb755e056fa04bc4cdd32eee4392634a866dd930263e6eeb011f81ee2bd90f9e6602adf016c80e124bdbfbb62c38

                 reply	other threads:[~2026-08-12 12:37 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=178653825193.1.5187154673126294298.rpms-python-cffi-c0e0c9e21e0c@fedoraproject.org \
    --to=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