Yeah, I agree, but that intermediate lookup table (a) can be in code and (b) can involve mapping local package names to url package names. One off scripts woul

Yeah, I agree, but that intermediate lookup table (a) can be in code and (b) can involve mapping local package names to url package names. One off scripts would do `from https://example.com/package https://example.com/package import bar` and bigger projects could define a translation table (e.g. in __init__.py or similar) that defines the translation table for the project. Embedding this sort of metadata in the runtime environment has a lot of advantages too: it’s a lot easier to write scripts that query and report on the metadata if you can just say something like `import deps; print( deps.getversions(‘https://example.com/foo’)` https://example.com/foo’)` One of the best parts about web development is that, for quick POC-type code, I can include a script tag that points at unpkg.com or similar and just start using any arbitrary library.