Huh, you got it exactly the wrong way around. You should use Python for sockets and the advanced things; the simple things that require computational power (not many of those in a MUDs) can be written as a C extension and loaded as a module into Python.
With Python and e.g. the Twisted framework, your entire MUD that can accept incoming connections and feed input from them to you broken down line by line is going to be at most 10 lines: inherit the twisted.protocols.telnet.Telnet object and override the processLine method. And as a bonus, you can plug in any other protocol as client or server into your MUD. Of course, Twisted is also an enterprise-level framework for other things you'd do in such a network server, like database-connectivity, events and callouts etc. Also doing the main thing in Python you can get full persisten for free using e.g. Cog or ZODB. Full as in after reboot, everything is still in exactly the same place.
I'm not sure what you'd want to write in C at all (unless you don't want work done but are looking for hard education). But you should do it only as a last resort when things.
This ancient project of mine can serve as an example; you need twisted and the util.py package from my homepage saved as erwutil.py somewhere. No support, but you shouldn't use it as a base for anything anyway, but feel free to steal anything from it, e.g. look at the usage of twisted.