Open GoogleCodeExporter opened 9 years ago
Good idea. See also Issue 16.
What do you mean by "slows processing"? The time for each step should be
roughly the
same (for linear problems at least). I guess it's more related to adding the
next
step to a growing hdf5 file? We may need to control what get's saved at what
step...
Original comment by robert.c...@gmail.com
on 15 Apr 2010 at 1:13
"Slows processing" is wrong, rather delays solution given all the printing :)
Also - this is not a defect but an enhancement
Following your previous comment:
"You can just click into 'Add a comment and make changes' field, type nothing,
change
labels, and save changes - this should work."
I don't have these options - I think only admins do.
Original comment by freevryh...@gmail.com
on 15 Apr 2010 at 2:19
I see :)
I have added your mail (freevryheid) to project members - try changing the issue
labels now.
Original comment by robert.c...@gmail.com
on 15 Apr 2010 at 2:27
Original comment by freevryh...@gmail.com
on 15 Apr 2010 at 3:36
I guess we should add two options:
--quiet to suppress all output
--log=<file> to redirect the output to a text file
Then
simple.py ... would print messages to screen
simple.py --quiet would not produce any text output
simple.py --log=file would both print to screen and log to the file
simple.py --quiet --log=file would not print to screen and only log to the file
What do you say?
Original comment by robert.c...@gmail.com
on 19 Apr 2010 at 7:16
Assuming you agree, the above solution is implemented in the github repo.
Original comment by robert.c...@gmail.com
on 21 Apr 2010 at 7:27
Thanks Robert!
Original comment by freevryh...@gmail.com
on 21 Apr 2010 at 12:33
Migrated to http://github.com/sfepy/sfepy/issues/120
Original comment by robert.c...@gmail.com
on 30 Jan 2012 at 10:26
Original issue reported on code.google.com by
freevryh...@gmail.com
on 15 Apr 2010 at 1:09