En Mon, 07 Jul 2008 12:26:28 -0300, Todd <[EMAIL PROTECTED]>
escribió:
On Jul 7, 10:17 am, Tim Golden <[EMAIL PROTECTED]> wrote:
Todd wrote:
> I ran a python script last night which connects to a matlab automation
> server via DCOM (using win32com). I expected to see the results when
> I cam
On Jul 7, 10:17 am, Tim Golden <[EMAIL PROTECTED]> wrote:
> Todd wrote:
> > I ran a python script last night which connects to a matlab automation
> > server via DCOM (using win32com). I expected to see the results when
> > I came in this morning. But apparently, not long after I left, python
> >
On Jul 7, 10:17 am, Tim Golden <[EMAIL PROTECTED]> wrote:
> Todd wrote:
> > I ran a python script last night which connects to a matlab automation
> > server via DCOM (using win32com). I expected to see the results when
> > I came in this morning. But apparently, not long after I left, python
> >
Todd wrote:
I ran a python script last night which connects to a matlab automation
server via DCOM (using win32com). I expected to see the results when
I came in this morning. But apparently, not long after I left, python
stopped. I hit enter in the console, and it started again.
Symptomati
Todd wrote:
> I ran a python script last night which connects to a matlab automation
> server via DCOM (using win32com). I expected to see the results when
> I came in this morning. But apparently, not long after I left, python
> stopped. I hit enter in the console, and it started again. I sco
Hello everyone,
I ran a python script last night which connects to a matlab automation
server via DCOM (using win32com). I expected to see the results when
I came in this morning. But apparently, not long after I left, python
stopped. I hit enter in the console, and it started again. I scoured
