Steve Howell [mailto:showell@...] wrote:
> I'd like to schedule a meeting for 11pm EST to discuss the
> PyYaml approach to putting dates into data files.
Is there a time pressure here?
> Here is the solution that I propose:
> 1) By default, PyYaml will treat 2002-11-02 (unquoted) as a
> simple string. This should make Mike happy.
> 2) I will cast a vote for Oren's option #3 from a prior
> email: "(3) Drop date and time altogether and live with YAML
> core types providing no solution to this issue." Oren and
> Brian both seem to like the idea, so the YAML standards body
> should be happy.
> 3) Give Clark an easy hook to convert strings to mxDateTime
> for use in his application. Although the hook API would be
> part of the PyYaml library, conceptually the hook
> implementation would be operating at a layer above the YAML
> parser and below Clark's application. This will hopefully
> keep Clark happy.
Hopefully. I have no problem with it. Just make sure Clark does give his OK
- you may have to call him to get him on the IRC session.
BTW, if you do have this session, you may also want to consider the #TAB
issue as well. At this point I'm not certain what my position on it is - if
you reach a strong consensus I'll very probably go with it.
From: Steve Howell <showell@zi...> - 2002-09-04 15:38:06
From: "Oren Ben-Kiki" <orenbk@...>
> Steve Howell [mailto:showell@...] wrote:
> > I'd like to schedule a meeting for 11pm EST to discuss the
> > PyYaml approach to putting dates into data files.
> Is there a time pressure here?
Not really. It would be nice to iron this out before the weekend, because I
will probably have some time work on the code then.
If you're interested in this issue, just let me know a good time, and I'll try
to set something up.