There are always pros and cons to what you do where and why. Is Python scripting part of the control? Is it part of the data post processing? Should it be done on the PLC itself, or on a cloud based server? Etc. Etc. The real answers are unlikely to be 'yes' or 'no', and most likely to be 'all of the above', but performance and resources will always force compromises.
We are already moving toward adding one or more forms of textual languages to future Do-more PLCs. We're certain that we'd like to have a C-like textual language for control, preferably something that could completely replace ladder. We're also certain that we'd like to have some form of scripting language for doing other things. Maybe Python is a good choice for that. We'll look into it.
As an initial offering, I could see the scripting language wanting access to PLC image register data, PLC file systems, and PLC comms (email? TCP? UDP? We'll see.). It won't be particularly fast. but for scripting that's probably fine. Anything else you absolutely need?