PyPI packages / git tags for beancount / beangulp v3

[kuba....@gmail.com]

Hi all,

I appreciate v3 is still in development but I was wondering it wasn't time to create a v3 PyPI for beancount and beangulp?

I've been using v3 for all my importing ever since beancount.ingest was deprecated and it has been completely stable for my general use. 

The main reason why I would like PyPI packages is that I have my importer on GitHub and in its requirements.txt it has

git+git://github.com/beancount/beancount@master
git+git://github.com/beancount/beangulp@master

These work but they are a moving target as they do not define a specific revision of either.

This bugs me a little as I would much prefer to specific a known good version in my list of dependencies.

If it's still not the right time for packages, then could we at least have v3 tags in git that I could use instead of the master branch?

Kind regards,

Jakub.

[Daniele Nicolodi]

On 27/01/2022 23:09, kuba....@gmail.com wrote:
> Hi all,
>
> I appreciate v3 is still in development but I was wondering it wasn't
> time to create a v3 PyPI for beancount and beangulp?
>
> I've been using v3 for all my importing ever since beancount.ingest was
> deprecated and it has been completely stable for my general use.
>
> The main reason why I would like PyPI packages is that I have my
> importer on GitHub and in its requirements.txt it has
> git+git://github.com/beancount/beancount@master
> git+git://github.com/beancount/beangulp@master
>
> These work but they are a moving target as they do not define a specific
> revision of either.
>
> This bugs me a little as I would much prefer to specific a known good
> version in my list of dependencies.

You can point pip to a specific commit

git+https://github.com/beancount/beancount@<hash>

cb3526a1af95b3b5be70347470c381b5a86055fe is the current head of the
master branch of Beancount.

Cheers,
Dan