I like the go way: import a url. If you want to alias the namespace however you want afterward then that's your problem. It doesn't solve every single security issues, obviously. But at the very least the source of the code is more transparent.
Second option: signed packages. A warning when a package is not digitally signed.
Finally, a package repository curated by whatever language foundation. But then we are getting close to OS wide native package management...
But at the very least namespace+package name should be the norm for every single package manager out there. instead of just a package name.
So it should be "pip install code.launchpad.net/beautifulsoup", not just "pip install beautifulsoup4", if it's not possible already. And then
import "code.launchpad.net/beautifulsoup" as beautifulsoup
Second option: signed packages. A warning when a package is not digitally signed.
Finally, a package repository curated by whatever language foundation. But then we are getting close to OS wide native package management...
But at the very least namespace+package name should be the norm for every single package manager out there. instead of just a package name.
So it should be "pip install code.launchpad.net/beautifulsoup", not just "pip install beautifulsoup4", if it's not possible already. And then
in the code.