mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@barebox.org>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@barebox.org>
Subject: [PATCH 1/3] Documentation: fix warnings during config build
Date: Fri, 10 Oct 2025 08:57:43 +0200	[thread overview]
Message-ID: <20251010065749.3141299-1-a.fatoum@barebox.org> (raw)

js_splitter_code contains backslashes that are meant for Javascript and
not for Python triggering a warning:

  conf.py:275: SyntaxWarning: invalid escape sequence '\p'
    .split(/[^\p{Letter}\p{Number}_\p{Emoji_Presentation}\-\.]+/gu)

Setting soruce_suffix to a string also seems deprecated:

  Converting `source_suffix = '.rst'` to
    `source_suffix = {'.rst': 'restructuredtext'}`.

Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
---
 Documentation/conf.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/conf.py b/Documentation/conf.py
index dfd416f7e0b2..9244bffe9e9b 100644
--- a/Documentation/conf.py
+++ b/Documentation/conf.py
@@ -35,7 +35,7 @@ extensions = []
 templates_path = ['_templates']
 
 # The suffix of source filenames.
-source_suffix = '.rst'
+source_suffix = {'.rst': 'restructuredtext'}
 
 # The encoding of source files.
 #source_encoding = 'utf-8-sig'
@@ -269,7 +269,7 @@ class DashFriendlySearchEnglish(SearchEnglish):
     # Accept words that can include 'inner' hyphens or dots
     _word_re = re.compile(r'[\w]+(?:[\.\-][\w]+)*')
 
-    js_splitter_code = """
+    js_splitter_code = r"""
 function splitQuery(query) {
     return query
         .split(/[^\p{Letter}\p{Number}_\p{Emoji_Presentation}\-\.]+/gu)
-- 
2.47.3




             reply	other threads:[~2025-10-10  6:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-10  6:57 Ahmad Fatoum [this message]
2025-10-10  6:57 ` [PATCH 2/3] scripts: container.sh: support -e for environment variables Ahmad Fatoum
2025-10-10  6:57 ` [PATCH 3/3] Documentation: add contributing section Ahmad Fatoum

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=20251010065749.3141299-1-a.fatoum@barebox.org \
    --to=a.fatoum@barebox.org \
    --cc=barebox@lists.infradead.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