Thanks, Martin! FYI - I just noticed it doesn't look like github has a tag for this release yet.
-Aaron On Mar 20 14:36, Martin Blais wrote: > 2021-03-20 > > - Fixed #639: Released 2.3.4. > > > 2021-01-09 > > - Fixed bug in booking that assumed number is set on cost. I did this while > running booking manually on entries freshly created on an importer > (never ahd > done that before, will be customary in v3). > > > 2021-01-08 > > - Fixed recently introduced bug with the export script that reordered the > columns. > - Fixed bug with printer leaving trailing whitespace. Was annoying. > > > 2020-12-20 > > - Merged half of branch pr128_seltzered_beanpriceupdate on this side of > Beancount. The other side will be patched to > http://github.com/beancount/beanprice. This adds some trimming functions > to > beancount.ops.lifetimes. > > > 2020-12-14 > > - Fixed #588: Catch more narrow exceptions from plugins and render full > stack > when caught. > > > 2020-11-25 > > - Fixed #584 - a bug which was occurring because a pathological example > using a > very large precision was used in inferring the precision of a currency > and a > subsequent attempt to quantize a large number exceeded the default > precision. > > > 2020-11-22 > > - Fixed bug in parser.parse_file() which when passed a filename in would > leave > the file unclosed. > - Fixed latent bug with key/value parsing (incorrect grammar rule, was > working > anyway somehow). > - Internal changes to lexer and parser to minimize diffs with ongoing work > in > 'master' / C++ scanner/parser. > > > 2020-11-17 > > - Made it legal to insert a balance entry after account closure. It is a > common > case that transactions happen on the last day of an account and the > balance > directive operates at the beginning of the day. It was arguable whether > directives should be allowed after closure; notes and documents were > allowed > because statements and phone calls may still occur after an account is > closed, but I suppose you can make the argument that a statement balance > can > also occur at a later date, so voila, make it legal. You still cannot > post > transactions to a closed account, which is the thing that really matters. > > > 2020-11-15 > > - Render the tolerance in Balance directives (merged from Aaron Lindsay). > > > 2020-11-01 > > - In the process of removing dependencies to the beancount.ops.holdings > module, > significantly sped up the net-worth-over-time script by using simple > aggregation to an inventory (which is how it should be done). > - Allow balance_by_account() method to compress positions that aren't > booked, > as an option. > - Added split() method to Inventory, like segregate_units but with no > constraints. > - Fixed #255: Added a new beancount.core.prices.project() method to project > prices to another cost currency. > > > ---------- Forwarded message --------- > From: Tomasz Zurkowski <[email protected]> > Date: Sat, Mar 20, 2021 at 6:52 AM > Subject: [beancount/beancount] Bump v2 to next minor version. (#639) > To: beancount/beancount <[email protected]> > Cc: Subscribed <[email protected]> > > > Would it be possible to bump v2 to 2.3.4 and upload it to pypi? The > beanprice repo depends on some newer code that is not available in 2.3.3 > and makes installation hard. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/beancount/beancount/issues/639>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AACSBE2BX4VJIQCF2GX6BYLTER5AVANCNFSM4ZQJ7WGQ> > . > > -- > 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/CAK21%2BhP0m%2BY3%2Bdhe_4tDOww1gbr9j42i4yF2jw2dzqe0dTYL-g%40mail.gmail.com. -- 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/YFaYRh8oeA3D9gTq%40okra.localdomain.
