From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: python3-peewee: update to 3.17.3.
Date: Thu, 25 Apr 2024 20:17:41 +0200 [thread overview]
Message-ID: <20240425181741.AA1EA201CA@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49978@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 4363 bytes --]
There's a merged pull request on the void-packages repository
python3-peewee: update to 3.17.3.
https://github.com/void-linux/void-packages/pull/49978
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
This gets rid of the following warnings upon install:
```
usr/lib/python3.12/site-packages/playhouse/migrate.py:673: SyntaxWarning: invalid escape sequence '\('
column_re = re.compile('(.+?)\((.+)\)')
usr/lib/python3.12/site-packages/playhouse/migrate.py:830: SyntaxWarning: invalid escape sequence '\]'
if re.match('%s(?:[\'"`\]]?\s|$)' % column_to_update, column):
usr/lib/python3.12/site-packages/playhouse/reflection.py:421: SyntaxWarning: invalid escape sequence '\['
begin = '(?:["\[\(]+)?'
usr/lib/python3.12/site-packages/playhouse/reflection.py:422: SyntaxWarning: invalid escape sequence '\]'
end = '(?:["\]\)]+)?'
usr/lib/python3.12/site-packages/playhouse/reflection.py:424: SyntaxWarning: invalid escape sequence '\s'
'(?:FOREIGN KEY\s*)?'
usr/lib/python3.12/site-packages/playhouse/reflection.py:425: SyntaxWarning: invalid escape sequence '\s'
'{begin}(.+?){end}\s+(?:.+\s+)?'
usr/lib/python3.12/site-packages/playhouse/reflection.py:426: SyntaxWarning: invalid escape sequence '\s'
'references\s+{begin}(.+?){end}'
usr/lib/python3.12/site-packages/playhouse/reflection.py:427: SyntaxWarning: invalid escape sequence '\s'
'\s*\(["|\[]?(.+?)["|\]]?\)').format(begin=begin, end=end)
usr/lib/python3.12/site-packages/playhouse/reflection.py:437: SyntaxWarning: invalid escape sequence '\('
column_type = re.sub('\(.+\)', '', raw_column_type)
usr/lib/python3.12/site-packages/playhouse/reflection.py:825: SyntaxWarning: invalid escape sequence '\('
match_obj = re.match('^(.+?\()(.+)(\).*)', sql)
usr/lib/python3.12/site-packages/playhouse/migrate.py:673: SyntaxWarning: invalid escape sequence '\('
column_re = re.compile('(.+?)\((.+)\)')
usr/lib/python3.12/site-packages/playhouse/migrate.py:830: SyntaxWarning: invalid escape sequence '\]'
if re.match('%s(?:[\'"`\]]?\s|$)' % column_to_update, column):
usr/lib/python3.12/site-packages/playhouse/reflection.py:421: SyntaxWarning: invalid escape sequence '\['
begin = '(?:["\[\(]+)?'
usr/lib/python3.12/site-packages/playhouse/reflection.py:422: SyntaxWarning: invalid escape sequence '\]'
end = '(?:["\]\)]+)?'
usr/lib/python3.12/site-packages/playhouse/reflection.py:424: SyntaxWarning: invalid escape sequence '\s'
'(?:FOREIGN KEY\s*)?'
usr/lib/python3.12/site-packages/playhouse/reflection.py:425: SyntaxWarning: invalid escape sequence '\s'
'{begin}(.+?){end}\s+(?:.+\s+)?'
usr/lib/python3.12/site-packages/playhouse/reflection.py:426: SyntaxWarning: invalid escape sequence '\s'
'references\s+{begin}(.+?){end}'
usr/lib/python3.12/site-packages/playhouse/reflection.py:427: SyntaxWarning: invalid escape sequence '\s'
'\s*\(["|\[]?(.+?)["|\]]?\)').format(begin=begin, end=end)
usr/lib/python3.12/site-packages/playhouse/reflection.py:437: SyntaxWarning: invalid escape sequence '\('
column_type = re.sub('\(.+\)', '', raw_column_type)
usr/lib/python3.12/site-packages/playhouse/reflection.py:825: SyntaxWarning: invalid escape sequence '\('
match_obj = re.match('^(.+?\()(.+)(\).*)', sql)
```
#### Testing the changes
- I tested the changes in this PR: **NO**, ~I have yet to test this.~ I don't really know how to test this well. All arches build, so that's that. It doesn't have that many dependants that I could test.
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
cc @jnbr (by the way, are you still an active maintainer?)
next prev parent reply other threads:[~2024-04-25 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 8:53 [PR PATCH] " meator
2024-04-25 17:19 ` cinerea0
2024-04-25 17:32 ` [PR PATCH] [Updated] " meator
2024-04-25 17:35 ` meator
2024-04-25 18:17 ` cinerea0
2024-04-25 18:17 ` cinerea0 [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-20 20:42 [PR PATCH] " jason1987d
2024-04-25 17:08 ` [PR PATCH] [Merged]: " cinerea0
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=20240425181741.AA1EA201CA@inbox.vuxu.org \
--to=cinerea0@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).