I'm a huge python fan.. In fact, I moved 2500 miles for a job programming mostly python.
I dont think that replacing Slick-C is a good idea.. Too much is written and working to break it.. But having Python bindings as a second option would be really cool..
To the SlickEdit Devs wanting to experiment with this:
I've interfaced libraries from C to Python in the past, and its not really that difficult... For quick prototyping, a package called ctypes (
http://starship.python.net/crew/theller/ctypes/) is good for experimenting, as it allows any app to bind to a lib.. I wouldn't use it for production use though... And I think its x86 only (at least it was)..
Another option is Pyrex (
http://www.cosc.canterbury.ac.nz/greg.ewing/python/Pyrex/) .. This is a subset of Python, and generates actaully C code to make python modules.. I have used this in production code at 2 jobs, and works quite well... Since it generates C code, it should be fairly cross platform.. (I've use it on Windows and Linux (x86 and x86_64)..) The really nice thing about this one is that if the Pyrex language wont let you do something completely, you can always tweak the C code... Pyrex has allowed me to generate bindings in days, as opposed to weeks..
Of course, you can always just write straight C code