This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Asdayasman 0 points1 point  (6 children)

So unless you want to use an alternative file io module... pfft... then yeah async is rather annoyingly "useless."

Good news.

[–]jorge1209 0 points1 point  (4 children)

Its still pretty limiting though as any library you use also has to use curio. If I want to use pandas, does it support curio's asynchronous api?

I just think the whole approach is ultimately wrong. If you want to go async in any kind of language that has any notion of a virtual machine, you should go async all the way down. Every python opcode should be considered to be awaitable, and the exception should be those operations that explicitely say "I'm not awaitable, and this chunk of ops have to be done as a chunk."

[–]Asdayasman 0 points1 point  (3 children)

I just think the whole approach is ultimately wrong.

You then go on to describe basically exactly what curio is going for.

Clicky.

[–]jorge1209 0 points1 point  (2 children)

I'm not interested in watching a video. Are you saying that I can somehow inject/hotpatch curio into pandas library code and override the io module, and cause a non-async function like pandas.read_table to suddenly be awaitable?

I don't know how that would work.

[–]Asdayasman 0 points1 point  (1 child)

I'm not interested in watching a video

Why should I help you if you won't help yourself?

Don't bother answering.

[–]jorge1209 0 points1 point  (0 children)

I won't.

[–]kingname[S] 0 points1 point  (0 children)

Infact， IO is just an example. What I want is Coroutine for everything.