Hi Martin, I've been having a look around the GitHub repo and am curious to follow up on the above discussion – with the shift to v3, where is the ability to parse time at? Feel free to direct me elsewhere if there's already documentation on the new syntax / changes with v3. I've read https://beancount.github.io/docs/beancount_v3.html but haven't seen anything on the latest implementation with v3.
Thanks again for everything you (and the other contributors) do for this community, it's hugely appreciated! Kind regards, KD On Wednesday, 23 September 2020 at 15:18:03 UTC+12 [email protected] wrote: > Repo was moved to github. > ISO8601 / UTF8 will be part of v3 (prototyped, using RE/flex, works well). > > > On Tue, Sep 22, 2020 at 8:25 PM Tony Xiao <[email protected]> wrote: > >> Was the parser to support ISO8601 ever implemented btw? When I click on >> the issue it shows a link not found error. >> >> https://share.getcloudapp.com/xQuLGkw5 >> >> >> On Monday, September 10, 2018 at 1:24:52 AM UTC+8 [email protected] wrote: >> >>> >>> https://bitbucket.org/blais/beancount/issues/332/add-date-time-parsing-to-parser-and >>> >>> On Sat, Sep 8, 2018 at 4:32 PM <[email protected]> wrote: >>> >>>> Here's what I could do for you, with relatively little investment in >>>>> complexity: >>>>> - Modify the parser to support parsing a full ISO8601 datetime, as you >>>>> suggest. You get your input syntax. >>>>> - When parsing, I ignore the time portion and just use the date as-is, >>>>> but I attach the full parsed date/time object as metadata for you. >>>>> - The rest of the codebase isn't modified to depend on time anywhere. >>>>> - Then you build a plugin that will translate things as you see fit >>>>> from the metadata field. >>>>> Would that be a good first step? >>>>> >>>>> From my perspective, I'm providing you with the syntax to build what >>>>> you want, but I'm not committing to entering the time-consuming domain of >>>>> dealing with timezone issues and tickets (not supported as a core >>>>> feature). >>>>> This is a bit similar to how Python3's grammar supports type annotations >>>>> but doesn't do anything with them nor mandate how you use them otherwise >>>>> (except they happen to provide a special "typing" module). >>>>> >>>> >>>> I'd say that sounds like a workable plan. We get consistent datetime >>>> input, and access, at minimal maintenance cost. >>>> >>>> -- >>>> >>> You received this message because you are subscribed to the Google >>>> Groups "Beancount" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To post to this group, send email to [email protected]. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/beancount/d6a65c2c-3ee2-4d69-b3e2-b5c94be62645%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/beancount/d6a65c2c-3ee2-4d69-b3e2-b5c94be62645%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>> >>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Beancount" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/beancount/d83aad63-140a-434c-8bec-8a81e3ca2304n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/beancount/d83aad63-140a-434c-8bec-8a81e3ca2304n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/beancount/00665fd5-0871-4a54-9b6c-5a8a80341a5bn%40googlegroups.com.
