Done. Thanks for reminding.
On Tue, Oct 18, 2022 at 5:32 AM Red S wrote:
> Also, there are references to v3 and v2 in README.md, which are now
> presumably out of date, given beangulp works fine on v2 as well? Should
> these be updated?
>
>
>
>
> --
> You received this message because you are
No plans.
On Tue, Oct 18, 2022 at 4:20 AM Red S wrote:
> It'd be helpful to release beangulp on PyPI. I'm wondering if there are
> plans to do so? Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Beancount" group.
> To unsubscribe from this group and
Also, there are references to v3 and v2 in README.md, which are now
presumably out of date, given beangulp works fine on v2 as well? Should
these be updated?
--
You received this message because you are subscribed to the Google Groups
"Beancount" group.
To unsubscribe from this group and
It'd be helpful to release beangulp on PyPI. I'm wondering if there are
plans to do so? Thanks.
--
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
On Sunday, April 10, 2022 at 8:36:21 PM UTC-7 redst...@gmail.com wrote:
> On Monday, February 1, 2021 at 10:20:34 PM UTC-8 bl...@furius.ca wrote:
>
>> - However, the bean-file, bean-extract, bean-identify tools are gone
>> (thanks Daniele!).
>> The new code will require that the configuration
On Monday, February 1, 2021 at 10:20:34 PM UTC-8 bl...@furius.ca wrote:
> - However, the bean-file, bean-extract, bean-identify tools are gone
> (thanks Daniele!).
> The new code will require that the configuration becomes a Python script.
>
> - Nothing changed in v2, everything is still there.
On 07/09/2021 13:50, kuba jamro wrote:
> Thanks for that.
>
> Now that I think about it I think I will create a wrapper for myself to
> have the --quiet option on by default.
That does not make much sense [1], but you're free too pick your poison.
[1] You have a process that does the
Thanks for that.
Now that I think about it I think I will create a wrapper for myself to
have the --quiet option on by default.
Kind regards,
Jakub.
On Mon, 6 Sep 2021 at 19:57, Daniele Nicolodi wrote:
> On 06/09/2021 20:53, Daniele Nicolodi wrote:
> > On 06/09/2021 18:11, kuba@gmail.com
On 06/09/2021 20:53, Daniele Nicolodi wrote:
> On 06/09/2021 18:11, kuba@gmail.com wrote:
>> Hi all,
>>
>> I have a question about beangulp. I've noticed that compared to
>> beancount.ingest, beangulp now produces more logging when doing an
>> extract so I wanted to question why it's there.
>
On 06/09/2021 18:11, kuba@gmail.com wrote:
> Hi all,
>
> I have a question about beangulp. I've noticed that compared to
> beancount.ingest, beangulp now produces more logging when doing an
> extract so I wanted to question why it's there.
> I see that the information logging is output on
Hi all,
I have a question about beangulp. I've noticed that compared to
beancount.ingest, beangulp now produces more logging when doing an extract
so I wanted to question why it's there.
In my specific case, I use beangulp directly within vim to import
transactions directly into my beancount
Thank you for doing this!
On Fri, Feb 19, 2021 at 7:20 PM Daniele Nicolodi wrote:
> On 02/02/2021 07:20, Martin Blais wrote:
> > Hi,
> >
> > Part of v3 plans is thinning out the repository.
> > I've just moved the beancount.ingest directory from beancount to a new
> > repository.
> >
No problem Daniele, thanks for fixing up the history!
On Fri, Feb 19, 2021 at 4:20 PM Daniele Nicolodi wrote:
> On 02/02/2021 07:20, Martin Blais wrote:
> > Hi,
> >
> > Part of v3 plans is thinning out the repository.
> > I've just moved the beancount.ingest directory from beancount to a new
>
On 02/02/2021 07:20, Martin Blais wrote:
> Hi,
>
> Part of v3 plans is thinning out the repository.
> I've just moved the beancount.ingest directory from beancount to a new
> repository.
> Announcing:
> https://github.com/beancount/beangulp
When beangulp was split off from the beancount
On Friday, 12 February 2021 at 21:45:21 UTC+1 dan...@grinta.net wrote:
> On 02/02/2021 07:28, Martin Michlmayr wrote:
> > * Martin Blais [2021-02-02 01:20]:
> >> - Nothing changed in v2, everything is still there.
> >> If you want things stable, stick with v2.
> >
> > Since beangulp
On 02/02/2021 07:28, Martin Michlmayr wrote:
> * Martin Blais [2021-02-02 01:20]:
>> - Nothing changed in v2, everything is still there.
>> If you want things stable, stick with v2.
>
> Since beangulp creates transactions on stdout, is it possible to
> migrate from ingest to beangulp while
On Fri, Feb 12, 2021 at 11:55 AM kuba@gmail.com
wrote:
> Hi all,
>
> On Friday, 12 February 2021 at 02:20:11 UTC+1 bl...@furius.ca wrote:
>
>> On Thu, Feb 11, 2021 at 6:23 PM kuba@gmail.com
>> wrote:
>>
>>> Thank you both,
>>>
>>> Martin for the beangulp documentation and Dan for the
Hi all,
On Friday, 12 February 2021 at 02:20:11 UTC+1 bl...@furius.ca wrote:
> On Thu, Feb 11, 2021 at 6:23 PM kuba@gmail.com
> wrote:
>
>> Thank you both,
>>
>> Martin for the beangulp documentation and Dan for the clear instructions.
>>
>> As a result I've managed to convert one of my
On Thu, Feb 11, 2021 at 6:23 PM kuba@gmail.com
wrote:
> Thank you both,
>
> Martin for the beangulp documentation and Dan for the clear instructions.
>
> As a result I've managed to convert one of my scripts quite easily.
>
> However on running the extract command, I am immediately hit with
Thank you both,
Martin for the beangulp documentation and Dan for the clear instructions.
As a result I've managed to convert one of my scripts quite easily.
However on running the extract command, I am immediately hit with an issue
with the rounding of the amount.
What used to be in v2
On 11/02/2021 22:53, kuba@gmail.com wrote:
> Regarding importer development on v2, if I was to make changes to
> csv.py, will the changes be migrated from the v2 branch into beangulp?
>
> I'm still unsure of how to use beangulp and I would like to make changes
> to the importers so will I
On Thu, Feb 11, 2021 at 4:53 PM kuba@gmail.com
wrote:
> Regarding importer development on v2, if I was to make changes to csv.py,
> will the changes be migrated from the v2 branch into beangulp?
I don't think a whole lot of development will happen on v2 anymore,
especially for ingest and
Regarding importer development on v2, if I was to make changes to csv.py,
will the changes be migrated from the v2 branch into beangulp?
I'm still unsure of how to use beangulp and I would like to make changes to
the importers so will I need to port the changes over myself once I
familiarise
I have both and switch and git checkout and rebuild back and forth.
Requires PYTHONPATH and local repos, not installed
Beangulp will be sync'ed to master/v3 and if something it depends on
changes in beancount and you're running it on top of a v2 install it might
break so at some point
On 02/02/2021 07:28, Martin Michlmayr wrote:
> * Martin Blais [2021-02-02 01:20]:
>> - Nothing changed in v2, everything is still there.
>> If you want things stable, stick with v2.
>
> Since beangulp creates transactions on stdout, is it possible to
> migrate from ingest to beangulp while
* Martin Blais [2021-02-02 01:20]:
> - Nothing changed in v2, everything is still there.
> If you want things stable, stick with v2.
Since beangulp creates transactions on stdout, is it possible to
migrate from ingest to beangulp while staying on v2 for other
functionality? (or is that not
Hi,
Part of v3 plans is thinning out the repository.
I've just moved the beancount.ingest directory from beancount to a new
repository.
Announcing:
https://github.com/beancount/beangulp
In keeping with all things of the bean (beanthings?), this one becomes
"beangulp".
I hope you like the name,
27 matches
Mail list logo
