Dan Allan

I like that. Two possible refinements: 1. Instead of looking for a `setup.py` check specifically where `tiled` is being imported from: ```py import importlib.util importlib.util.find_spec("tiled").origin ``` 2. Should we warn...

I would be equally happy with "warn" or "fail and tell the dev to set an env var like `TILED_MOUNTED_SOURCE` or something to suppress the error".

Oh, cool, I wasn't aware of that feature. At first glance, it looks like this would require separate client capability. For example, there are [Python libraries for it](https://www.google.com/search?q=python+requests+eventsource) but `httpx`...

I agree. And I could be persuaded to flip the order. I guess I'm just advocating that we lay track for doing both, because I think will be eventually want...

Circling back to think about this almost a year later… * The idea of using BackgroundTask for this was misguided. This is fundamentally decoupled for the HTTP and we should...

Also, at some point we discussed reusing artifacts across repeated requests but this is also complicated by permission—the way different users have different views into a node. We would also...

Summarizing discussion with @dylanmcreynolds * We can use Redis to manage both the queue of jobs and the "database" of outputs. * Output can be marked as eligible for deletion...

Thanks. I've been rethinking the interface to `ArrayAdapter` and `DataFrameAdapter`, with an eye to improving usability, and I'll factor this in to that effort.

@J-avery32 Tiled v0.1.0a67 changes the `__init__` signature of `DataFrameAdapter` and adds several more `classmethod` constructors. Does it improve the situation for your use case? Is the error message any better?

Might also be use to count socket and file system reads.