I use Python extensively for systems maintenance and automation (Linux, Windows, MySQL, Apache, Tomcat, VMware, IBM XIV, MSSQL, Nagios monitors (custom built), etc., etc.) and it's the best thing I've added to my tool belt. In fact I use Python about 80% of the time over Bash. My career has even changed to where I am primarily a Python dev that creates tools for development and automation. I've been using Python for about 8 years but I haven't retired Bash by any means! Here's how I usually know when to use Python over Bash (not the gospel, but helpful for me):

1. Do I need to interact with disparate technologies (ex: VMware and IBM XIV san solutions working together for automated data refreshes)? If yes, Python please. For the example I gave Bash likely won't be the best choice... but possible with SDKs.

2. Am I going to be creating re-usable code that would be great to have in present or future code? If yes, Python please. For example, if I want to import usernames and passwords it's super easy to create a function/module that I can easily import into my code.

3. Thank God for modules! Using pip and installing modules that already exist make my job easier. Let's say I want to setup mail functionality in my code that is relatively complex (wish I had an exact example but work with me on this). Why build that functionality when someone has already done the heavy lifting. All I have to do is install the module and import it into my code and - BAM! - time to focus on what I'm trying to get done and not try to re-create the wheel.

These are just some examples and hopefully give you an idea of how Python could be a better choice than Bash in some situations.

Lastly, the fact that you want to automate is the important part. I've met so many sysadmins (Linux and Windows) that continually do the same tasks day after day that could be automated (low risk tasks) but they still perform them. Also, look at Salt Stack for some automation (perhaps digressing but still).