4 ms·
PyPI packages don’t always have the same name as what you import. PIL comes to mind, as well as others I don’t remember right now.
by andreareina 4y ago
PyPI packages don’t always have the same name as what you import. PIL comes to mind, as well as others I don’t remember right now.
- felipelemos 4y agopyyaml is a good example as well
- PaulHoule 4y agoIs that really a problem? Can't you just stuff a list of deps in your script? This doesn't seem too different from the old 'setup.py' approach of Python packaging except that the 'one script' has both a 'setup.py' in it and the real script.
- andreareina 4y agoSure. I skimmed the article and only really looked at the code for the deno one so I missed that they pretty much all had some special way to declare the deps that needed to be fetched.
- rubenfiszel 4y agoIndeed: https://github.com/windmill-labs/windmill/blob/3f318b4ac41709ded4935d8aabc533c37b2591a4/backend/parsers/windmill-parser-py/src/lib.rs#L175 https://github.com/windmill-labs/windmill/blob/3f318b4ac4170... :)