Bump winloop from 0.1.6 to 0.1.7

[dependabot]

Bumps winloop from 0.1.6 to 0.1.7.

Release notes

Sourced from winloop's releases.

Winloop 1.4

What's Changed

• Original shutdown_default_executor() from uvloop. by @​lschoe in Vizonex/Winloop#25
• Put all (socket)errors in form UV_ERROR. by @​lschoe in Vizonex/Winloop#24
• Found cause for issue #18. by @​lschoe in Vizonex/Winloop#26
• Add test_dealloc. Use uv_pipe to avoid bad fds. by @​lschoe in Vizonex/Winloop#27
• Winloop has more uvloop styled behaviors

Note

Some Optimizations have been temporarily removed but will be likely added back in in a future update once the move to being closer to uvloop has been completed.

Full Changelog: Vizonex/Winloop@0.1.3-v1...0.1.4-v1

Winloop 1.3

Decided I better release what we have so far since there were some interesting changes since the last updated. I have been busy with other things going on in my life as well as other projects, I might try and add some maintainers for this project in the future to help winloop stay alive.

• Dropped WinLoopPolicy Finally Please use BaseEventLoopPolicy
• Wsa Send is now used instead of our original try_write workaround C-code for it will be removed soon
• Fixed Many Bugs
• Aiodns now has support for winloop and uvloop

TODOS

• 32 Bit Wheels for windows I tried to compile a .lib File for 32 bit users and I can't seem to figure out how to make 32 bit versions of libuv
• Fix Help Side-Effect Even though I haven't made that a priority yet due to pyright existing
• Having problems making nightly workflow
• Test pyppeteer2 support (asynchronous version of selenium webdriver)

0.1.2-v1

Glad to see that this library is still alive and well, that makes me happy.

• Updated Libuv to 1.48.0 due to CVE-2024-24806 (that's bad)
• put a better warning onto WinLoopPolicy That I'm removing it in the next update (This is the final warning that you need to migrate to BaseEventLoopPolicy) If you need to retain WinLoopPolicy Importing the other class and calling

import winloop 
WinLoopPolicy = winloop.BaseEventLoopPolicy 

Will retain backwards compatibility with whatever you need it. Anyways happy programming in asyncio. :>

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)