Python is a high level language, it is an abstract language. Python uses higher level concepts, and is more focussed on shortening code, making it potentially easier to learn (I got bored with it quickly though, I only got a quarter through the codacademy course), but when optimisation is needed you can hit a dead end quickly.
C is a low level language, C++ introduces higher level features, the most notable of which are classes. C is versatile, you have the high level concepts available if needed through the use of C++, but the low level oriented syntax and structure enable access of the hardware.
High level - higher abstraction, lower complexity. Less code written by user. Lower optimisation if working on a program that approaches the computing limits of the system.
Low level - lower abstraction, higher complexity. Greater optimisation, the trade off is that more user input is required.
If you learn python, the simplest solution is use of the Raspberry Pi. You will find that nearly all of the software that is published on the site and the magazine's is centered around Python. And of course, most utilise the GPIO ports, your connection to other external electronic components. As the hype of the Pi has been accompanied by the use of python, python has an easily integratable feature for use with the GPIO's. The only trusted libs that I can find for the Pi with C are wiring Pi and BCM2835.
But anything other than the Pi, I have not really seen other options for python-electronic interface. C on the other hand goes further. You can get the arduino, compile it and it is sent in machine code to the at328. A uc itself can standalone and have a C program compiled and run on it. So C will give you far more options in terms of electronic usage.
Beyond that you have assembly, the lowest level human readable language, machine code is like writing in the actual bytes that will be loaded into the flash. Look at the 8008 instruction set and the two are directly translatable as far as I can see, on the avr's it is slightly different and the individual bits of the bytes can be made to do different things dependant upon the instruction.
Your compiled code can be viewed as a hex file, which can be seen as one step lower than the assembly. This is human readable... If you can memorise the Opcode's! Finally, the compiled code is transfered through a serial protocol to the chip, AVR uses an ISP system.
That was probably tl;dr and a little opinionated.
