Plex: SyntaxWarning: invalid escape sequence '\.' """

[casakampa]

The problem

After upgrading from 2024.4.b0 to b1, and from b1 to b3 (I skipped b1 > b2), I get this error in my logs:

Logger: py.warnings
Bron: components/plex/server.py:10
Eerst voorgekomen: 09:14:39 (1 gebeurtenissen)
Laatst gelogd: 09:14:39

/usr/local/lib/python3.12/site-packages/plexapi/base.py:158: SyntaxWarning: invalid escape sequence '\.' """ Load the specified key to find and build all items with the specified tag

The strange thing is, I don't use plex in home assistant, nor have I added it in the past.

What version of Home Assistant Core has the issue?

core-2024.4.0b0

What was the last working version of Home Assistant Core?

core-2024.3.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Plex

Link to integration documentation on our website

https://www.home-assistant.io/integrations/plex/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: py.warnings
Bron: components/plex/server.py:10
Eerst voorgekomen: 09:14:39 (1 gebeurtenissen)
Laatst gelogd: 09:14:39

/usr/local/lib/python3.12/site-packages/plexapi/base.py:158: SyntaxWarning: invalid escape sequence '\.' """ Load the specified key to find and build all items with the specified tag

Additional information

I only joined the beta channel to update core, supervisor and operating system are stable releases.

[home-assistant]

Hey there @jjlawren, mind taking a look at this issue as it has been labeled with an integration (plex) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of plex can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign plex Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

plex documentation
plex source
_{^{(message by IssueLinks)}}

[hmmbob]

Also seeing this on beta 3. Also, just as casakampa, I'm not even using Plex....

[jjlawren]

This is harmless, but an issue in an underlying library's docstring. It's fixed in that library's repo but no release has been published yet. I'll take care of that soon.

[jjlawren]

Although I'm not sure what is triggering this warning. I can't reproduce in my dev environment.

[hmmbob]

Although I'm not sure what is triggering this warning. I can't reproduce in my dev environment.

I've only seen it happening just at boot

[hmmbob]

Still happening on beta 7:

/usr/local/lib/python3.12/site-packages/plexapi/base.py:174: SyntaxWarning: invalid escape sequence '\d' """ Load the specified key to find and build all items with the specified tag

@joostlek can you reopen this issue? It has not been solved.

[joostlek]

Let me double check if we want to have these issues tracked in core or that we just want people to create this at the library itself.

A lot of libraries aren't maintained as well, so then it doesn't make sense for people to keep open an issue in this issue tracker while we can't really solve it.

[hmmbob]

Let me double check if we want to have these issues tracked in core or that we just want people to create this at the library itself.

A lot of libraries aren't maintained as well, so then it doesn't make sense for people to keep open an issue in this issue tracker while we can't really solve it.

There are more, similar issues tagged for the milestone

[joostlek]

I know, but that's why I want to know how we want to handle all these issues in general. I also have some warnings in my own log, so if all those warnings got an issue, it might be overkill, so I am asking some questions how we want to handle these

[jjlawren]

I see where the issue is, one invalid escape sequence in the library's docstring remains. We can reopen this one for now.