It's clearly not designed for doing anything advanced, though: it's not like you can get access to platform-specific APIs outside of the basics without doing a lot of work.
You have the stdlib ctypes of course, but also pypy's cffi for an even better story.
We even have specialized ready to use tools for those, such as pywin32 to manipulate the windows api and registry, pyqt to leverage the c++ qt lib and all it's tooling, or watchdog to survey file changes, using the native api when possible.
In fact, mac and linuxes implement natively of lot of tools in their os for this reason.
There is also a reason it's one of the few languages allowed in prod at google. It's the best at nothing, but it's damn good at most things.
Not something I would call seamless.
> pyqt to leverage the c++ qt lib and all it's tooling
This isn't native.
> mac and linuxes implement natively of lot of tools in their os for this reason
Generally command line scripts, which is something that Python is good at.
> There is also a reason it's one of the few languages allowed in prod at google.
What Google allows in production has only an oblique relevance to whether it should be used for a specific task.
Can you explain how platform-specific stuff takes "a lot of work" with Python, and wouldn't with some other language that is not Python?
Sure, just look at a modern Cocoa app written in Swift, or Android one in Java, and compare it to the amount of work you'd have to do to shoehorn Python in there.
About 15.5 years ago while I was still a grad student, I released a (horribly designed, mostly self-experimentation) editor in Python + wxPython that I initially wrote to run on Windows. I didn't run it regularly in Linux or OS X until 2008, and it all just worked. OS X was a little laggy with my editor, but hey, write once run on 3 platforms.
Python is really solid on multi-platform, because there are so many Python users already using every platform that want to bring Python there.