Henning Hasemann wrote:
> Sheldon wrote:
...
>> Does anyone know if one can resume a python script at the error point
>> after the error is corrected?
>> I have a large program that take forever if I have to restart from
>> scratch everytime. The error was the data writing a file so
Sheldon wrote:
> MRAB wrote:
>> Sheldon wrote:
>>> MRAB wrote:
Sheldon wrote:
> Hi.
>
> Does anyone know if one can resume a python script at the error point
> after the error is corrected?
> I have a large program that take forever if I have to restart from
> scratch e
MRAB wrote:
> Sheldon wrote:
> > MRAB wrote:
> > > Sheldon wrote:
> > > > Hi.
> > > >
> > > > Does anyone know if one can resume a python script at the error point
> > > > after the error is corrected?
> > > > I have a large program that take forever if I have to restart from
> > > > scratch every
On 3 Oct 2006 16:58:17 -0700, MRAB <[EMAIL PROTECTED]> wrote:
> > I like your idea Matthew but I don't know how to pickle the many
> > variables in one file. Do I need to pickle each and every variable into
> > a seperate file?
> > var1,var2
> > pickle.dump(var1,f)
> > pickle.dump(var2,f2)
> >
> U
Sheldon wrote:
> MRAB wrote:
> > Sheldon wrote:
> > > Hi.
> > >
> > > Does anyone know if one can resume a python script at the error point
> > > after the error is corrected?
> > > I have a large program that take forever if I have to restart from
> > > scratch everytime. The error was the data w
MRAB wrote:
> Sheldon wrote:
> > Hi.
> >
> > Does anyone know if one can resume a python script at the error point
> > after the error is corrected?
> > I have a large program that take forever if I have to restart from
> > scratch everytime. The error was the data writing a file so it seemed
> >
MonkeeSage wrote:
> Georg Brandl wrote:
> > As I said before, this can be done by finding out where the error is raised,
> > what the cause is and by inserting an appropriate try-except-statement in
> > the code.
>
> I could be mistaken, but I *think* the OP is asking how to re-enter the
> stack a
Sheldon wrote:
> Hi.
>
> Does anyone know if one can resume a python script at the error point
> after the error is corrected?
> I have a large program that take forever if I have to restart from
> scratch everytime. The error was the data writing a file so it seemed
> such a waste if all the data
Georg Brandl wrote:
> As I said before, this can be done by finding out where the error is raised,
> what the cause is and by inserting an appropriate try-except-statement in
> the code.
I could be mistaken, but I *think* the OP is asking how to re-enter the
stack at the same point as the exceptio
I don't know how much help this is going to be, but you could store
values in a temporary file on the hard disk and write checkpoints to
read in the data and begin from a point somewhere in the middle of the
script.
Sheldon wrote:
> Hi.
>
> Does anyone know if one can resume a python script at the
Sheldon wrote:
> Hi.
>
> Does anyone know if one can resume a python script at the error point
> after the error is corrected?
> I have a large program that take forever if I have to restart from
> scratch everytime. The error was the data writing a file so it seemed
> such a waste if all the data
Sheldon wrote:
> Does anyone know if one can resume a python script at the error point
> after the error is corrected?
> I have a large program that take forever if I have to restart from
> scratch everytime. The error was the data writing a file so it seemed
> such a waste if all the data was lost
Sheldon wrote:
> Hi.
>
> Does anyone know if one can resume a python script at the error point
> after the error is corrected?
> I have a large program that take forever if I have to restart from
> scratch everytime. The error was the data writing a file so it seemed
> such a waste if all the data
13 matches
Mail list logo
