astral-sh
Lock for the duration of tool commands
Feedback from https://github.com/astral-sh/uv/pull/4501#discussion_r1655391958
Ah this is a bit annoying because now we're locking the directory before we make sure it exists, which I preferred to have happen once we knew we wanted to mutate it so we weren't creating during inspection. I'm not sure how much this matters in practice.
Ah this is a bit annoying because now we're locking the directory before we make sure it exists, which I preferred to have happen once we knew we wanted to mutate it so we weren't creating during inspection. I'm not sure how much this matters in practice.
Where is this happening in the code? I think it's ok though.
@charliermarsh you can see the CI failures are due to the lock being acquired without init first which throws an error. Previously, we waited to call init until we needed do something.