Joel Berendzen

I can confirm this is an issue for me. It makes the plugin totally unusable. I install a virtualenv, and within seconds it gets auto-deleted: ``OpenJDK 64-Bit Server VM warning:...

I reinstalled plugin version 1.0.1 and verified that the auto-dispose of the python interpreter does not happen with the plugin enabled.

This might be a complete red herring, but the other problem that was driving me crazy was JCEF crashing with the ReStructuredText plugin enabled due to [problems accessing the GPU](https://youtrack.jetbrains.com/issue/IDEA-248140)....

Thanks, @NickleDave, this issue is still very much alive for me. I don't think that @abn ever quite grokked my description, and yours is better. But let me try again....

I’ve switched to using “>=X” for 90% of my development work. It’s a minor nuisance editing it by hand. But I’m guessing I’m not alone in having updates of dependencies...

This problem is becoming more and more frequent in my work as a computational biologist. It is for this reason I cannot recommend poetry for any new project and project...

I strongly second this. It's ugly having to put module test dependencies when we could simply do installs with `my module[test]`. This would also make CI installs cleaner and more...

I haven't tried it against master.

Thanks for the prompt response. I'll try to get you a PR. I'm intrigued by the statement--which you are quite knowledgeable about--that asyncio schedules everything deterministically. Do you mean that...

After some testing, I have found a simple workaround, which is to simply install `pytest-trio`. The plugin gets loaded at pytest startup, and the monkey-patching gets done at that time....