DEP Draft/Request For Shepherd: Unasyncify Codegen

As part of the process outlined in DEP 0001, I would like to start a discussion on a draft DEP I have posted here, which I am calling “Unasyncify Codegen”.

This is a strategy to generate a sync variant to async functions, similar to what is done by psycopg (though targetted at specific functions instead of entire files). I believe this would be a helpful tool for moving forward with DEP 0009.

I have discussed this idea with several members of the community, and have a reference implementation, (which I found was needed to validate the idea).

I am looking for a Shepherd for this DEP, any feedback, and (of course) any bikeshedding on naming.

3 Likes

That sounds great. I think it would help to see and discuss the reference implementation. If people feel comfortable with it, they might be more motivated to shepherd it.

2 Likes

I linked a reference implementation near the end of the DEP that handles some small examples. I am comfortable with discussing that implementation.

It doesnt show using this for queryset methods, though.

Main reason is I want to decouple the “using code gen for sync/async” discussion from “how to handle transitioning async queryset methods from being just a call to the sync variant” discussion. I plan on opening a thread in the Async subforum on this second point.

Unfortunately I do not have access to a keyboard the next 6 days so it will take me some time to write it out :joy:

Oh, my mistake then. I was looking at the thread in my mail program on the phone which didn’t show the dep link so I assumed it wasn’t published yet. Sorry for the noise.

1 Like