Conner Nilsen

@hauntsaninja no problem, I get that you're trying to keep things private for your use case 😄. In the future, if you would prefer, we can also send semi-sensitive stuff...

Alright, I have two PRs that should fix different parts of this: - #439 should make sure your `site-package-path` is always included in `project-excludes`. I'm still trying to figure out...

I'm hoping some of the changes I added above will help, but just to double check some stuff, can you run `pyrefly check . --verbose`, and add a couple lines...

@hauntsaninja got it. Maybe test it out once I get #440 landed too to see if that addresses any of the issues with it, especially with #439 committed. Note: #439...

@hauntsaninja Alright, I just released version 0.19.1, which might fix some of the problems you're seeing (especially when the venv is in the same directory as the rest of your...

@hauntsaninja If you try setting [`untyped-def-behavior`](https://pyrefly.org/en/docs/configuration/#untyped-def-behavior) to `skip-and-infer-return-any`, does that speed things up for you?

Sorry about the long delay, was busy with performance cycle at work and I forgot to come back to this. I just tried reproing [with your more recent setup](https://github.com/facebook/pyrefly/issues/360#issuecomment-2961409433), and...

Got it, I changed some steps in the script (venv in current directorY), thinking it wouldn't cause problems, so I'll retry using exactly what you have. I'm still waiting for...

Oh wow, I'm seeing it now. It seems to be related to having the venv located outside of the project directory, but I'm not yet sure why that would be...

My current working theory is that we keep re-querying the interpreter a ton when the venv is outside of the directory for some reason. I need to double check why...