-
-
Notifications
You must be signed in to change notification settings - Fork 566
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
python-construct-2.9.45 #374
Comments
The right way to do it would be to remove the pinning to a given release of construct. |
This isn't possible. Long story short: A lot of minor releases of construct broke this library in the past. We don't want to pin requirements. There is no better solution at the moment. |
What do the developers of |
I think the API has now been stabilized (due to lack of time from the maintainer), so I think we could proceed to upgrade. The problem is that when it starts to break again, we will be getting issues again everywhere (search for construct on homeassistant's issue tracker or here to see). |
with a likely stabilized construct API it would be the best choice imho to |
I had a brief conversation with syssi about this and we decided, that as the API has been stabilized we will simply go and remove the pinning for the next release. Let's hope it stays stable! |
great decision imho! thank you for heads up! :) |
Can be closed if #384 is merged. |
first of all thank you for that great project! :)
current version of python-construct on arch linux is 2.9.45, but python-miio is pinned to 'construct==2.9.41'.
just bumped the required version within my local repo and looks like python-miio works just fine with 2.9.45.
The text was updated successfully, but these errors were encountered: