Vyas Ramasubramani

I apologize, I think in between when I first encountered the problem and when I wrote up this issue I forgot the exact problem and developed a misunderstanding of what...

I think the issue is likely a bug in either CPython that is due to some subtle interplay with build options. I reported https://github.com/python/cpython/issues/107353 a couple of years ago, and...

@wence- good call! It didn't occur to me to check that. It seems like `PYTHONSAFEPATH` is set to a nonempty value on the systems where I observe this behavior. Unfortunately,...

@ritchie46 how would you like me to proceed here? If I do figure out how to get PYTHONSAFEPATH unset, would you be open to adding that into the benchmark suite?...

> > if run directly, but it does not work if I change the run-polars target to include that. > > Including `PYTHONSAFEPATH= $(VENV)/bin/python ...` works fine for me. But...

The issue is that `PYTHONSAFEPATH` is being set in the bashrc files, so any subshell that is launched winds up having this problem. So I think the options are: 1....

Any thoughts on how best to proceed with this PR?

Nice OK that seems like a good solution, so if you don't intend to implement support for specifying requirements in the python tests section that would probably be fine given...

I don't know how much people are currently using spilling right now. Most of the times that I've heard about people using it they are people internal to NVIDIA doing...

I would consider publicly visible modules to also be part of the public API. They may not be how we most frequently interact with packages, but there are many packages...