Yeah I checked aiohttp to see if things where okay but the badge showed that the build was breaking, when I check Travis it complained about the same thing.
Funny enough it seems that home-assistant seem to have fixed the issue by pinning the old idna version, I haven't thought about it since we weren't using idna directly. I will keep that in mind haha
--EDIT--
Also, it seems that aiohttp fixed the issue by following the same strategy.
I haven't thought about it since we weren't using idna directly. I will keep that in mind haha
That's a good strategy. You add the indirect dependency to your code, pin it, wait until your direct dependency solves the issue and then remove the indirect one. Until the next time then :D
Yeah I checked aiohttp to see if things where okay but the badge showed that the build was breaking, when I check Travis it complained about the same thing.
Funny enough it seems that home-assistant seem to have fixed the issue by pinning the old idna version, I haven't thought about it since we weren't using idna directly. I will keep that in mind haha
--EDIT--
Also, it seems that aiohttp fixed the issue by following the same strategy.
That's a good strategy. You add the indirect dependency to your code, pin it, wait until your direct dependency solves the issue and then remove the indirect one. Until the next time then :D
BTW do you use aiohttp directly?
Yeah I never thought about doing that, I think I will update my post with this for the future haha
Yeah we use aiohttp directly why?
Because it would be great if you wrote an article on using aiohttp day by day :)
Great idea I will work something out :D