-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SyntaxWarning: invalid escape sequence '\s' #53
Comments
The SyntaxWarning is new to Python 3.12 and I've been getting the same warning too. I agree a PR here would make sense (with the obvious disclaimer that I'm not the maintainer of the package, just a fellow user). |
@vEnhance , let's wait for some of the maintainers to reply. |
It's very unlikely. This project has been abandoned for a while now (see #47). Bye 👋 |
I noticed it too (actually I was questioning what the old .archey3.cfg file was doing in my user home folder, and if I could clean things up, and that made me searching further for this thing on my system). Turns out in my case, it was also still sitting on my Arch Linux system, but in the case I have installed it from the official Arch repos (no idea), it's no longer there either. |
It used to be in the main repository but got orphaned and then dropped down to AUR about six weeks ago: A few weeks ago I actually adopted the AUR package and then patched the issue at https://aur.archlinux.org/cgit/aur.git/tree/py312-syntax-warning.patch?h=archey3, but it would of course be better to have that change merged upstream. But that requires the maintainer. |
Has something recently changed in Python? I've not consciously changed anything on my system that could affect archey3 the way I describe below.
Whenever I execute
archey3
I get this warning before the usual output:the lines are these
archey3/archey3
Lines 332 to 333 in ac68752
and this
archey3/archey3
Line 697 in ac68752
and prepending
r
to the first"string"
of both lines solves the problem.I can make a PR if this project is still alive.
The text was updated successfully, but these errors were encountered: