public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Lumir Balhar <lbalhar@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/pylint] rawhide: Update patch for compatibility with Python 3.15 beta 1
Date: Fri, 12 Jun 2026 15:43:24 GMT [thread overview]
Message-ID: <178127900415.1.2486575977893739001.rpms-pylint-659656cc4e51@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/pylint
Branch : rawhide
Commit : 659656cc4e511295955e1a31737039f9c724a27e
Author : Lumir Balhar <lbalhar@redhat.com>
Date : 2026-06-06T16:27:24+02:00
Stats : +2/-14 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/pylint/c/659656cc4e511295955e1a31737039f9c724a27e?branch=rawhide
Log:
Update patch for compatibility with Python 3.15 beta 1
---
diff --git a/python315.patch b/python315.patch
index ae591ae..c832e73 100644
--- a/python315.patch
+++ b/python315.patch
@@ -44,7 +44,7 @@ new file mode 100644
index 0000000..6b687c7
--- /dev/null
+++ b/tests/functional/u/unspecified_encoding_py38.315.txt
-@@ -0,0 +1,40 @@
+@@ -0,0 +1,41 @@
+unspecified-encoding:13:0:13:14::Using open without explicitly specifying an encoding:HIGH
+unspecified-encoding:14:0:14:20::Using open without explicitly specifying an encoding:HIGH
+unspecified-encoding:15:0:15:20::Using open without explicitly specifying an encoding:HIGH
@@ -65,6 +65,7 @@ index 0000000..6b687c7
+unspecified-encoding:68:0:68:50::Using open without explicitly specifying an encoding:HIGH
+unspecified-encoding:75:0:75:35::Using open without explicitly specifying an encoding:HIGH
+unspecified-encoding:76:0:76:50::Using open without explicitly specifying an encoding:HIGH
++unspecified-encoding:77:0:77:61::Using open without explicitly specifying an encoding:HIGH
+unspecified-encoding:81:0:81:21::Using open without explicitly specifying an encoding:HIGH
+unspecified-encoding:82:0:82:25::Using open without explicitly specifying an encoding:HIGH
+unspecified-encoding:83:0:83:25::Using open without explicitly specifying an encoding:HIGH
@@ -85,19 +86,6 @@ index 0000000..6b687c7
+unspecified-encoding:183:0:183:29::Using open without explicitly specifying an encoding:INFERENCE
+unspecified-encoding:186:0:186:44::Using open without explicitly specifying an encoding:INFERENCE
+unspecified-encoding:193:0:193:34::Using open without explicitly specifying an encoding:INFERENCE
-diff --git a/tests/functional/u/unspecified_encoding_py38.py b/tests/functional/u/unspecified_encoding_py38.py
-index 9ff2fd7..0c7a289 100644
---- a/tests/functional/u/unspecified_encoding_py38.py
-+++ b/tests/functional/u/unspecified_encoding_py38.py
-@@ -74,7 +74,7 @@ Path(FILENAME).write_text("string", encoding="utf8")
- LOCALE_ENCODING = None
- Path(FILENAME).write_text("string") # [unspecified-encoding]
- Path(FILENAME).write_text("string", encoding=None) # [unspecified-encoding]
--Path(FILENAME).write_text("string", encoding=LOCALE_ENCODING) # [unspecified-encoding]
-+Path(FILENAME).write_text("string", encoding=LOCALE_ENCODING) # <3.15: [unspecified-encoding]
-
- LOCALE_ENCODING = locale.getlocale()[1]
- Path(FILENAME).open("w+b")
diff --git a/tests/testutils/test_functional_testutils.py b/tests/testutils/test_functional_testutils.py
index 2b1574e..6691e17 100644
--- a/tests/testutils/test_functional_testutils.py
reply other threads:[~2026-06-12 15:43 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=178127900415.1.2486575977893739001.rpms-pylint-659656cc4e51@fedoraproject.org \
--to=lbalhar@redhat.com \
--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