concurrent rendering name inconsistent #1202
Replies: 3 comments
-
That's a bug. Do you want to PR to change it to ASYNC? |
Beta Was this translation helpful? Give feedback.
-
I'm going to hold off on messing with concurrent rendering as it doesn't benefit me. I don't do any I/O calls in the render logic under normal circumstances and all hooks are already async. The cpu portion of the rendering isn't actually in parallel because of how asyncio works. |
Beta Was this translation helpful? Give feedback.
-
I created a discussion around the concurrent rendering. Basically, I don't want to be the one to fix this because I feel like it's endorsing it when I'm not sure its providing value yet. If it does provide value, then I suggest just having one code route. My presumption is that this is a config option since it may have bugs? |
Beta Was this translation helpful? Give feedback.
-
All references to concurrent rendering use
ASYNC
and even the instructions in the changelog say to use the environment variableREACTPY_ASYNC_RENDERING=true
but its actuallyREACTPY_CONCURRENT_RENDERING=true
Beta Was this translation helpful? Give feedback.
All reactions