I use bean-price / beancount.prices a lot (except the price sources) and
interested in maintaining it. Though I'd rather maintain fork of the entire
v2 codebase, because I don't see any reason to switch to v3.
On Monday, July 6, 2020 at 6:04:31 AM UTC+3, Martin Blais wrote:
> Hi,
> A per
> htt
On Sat, Jul 04, 2020 at 02:34:35AM -0400, Martin Blais wrote:
> Today I'm starting development on Beancount v3.
>
> This is going to be a pretty big change and will take a while.
> I've laid down the details in this document:
> https://docs.google.com/document/d/1qPdNXaz5zuDQ8M9uoZFyyFis7hA0G55BEf
The v3 goals & design document expresses an openness to some kind of
support for budgeting semantics.
Beancount does not support budgeting constraints explicitly, but I think it
> would be possible to extend the balance assertion semantics to cover this.
>
> The current balance assertions check
On Sat, Jul 04, 2020 at 03:09:34AM -0700, Andre Engelbrecht wrote:
> *Disclosure*: I've converted a couple of people from using webapps or
> spreadsheets to use ledger. They love ledger despite some of the
> nuance. I've been trying to move them over to beancount, but having a
> bit harder time bec
On Sat, Jul 04, 2020 at 11:48:00PM -0700, Justus Pendleton wrote:
> * Have a "bugmaster". This is a community member who isn't even necessarily
> that acquainted with the code base (perhaps not even technical at all) but
> they are engaged with the project and can help reply to new bug reports
>
> Checkout branch "v2" if you really must have those right now.
> Let me know if you care for those, at this stage I could easily fork a
copy to a separate repository (for others to maintain).
I still use bean-web from time to time, though I don't depend on it since I
have my own scripts to extrac
Well… What I’m doing is:
2020-03-06 * “Dentist A" “Dentist urgency bla..bla."
Assets:Account:Bank -100 CHF
Expenses:Me:Dentist
2020-03-06 * “Pharmacy A" “Dentist urgency meds"
Assets:Cash -10 CHF
Expenses:Me:Meds
I'm also thinking about staying on v2. It covers all my needs, I love that
it is written in python and it seems that v3 will bring too many breaking
changes.
I don't use the parts which were removed, but I think it is important to
provide at least some support for their users. The idea of split
Hello Justus,
open source projects evolve and function in very different ways from
more structured enterprises. They are often described as do-ocracies:
the control is in the hands of those that step up to do things that go
in what is perceived to be the direction of the project as a whole.
There
On 06/07/2020 03:00, Stefano Zacchiroli wrote:
> You mention you're gonna keep using flex/bison, which is for sure well
> known technology. However, the expressivity of bison grammars make it
> kinda hard to hack on existing parsers, raising the barrier for
> contributors. Have you considered switc
On Sun, Jul 5, 2020 at 11:17 PM Daniele Nicolodi wrote:
> On 05/07/2020 21:04, Martin Blais wrote:
> > Hi,
> > A
> > per
> https://docs.google.com/document/d/1qPdNXaz5zuDQ8M9uoZFyyFis7hA0G55BEfhWhrVBsfc/
> > I just deleted:
> > - bean-web (use Fava)
> > - bean-bake (unfortunately no replacement)
On Mon, Jul 6, 2020 at 3:15 AM Kirill Goncharov
wrote:
> I use bean-price / beancount.prices a lot (except the price sources) and
> interested in maintaining it. Though I'd rather maintain fork of the entire
> v2 codebase, because I don't see any reason to switch to v3.
>
v3 will take a while, b
On Mon, Jul 6, 2020 at 2:04 PM Kirill Goncharov
wrote:
> I'm also thinking about staying on v2. It covers all my needs, I love that
> it is written in python and it seems that v3 will bring too many breaking
> changes.
>
Actually I don't expect that v3 will break much. Existing syntax and
semant
On Sat, Jul 4, 2020 at 3:27 AM Martin Michlmayr wrote:
> * Martin Blais [2020-07-04 02:34]:
> > This is going to be a pretty big change and will take a while.
> > I've laid down the details in this document:
> >
> https://docs.google.com/document/d/1qPdNXaz5zuDQ8M9uoZFyyFis7hA0G55BEfhWhrVBsfc/
>
On Sat, Jul 4, 2020 at 4:20 AM Kirill Goncharov
wrote:
> Hi,
>
> What is the scope of expected breaking changes and how difficult will it
> be to migrate? I use beancount a lot and particularly interested in API
> changes in core, prices, ingest, loader and query subpackages.
>
Syntax and semant
15 matches
Mail list logo
