Skip to content

bump libuv to 1.46.0 #554

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

Closed
wants to merge 4 commits into from
Closed

Conversation

dulmandakh
Copy link
Contributor

@dulmandakh dulmandakh commented Aug 11, 2023

there are many bug fixes and improvements, like io_uring support https://www.phoronix.com/news/libuv-io-uring

@dulmandakh dulmandakh marked this pull request as draft August 11, 2023 14:25
@achimnol
Copy link
Contributor

achimnol commented Sep 9, 2023

Would this enable writing true async file I/O implementation aside the current thread-pool based solutions such as aiofiles? 👀
Since there is no official AbstractEventLoop interface to offer async file I/O yet, I think uvloop may need to define additional methods to expose the underlying libuv's file I/O APIs and write a high-level wrapper as a separate module or package.

@dulmandakh
Copy link
Contributor Author

dulmandakh commented Sep 9, 2023

Would this enable writing true async file I/O implementation aside the current thread-pool based solutions such as aiofiles? 👀
Since there is no official AbstractEventLoop interface to offer async file I/O yet, I think uvloop may need to define additional methods to expose the underlying libuv's file I/O APIs and write a high-level wrapper as a separate module or package.

I expect that it'll make networking much faster for Python.

@achimnol
Copy link
Contributor

achimnol commented Sep 14, 2023

Would this enable writing true async file I/O implementation aside the current thread-pool based solutions such as aiofiles? 👀
Since there is no official AbstractEventLoop interface to offer async file I/O yet, I think uvloop may need to define additional methods to expose the underlying libuv's file I/O APIs and write a high-level wrapper as a separate module or package.

I expect that it'll make networking much faster for Python.

That will be also an expected effect, but what I'm looking forward to see is the native async operations on disk file I/O without using thread pools.

@fantix
Copy link
Member

fantix commented Oct 15, 2023

Thank you for the PR! I'm closing this one as #571 is merged. Regarding io_uring-based file I/O, another Python package as a uvloop extension is probably the most feasible way to implement it - I'm open to adding libuv-specific Cython APIs to support extensions.

@fantix fantix closed this Oct 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants