I wonder whether it would be possible to have a licensing scheme that was compatible with a package manager config to help solve these problems. # new envi

I wonder whether it would be possible to have a licensing scheme that was compatible with a package manager config to help solve these problems. # new environment with explicit config pyenv virtualenv myEnv —-licensing=personal pip install some-free-package # Success vs # new environment defaults to restrictive pyenv virtualenv myEnv pip install some-free-package # failure ERROR: PACKAGE LICENSE INCOMPATIBLE WITH PIP CONFIG It would be just as much on the honor system as things are today, but I think people are generally honest. If a package I want isn’t compatible with my license config at work, I think I’m more likely to find a different package or try to get a license than I am to change my package manager confit away from the team sanctioned settings, potentially opening my employer to what I now explicitly know to be legal risk. I’m thinking about the packages I usually use and I don’t know their licenses. Pandas? Pytorch? I assume I can use them at work because everyone else does. If my package manager told me otherwise, I don’t have to be proactive.