Python is good for scripting. If you start importing and having multiple packages involved with relative imports, that’s no longer “scripting”. We have standard library and the package manager for a reason. I think you are conflicting with full fledged applications and scripting.
There are plenty of things that are “scripting”, i.e. ad-hoc admin of other projects that aren’t actually Python projects, where you want to share code between multiple scripts.
For such important projects, its not a big deal to just create Python packages. I don’t get your point. You can use Python for scripting, and you can use it for full fledged programs or share package dependencies.
My only problem is, that non standard package dependencies need to be installed by the end user, or sometimes the Python version does not match. These are the biggest issues to me.
No, it means it’s unsuitable for scripting, if you need anything more than a single file. Better than Bash of course (not hard).
Python is good for scripting. If you start importing and having multiple packages involved with relative imports, that’s no longer “scripting”. We have standard library and the package manager for a reason. I think you are conflicting with full fledged applications and scripting.
There are plenty of things that are “scripting”, i.e. ad-hoc admin of other projects that aren’t actually Python projects, where you want to share code between multiple scripts.
For such important projects, its not a big deal to just create Python packages. I don’t get your point. You can use Python for scripting, and you can use it for full fledged programs or share package dependencies.
My only problem is, that non standard package dependencies need to be installed by the end user, or sometimes the Python version does not match. These are the biggest issues to me.