There may be several options. If you package your script into a toolbox you could reference your toolbox (and tool) via ArcObjects as such:

 IGeoProcessor2 gp = new GeoProcessorClass();
 gp.AddToolbox(@"C:\YourPath\YourToolbox.tbx");
 parameters.Add(@"C:\YourPath\ParamsIfYouHaveThem.gdb\ParamFC");
 gp.Execute("NameOfYourToolInsideReferencedToolbox", parameters, null);


Read more on this method here: http://help.arcgis.com/en/sdk/10.0/arcobjects_net/conceptualhelp/index.html#executingCustomTool

Or you could try this route:

System.Diagnostics.Process proc = new System.Diagnostics.Process();
proc.StartInfo.FileName = @"C:\path\toYour\script.py";
proc.StartInfo.UseShellExecute = true;
proc.Start()


which is mentioned here: http://forums.esri.com/Thread.asp?c=93&amp;f=993&amp;t=276632

Running ArcPy script from ArcObjects?
Just as universal arrows can be characterized as initial objects of some appropriate comma category, and (co)limits can be characterized as (initial) terminal objects of the appropriate (co)cone category, is there some (and if so, what is the) appropriate category for which, given a functor with a left/right adjoint, we can characterize said adjoint as its initial/terminal object? My goal in this is to characterize [initial objects, universals, limits, adjunctions] all as examples of each other.
