ori on Nostr: It feels like homebrew should be able to just ignore my user packages when running ...
It feels like homebrew should be able to just ignore my user packages when running "system" Python programs
It's not clear that's the expectation. I personally would expect that 'pip install' would lead to the brew-managed python seeing the packages.
If I'm not a massive outlier, and that's at least a somewhat common user expectation, then segregating the brew managed packages from the pip managed packages would lead to a lot of user complaints.
On the other hand, making mixing them work well, such that pip and Homebrew don't step on each other's toes, seems like it could be a lot of work.
Doing nothing and letting things break, while in line with my expectations, also could lead to reputational damage: "oh, yeah, it always breaks, just delete it and reinstall"
It feels like a field of bad choices, and saying "no" may have been the most reasonable way to sidestep them.
It's not clear that's the expectation. I personally would expect that 'pip install' would lead to the brew-managed python seeing the packages.
If I'm not a massive outlier, and that's at least a somewhat common user expectation, then segregating the brew managed packages from the pip managed packages would lead to a lot of user complaints.
On the other hand, making mixing them work well, such that pip and Homebrew don't step on each other's toes, seems like it could be a lot of work.
Doing nothing and letting things break, while in line with my expectations, also could lead to reputational damage: "oh, yeah, it always breaks, just delete it and reinstall"
It feels like a field of bad choices, and saying "no" may have been the most reasonable way to sidestep them.