6 Commits (ebc9f092adda382297dc7b76f510aad6d5924c20)

Author	SHA1	Message	Date
James Cammarata	799159b8ee	Removing erroneous import from async_status	8 years ago
James Cammarata	b75f305079	Ensure async wrapper and status return consistent fields	8 years ago
codemeup @ Work	1e0bb94ced	Fixing compile time errors irt (, e => as e, print(), ocat now 0o not 0) exception handling for Python 3 (#3851) ... * Fixing compile time errors irt a) exception handling for Python 3 in util, also: b) problem octal usage (fixed) and c) print json_dump -> print(json_dump(xyz) ... et al * This code was not Python 2.4 compliant. Octal codes and exception handling is now working with Py 2.4, 2.6, & 3.5. * Fixing formating (or rather reverting an non 2.4 compatible change). Works in compile & runtime checking. * a) revert to use print sys.stderr not fail_json; b) fixed var name in exception * Python 3 compatible print (print >>sys.stderr will generate a TypeError - now uses sys.stderr.write instead).	9 years ago
nitzmahone	077f8131aa	mark failed async_status as finished ... Running async_status in an "until: result.finished" loop will mask a module failure (eg, traceback) with a template failure, because the fail dict doesn't include "finished" (eg, you'll see "ERROR! The conditional check 'bogus_out.finished' failed. The error was: ERROR! error while evaluating conditional: bogus_out.finished ({% if bogus_out.finished %} True {% else %} False {% endif %}"). Because the failure dict still includes "failed: true", this change has no effect on stoppage/failure reporting, it just prevents the common usage pattern from masking the underlying error message.	9 years ago
Greg DeKoenigsberg	2a5f0bde87	Proper author info for all remaining modules	10 years ago
Michael DeHaan	cec519f70e	Move internal category to utilities to remove one more category from the left hand menu, keeping it concise.	10 years ago