'matplotlib' throws warning on 2021.12.0b3 #61336
Milestone
Comments
hmmbob
changed the title
|
Idd be interested to learn which integration is responsible for that too, thanks for logging. Seeing since several updates, and no idea as to the why either |
|
Interestingly enough, I did see this on b3, but not (yet) on b4 |
hmmbob
changed the title
|
There isn't a single direct reference to |
I do, but neither of them seem to use the lib as well. Was trying to debug this with @frenck over discord as well. Custom Components:
Yet, searching for it in my config dir does not show anything: So I did the same inside the container, and that gave me some results, including But.... I saw it once, and did not see it anymore 🤷🏻 Furthermore, I see a lot of similar deprecation warnings if I open the logs of the container: bob@debian:~$ docker logs -f homeassistantI'm remote now so can't copy a dump here, but there are more packages throwing the same warnings - they're just not showing in the HA frontend (I run |
|
Dump of |
|
Out of curiosity, can you temporarily disable all of your custom components and restart? If the logs go away, you know The issue lies in there. |
|
These are all warnings in libs from core (see for example the last two warnings, they match 1-on-1 with https://github.com/home-assistant/core/blob/dev/homeassistant/components/media_player/__init__.py#L999 ). BUT..... With "Xiaomi Cloud Map Extractor" disabled, I'm not seeing any of these deprecation warnings in other components. I've disabled all I know "custom component" doesn't get support from HA - but the warnings are thrown for core components. Is that to be expected? (And don't get me wrong, I am perfectly happy to ignore the warnings as they are only visible when running |
|
If you can access a console, install It will tell you which packages (in)directly depend on matplotlib. |
|
@hmmbob I hear what you're saying, but we can't guarantee that core "stuff" will automatically jive with custom components (kind of like how a car manufacturer warranties that your battery will start the car, but makes no guarantees about using that battery to power a grill [even though "it's a battery and should work"]). A custom component may not be aware of what core "requires". Perusing the upcoming release notes for 2021.12.0, there's a large section aimed at custom component developers: https://rc.home-assistant.io/blog/2021/12/03/release-202112/#updates-for-custom-integration-developers. Perhaps something there is relevant? |
|
Not that I can tell, but I'm no dev. Just wondering if those deprecation warnings for core components should be taken care of before we can start using Python 3.11 - as the warnings seem to indicate that this will break. |
|
The warnings for core integrations will be taken care off. |
|
Great, thanks for that. I'll just close this issue, as it is not breaking my install and only popping up due to a custom component. Thanks for checking both, appreciate it! |
|
Not for my loggings, not using that. Tbh in assumed it to be custom apex chart card but haven't checked yet |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The problem
No idea which component is responsible for this:
What version of Home Assistant Core has the issue?
core-2021.12.0b3
What was the last working version of Home Assistant Core?
core-2021.11.5
What type of installation are you running?
Home Assistant Container
Integration causing the issue
No response
Link to integration documentation on our website
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: