[threeten-dev] Non-webrev: Part one of better date parsing

[Stephen Colebourne]

I envisage a boolean flag indicating strict/lenient, passed to
TemporalField and Chronology.

I don't think that affects this patch, which is simply locating the
builder code in the right location - ChronoField is by definition
meaningless without the chronology, so thats where the logic has to
sit.

Stephen


On 27 February 2013 19:06, roger riggs <roger.riggs at oracle.com> wrote:
> Hi Stephen,
>
> To extend it will require that the semantics of various leniency levels
> would be
> propagated to the Chronology. It would be better if the leniency
> concepts can be self contained in the parser.  In related cases, the
> dates are corrected to the "previous valid" date.
>
> Roger
>
>
> On 2/27/2013 11:37 AM, Stephen Colebourne wrote:
>>
>> Issue: #268
>> Patch: https://gist.github.com/jodastephen/5049319
>>
>> This can then be extended to "fix" the stricter Japanese era
>> requirements, and add lenient/strict resolving in general.
>>
>> Stephen
>
>