On Wed, Apr 9, 2008 at 10:15 PM, Bob Ippolito [EMAIL PROTECTED] wrote:
That sounds like a really bad idea, if there is an option to change
the behavior it shouldn't live in module state.
Would you rather have strictness controls as parameters? demjson
currently has seventeen of those. Maybe
On Wed, Apr 9, 2008 at 11:01 PM, John Millikin [EMAIL PROTECTED] wrote:
On Wed, Apr 9, 2008 at 10:15 PM, Bob Ippolito [EMAIL PROTECTED] wrote:
That sounds like a really bad idea, if there is an option to change
the behavior it shouldn't live in module state.
Would you rather have
John Millikin wrote:
On Wed, Apr 9, 2008 at 10:15 PM, Bob Ippolito [EMAIL PROTECTED] wrote:
That sounds like a really bad idea, if there is an option to change
the behavior it shouldn't live in module state.
Would you rather have strictness controls as parameters? demjson
currently has
[Bob]
simplejson would give you an error and tell you exactly where the
problem was,
Another good point.
Other JSON modules should follow simplejson's lead, and provide access
to the location in the document where the lexical or parse error
occurred, so that the offending document can be
Bob Ippolito wrote:
On Wed, Apr 9, 2008 at 8:04 PM, John Millikin [EMAIL PROTECTED] wrote:
For exception by default behavior, the library can call
warnings.simplefilter (error, JSONWarning) on initialization. Then
we just define various subclasses of JSONWarning for the different
warning
