Closed henning-meinhardt closed 2 years ago
It seems the wheel package is missing. It is needed to generate a wheel from the source distribution. I propose you try adding wheel to the python_packages section of your addon configuration.
Just tried that but to no avail. Adding wheel
just produces the extra output
Looking in links: https://wheels.home-assistant.io/alpine-3.13/amd64/
Requirement already satisfied: wheel in /usr/lib/python3.9/site-packages (0.37.0)
The error remains:
ModuleNotFoundError: No module named 'wheel.bdist_wheel'
Also tried to add both, wheel
as well as setuptools
packages as proposed in some stackoverflow issue regarding another lib with a similar problem. Same result.
Oh man, not related, but your debug log shows a major stupid error/bug... 🤒 Alpine 3.13 wheels... we are on 3.14 already. Fixing that asap.
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!
Problem/Motivation
Using v0.7.1 of this addon I'm unable to load a recent version of the pyads library
When omitting the version number (i.e. specifying just
pyads
instead ofpyads==3.3.7
) the library is successfully loaded, however using a quite old version 3.2.(some) which misses a function added in 3.3.0 that I rely on. I tried different versions starting with 3.3.0 up to 3.3.9 (latest) but none of them can be loaded. The problem is basically that a shared system library that should be installed with the pyads library can not be found. The addon starts with an error message saying that no wheel could be built and so installation falls back to a legacy method. Later, when importing the library in an app, another error is logged saying that the system library is not available.Unfortunately I'm not a python guy so I can't see from the logs whether the problem is caused by this addon or the pyads library. So I'll address the same question also to the author of the pyads library. Maybe there is a way to manually build the shared library using the
init_commands
option. According to https://pyads.readthedocs.io/en/latest/installation.html the system library may be manually build usingBut I don't know how to leverage this in the
init_commands
Expected behavior
It should be possible to use a recent version of the pyads library (ideally 3.3.9) with this addon.
Actual behavior
Restarting the addon gives the following error in the logs:
Later when an app that imports the library is started, the log shows an other error:
Steps to reproduce
Use the following addon configuration
and create an app that imports the library, e.g.:
Proposed changes
It would be nice to have a more detailed documentation of how a specific version of a library may be referenced (using
==<version>
) - I had to google several sites until I found that by accident. Also, how exactly isinit_commands
meant to be used? What's the purpose of this, when is it executed/applied?