Python packaging has historically been so bad that dotcloud invented docker in an attempt to make it usable.
Just importing doesn't seem to work for millions of people:
- https://stackoverflow.com/questions/4383571/importing-files-... (1.5m views)
- https://stackoverflow.com/questions/14132789/relative-import... (215k views)
- https://stackoverflow.com/questions/72852/how-to-do-relative... (325k views)
- https://stackoverflow.com/questions/1918539/can-anyone-expla... (100k views)
- https://stackoverflow.com/questions/1260792/import-a-file-fr... (480k views)
- https://stackoverflow.com/questions/7505988/importing-from-a... (136k views)
- https://stackoverflow.com/questions/9252543/importerror-cann... (700k views)
- https://stackoverflow.com/questions/2325923/how-to-fix-impor... (430k views)
- https://stackoverflow.com/questions/15514593/importerror-no-... (250k views)
Unless you have a Python version locally that doesn't support some features used in said .py file...
I ran into one with Go imports just the other day, and since I’m new to it, it wasn’t a 10 minute google fix.
Nested `mod`s with sometimes `pub` and then `use` for other stuff certainly seems more complex to me than `import X from P`.
Package/crate management is fairly trivial in both cases, yes. `npm i [package]` isn't exactly a difficult process either.
i don't think it's possible to do that any more with Python, the genie is out of the bottle. but you can get close with things like Black (auto-formatting) and Poetry (nicer deps mgmt and so much more). of course, how would a beginner know this? hopefully some day tools like that will become the default answers