this post was submitted on 28 Oct 2026
83 points (100.0% liked)
Programming
29103 readers
365 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.