Closed timkpaine closed 3 days ago
We can change this, but it's API breaking. If we do, we should also do this for the other handler types and remove the try
/except
import logic as it swallows important errors sometimes.
Why is a properly constrained virtual env not the appropriate solution?
Why is a properly constrained virtual env not the appropriate solution?
One might very reasonably want tornado in the environment, but not have it imported if not used. I have photoshop on my computer, I'd rather not have it open every time I use slack.
Fixed in #2754, released in v3.1.0
I have a FastAPI-based webserver that I want to ensure my import time and memory footprint is minimized. I see that
tornado
is being imported, even though I'm not using tornado.Steps to Reproduce:
Expected Result:
Actual Result:
Environment:
3.0+
Additional Context: