Importing fails trying to open `.env` from `/dev/fd` when using `<(command)` process substitution

[shawnferry]

Posting 2.10.0
Installed via uv tool install posting

Instead of downloading my specification file and subsequently loading it I want to just load what I'm currently developing/serving. However, this fails trying to find/open a colocated .env file.

posting import <(curl -q http://127.0.0.1:8000/openapi.json)
Importing is currently an experimental feature.
Importing OpenAPI spec from '/dev/fd/63'.
...
FileNotFoundError: [Errno 2] No such file or directory: '/dev/fd/.env'

I didn't find a way to skip trying to open .env including attempts to pass --env test.env

A work around is to (use the normal and expected behavior) first write out and then load the specification.
curl -q http://127.0.0.1:8000/openapi.json -o openapi.json; posting import openapi.json; rm openapi.json

[Huaian666]

the error messages are actually helpful?? like they tell you what went wrong AND how to fix it?? wild concept. more tools should do this.