Re: Is v2 > v3 still?

[Daniele Nicolodi]

On 19/07/23 22:03, Eric Altendorf wrote:

In a related vein, are there other reporting tools I can use with v3
to generate even non-interactive reports?


It really depends on what you intend for reporting tools. I use 
beanquery for extracting data from my ledgers, but it is not exactly 
what most people would call a reporting tool.


Cheers,
Dan

--
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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/7d117994-aa7f-d500-1d94-e886e451f751%40grinta.net.

Re: Is v2 > v3 still?

[Daniele Nicolodi]

On 20/07/23 04:47, Eric Altendorf wrote:
the installation instructions are a bit confused and misleading with 
some out-of-date v2 instructions and some incomplete and out-of-date v3 
instructions (as came up earlier in the thread).


The instructions to install the latest development version of beancount 
do not exist, because they are the same as for any other Python package 
that does not have wheels released on PyPI, and they are very easy:


pip install git+https://github.com/beancount/beancount.git

Replace "beancount.git" with "beangulp.git" or "beanquery.git" for 
getting the other components you may need.


Because beancount v3 is still in development, I assumed that all 
interested in installing it would have a minimal knowledge of Python 
package development, and if they do, that is the first command they 
would try to install the package. As nothing special is required, I felt 
that no special instruction are needed.



On linux, roughly:
1) git clone the repos you want (beancount, beangulp, ...)
2) create a virtual environment to have an isolated and disposable 
beancount install/config
3) in the venv, `python3 -m pip install -r 
beancount/requirements/dev.txt -e beancount/ -e beangulp/`


This gives you editable installs of the packages. While it should not 
have any downsides (other than you need to keep the source trees around, 
or things will stop working) I would not recommend it for users that 
don't want to work on the code of these packages.


Possibly you may need to run `make` in the beancount/ dir; I'm not 
sure.


You don't need to run make.

 Martin said you don't need Bazel, at least on linux.  On windows 
I'm not sure because I have no idea how C++ build tools work on windows.


There are no C++ components used yet. Bazel is used only to build the 
experimental components in C++, but these are not used anywere yet.


Plan on running (2) and (3) again in the future if you ever need to 
install other python modules; pip gets easily confused and can work your 
install packages into a wonky state that is difficult to back out of, 
easier to just wipe and reinstall everything with one run of pip with 
all packages at once.  (For example, if later you try to install Fava, 
pip will helpfully silently install beancount v2 in an attempt to meet 
the Fava compatibility requirements, and you'll end up with a random mix 
of v3 and v2, mostly v2.  You only get a compatibility error if you try 
to install beancount v3 and fava in the same pip invocation.)


OTOH I'm not sure if v3 offers major user-facing upgrades at this 
point.  v3 sounds like it's mostly about internal reworking.


In v3 some components (beancount.query, beancount.ingest, bean-price) 
have been moved out of the core application into their own projects 
(beanquery, beangulp, beanprice). The first two have seen major updates 
compared to the version contained in beancount v2. However, you can use 
these also with beancount v2.


 Unless 
there's a specific capability v3 offers you, or you want to contribute 
to code development, I think v2 might be fine.  Just don't try to follow 
the instructions for installing the "dev" version of v2, it describes 
how to build v2 but since the repo head is now v3 your git clone will 
get v3 code (at least I think that's what happened to me on my first 
attempt at installing).


If you want the source code for beancount v2 just checkout the v2 
branch. However, the development instructions for v2 and v3 should be 
identical (despite they deviate from what are modern python packaging 
practices and follow Martin's workflow), so I'm surprised you ran into 
issues.


HTH, in another life I'm messing with PyTorch and LLMs and there I'm in 
a hellscape of pip-installed packages, conda-installed packages, and 
apt-installed Cuda libraries, it's total chaos.  Apt is OK, but Python 
package management is ... unpleasant.


Don't try to mix conda-installed and pip-installed packages. It works in 
simple cases but it is likely to cause issue. I mean, it is written 
clearly in the conda documentation that you should not do it...


Cheers,
Dan

--
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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/2a323ab1-41fd-e522-64a0-2c5e0e0f66bf%40grinta.net.

Re: Is v2 > v3 still?

[Daniele Nicolodi]

On 20/07/23 00:56, Andrew Ng wrote:
I guess I'm just a bit lost then. Not a programmer, despite the name, 
ironically.


I was able to compile v2 successfully, but am having trouble 
understanding the install instructions for v3.


Unless you want to develop beancount itself, or you want to hack on the 
C++ rewrote, installing beancount does not require anything special or 
different from installing any other development python package:


pip install 'beancount @ git+https://github.com/beancount/beancount.git'

or even simpler:

pip install git+https://github.com/beancount/beancount.git

This is very standard, therefore I never felt the need to spell the 
instructions out. However, I've repeated the information many times on 
the mailing list.



pip install –requirement requirements/dev.txt  doesn't work, presumably
because I'm missing pytype & pylint and need 
to compile those with a C compiler?


These are only tools used for development, you don't need them. However, 
if the content of requirements/dev.txt is not installed when you run 
that command, you must have some other problem with your Python instance.


And once I compile those, do I just 
use pip and it should compile smoothly? Or is using Bazel required? What 
am I missing here, because I think it might be a lot...


Bazel is not required for installing the Python package.

Cheers,
Dan

--
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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/012b24d7-74fd-9899-28c0-16ab4feb3d81%40grinta.net.

Re: Is v2 > v3 still?

[Eric Altendorf]

On Wed, Jul 19, 2023 at 15:56 Andrew Ng  wrote:

> I guess I'm just a bit lost then. Not a programmer, despite the name,
> ironically.
>
> I was able to compile v2 successfully, but am having trouble understanding
> the install instructions for v3.
>
> > pip install –requirement requirements/dev.txt doesn't work, presumably
> because I'm missing pytype & pylint and need to compile those with a C
> compiler? And once I compile those, do I just use pip and it should compile
> smoothly? Or is using Bazel required? What am I missing here, because I
> think it might be a lot...
>

the installation instructions are a bit confused and misleading with some
out-of-date v2 instructions and some incomplete and out-of-date v3
instructions (as came up earlier in the thread).

On linux, roughly:
1) git clone the repos you want (beancount, beangulp, ...)
2) create a virtual environment to have an isolated and disposable
beancount install/config
3) in the venv, `python3 -m pip install -r beancount/requirements/dev.txt
-e beancount/ -e beangulp/`

Possibly you may need to run `make` in the beancount/ dir; I'm not sure.
Martin said you don't need Bazel, at least on linux.  On windows I'm not
sure because I have no idea how C++ build tools work on windows.

Plan on running (2) and (3) again in the future if you ever need to install
other python modules; pip gets easily confused and can work your install
packages into a wonky state that is difficult to back out of, easier to
just wipe and reinstall everything with one run of pip with all packages at
once.  (For example, if later you try to install Fava, pip will helpfully
silently install beancount v2 in an attempt to meet the Fava compatibility
requirements, and you'll end up with a random mix of v3 and v2, mostly v2.
You only get a compatibility error if you try to install beancount v3 and
fava in the same pip invocation.)

OTOH I'm not sure if v3 offers major user-facing upgrades at this point.
v3 sounds like it's mostly about internal reworking.  Unless there's a
specific capability v3 offers you, or you want to contribute to code
development, I think v2 might be fine.  Just don't try to follow the
instructions for installing the "dev" version of v2, it describes how to
build v2 but since the repo head is now v3 your git clone will get v3 code
(at least I think that's what happened to me on my first attempt at
installing).

HTH, in another life I'm messing with PyTorch and LLMs and there I'm in a
hellscape of pip-installed packages, conda-installed packages, and
apt-installed Cuda libraries, it's total chaos.  Apt is OK, but Python
package management is ... unpleasant.

eric



> Thanks,
> Andrew
> On Wednesday, July 19, 2023 at 2:04:08 PM UTC-7 dan...@grinta.net wrote:
>
>> On 19/07/23 19:56, Andrew Ng wrote:
>> > On this note, is there any support at all yet for v3 on Windows?
>>
>> What do you mean? Beancount v3 works just fine on Windows. Just there
>> aren't any Python wheels released for it. You need a C compiler to
>> compile the Python extensions modules.
>>
>> Cheers,
>> Dan
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Beancount" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beancount/LVBQ4cD0PYc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beancount+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beancount/5e3adf29-c99f-40d4-98ed-65c735f29190n%40googlegroups.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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/CAFXPr0vVJamAP2e6hY0trEW3vTFW-%3DU8kZ2UWwak67wkzf3v0w%40mail.gmail.com.

Re: Is v2 > v3 still?

[Andrew Ng]

I guess I'm just a bit lost then. Not a programmer, despite the name, 
ironically.

I was able to compile v2 successfully, but am having trouble understanding 
the install instructions for v3.

> pip install –requirement requirements/dev.txt doesn't work, presumably 
because I'm missing pytype & pylint and need to compile those with a C 
compiler? And once I compile those, do I just use pip and it should compile 
smoothly? Or is using Bazel required? What am I missing here, because I 
think it might be a lot...

Thanks,
Andrew 
On Wednesday, July 19, 2023 at 2:04:08 PM UTC-7 dan...@grinta.net wrote:

> On 19/07/23 19:56, Andrew Ng wrote:
> > On this note, is there any support at all yet for v3 on Windows?
>
> What do you mean? Beancount v3 works just fine on Windows. Just there 
> aren't any Python wheels released for it. You need a C compiler to 
> compile the Python extensions modules.
>
> Cheers,
> Dan
>
>

-- 
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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/5e3adf29-c99f-40d4-98ed-65c735f29190n%40googlegroups.com.

Re: Is v2 > v3 still?

[Daniele Nicolodi]

On 19/07/23 19:56, Andrew Ng wrote:

On this note, is there any support at all yet for v3 on Windows?


What do you mean? Beancount v3 works just fine on Windows. Just there 
aren't any Python wheels released for it. You need a C compiler to 
compile the Python extensions modules.


Cheers,
Dan

--
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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/43c638db-1895-e0df-7c97-52f9d7b55f8e%40grinta.net.

Re: Is v2 > v3 still?

[Andrew Ng]

On this note, is there any support at all yet for v3 on Windows? Another 
new user here and I don't have a Linux install handy. No problem if not, 
just wondering.

On Friday, July 14, 2023 at 4:45:21 PM UTC-7 Martin Blais wrote:

> v3 > v2
> No less stable; less overall code, many parts moved to subprojects that 
> have been more actively developed. Some c++ bit present but not used in the 
> main loop.
> Use v3.
>
> (Apologies for the little warning in every invocation.)
>
> On Sat, Jul 15, 2023, 07:42 Eric Altendorf  wrote:
>
>> I'd like to get started with Beancount, and it wasn't clear to me if the 
>> docs have been updated recently.  Is v3 still considered unstable, and it's 
>> best to use v2?
>>
>> thanks,
>> eric
>>
>> -- 
>> 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 beancount+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beancount/1f684516-bd76-4ff5-adcb-b2b15b28b6a6n%40googlegroups.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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/37f4437f-066d-4ad0-bda5-58312deb760en%40googlegroups.com.

Re: Is v2 > v3 still?

[Eric Altendorf]

On Wed, Jul 19, 2023 at 11:32 AM Daniele Nicolodi 
wrote:

> On 19/07/23 16:58, Eric Altendorf wrote:
> > On Sun, Jul 16, 2023 at 10:07 PM Martin Blais  > > wrote:
> >
> > bean-query, bean-price have  been moved to their own projects in v3.
> > See other repos in the same org.
> >
> > Bean-web has been deleted; use Fava instead.
> >
> >
> > Noob question; how do you run Fava with Beancount v3?
>
>  From the output of "pip install" below, it seems that the Fava
> developers don't want you to run Fava with Beancount 3.0. I don't know
> why this is the case, but the short answer is: you don't.
>

Indeed, that's what the Fava config says, but since Martin had said
"Bean-web has been deleted [in v3]; use Fava instead"
I inferred that perhaps some people are indeed using Fava with
v3, so it seemed reasonable to ask how. :)

In a related vein, are there other reporting tools I can use with v3
to generate even non-interactive reports?



>
> Cheers,
> Dan
>
> --
> 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 beancount+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beancount/d33d8b26-ed64-106c-4017-12e807db2f6d%40grinta.net
> .
>

-- 
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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/CAFXPr0useiHRDnsn98aWWXff5mo5NspW7Q7Uys6sXYLRwtig9g%40mail.gmail.com.

Re: Is v2 > v3 still?

[Daniele Nicolodi]

On 19/07/23 16:58, Eric Altendorf wrote:
On Sun, Jul 16, 2023 at 10:07 PM Martin Blais > wrote:


bean-query, bean-price have  been moved to their own projects in v3.
See other repos in the same org.

Bean-web has been deleted; use Fava instead.


Noob question; how do you run Fava with Beancount v3?


From the output of "pip install" below, it seems that the Fava 
developers don't want you to run Fava with Beancount 3.0. I don't know 
why this is the case, but the short answer is: you don't.


Cheers,
Dan

--
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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/d33d8b26-ed64-106c-4017-12e807db2f6d%40grinta.net.

Re: Is v2 > v3 still?

[Eric Altendorf]

On Sun, Jul 16, 2023 at 10:07 PM Martin Blais  wrote:

> bean-query, bean-price have  been moved to their own projects in v3.
> See other repos in the same org.
>
> Bean-web has been deleted; use Fava instead.
>

Noob question; how do you run Fava with Beancount v3?

I noticed when I pip install Fava it downgrades me to Beancount v2.

Cloning latest github repos for beancount, beangulp, and fava, and letting
pip think about all its dependencies at once suggests Fava is v2-only?

python3 -m pip install -r beancount/requirements/dev.txt -e beancount/ -e
beangulp/ -e fava/
...
ERROR: Cannot install beancount 3.0.0.dev0 (from
/home/eric/crypto-taxes/beancount), beangulp==0.1.dev0 and fava==1.25
because these package versions have conflicting dependencies.

The conflict is caused by:
The user requested beancount 3.0.0.dev0 (from
/home/eric/crypto-taxes/beancount)
beangulp 0.1.dev0 depends on beancount>=2.3.5
fava 1.25 depends on beancount<3 and >=2.3.5


> On Mon, Jul 17, 2023, 10:26 Eric Altendorf 
> wrote:
>
>> Thanks.
>>
>> make & pip install worked fine.  can run bean-check.  Still doesn't seem
>> to be building some of the tools, e.g., `bean-web` is still missing:
>>
>> beancount$ ls bin
>> bean-check  bean-doctor  bean-example  bean-format  BUILD  treeify
>>
>> do i still need to do something with setup.py like in v2?
>>
>>
>> On Sun, Jul 16, 2023 at 5:10 PM Martin Blais  wrote:
>>
>>>
>>>
>>> On Mon, Jul 17, 2023, 06:00 Eric Altendorf 
>>> wrote:
>>>
 On Sun, Jul 16, 2023 at 2:27 PM Martin Blais  wrote:

> Precisely reliable and reproducible packaging and instructions that
> work for everyone all the time are impossible tasks in my experience and I
> tried for 25 years and eventually gave up. Too many environments, to many
> different users and setups. I keep it simple for dev which I think is the
> key, best is to use it like that to get the freshest. Other people do
> packaging. Packages will inevitably be slightly older. Here's the gist:
>

 Sure.  I don't think I'm complaining about the install not working in
 weird corner cases or anything like that.  Mostly remarking that the
 documentation is incorrect/broken/misleading in case you want to fix it for
 the next person who comes along.

 - "make build" will compile a .so in place (in the tree where you can
> import it). Needs a C compiler with Python dev headers and library, bison
> and flex.
>

 The v3 install instructions that I found said to use Bazel, not make.
 Is Bazel just wrapping make here?  Is there some reason to use make
 directly?

>>>
>>> Ignore bazel, this is work in progress you don't need. V3 works fine
>>> with the Python/c parser. There will also be a warning when you run about
>>> missing that library, ignore that too.
>>>
>>>
>>>

> - set your PYTHONPATH to be able to import directly from the tree.
>

 I'll do this with a venv to manage and isolate the dependencies and
 path management (which, FYI, if you wanted a hermetic and 100% reproducible
 build setup, would probably be the way to go, although I'm hardly an expert
 on that, and the last thing I want to do is debate your package's build
 setup :).

>>>
>>> Knock yourself out,
>>> pip install . into your venv should work.
>>>
>>>
 Hope this helps,
>

 Thanks! :)

 eric


>
>
>
>
>
> On Mon, Jul 17, 2023, 02:37 Eric Altendorf 
> wrote:
>
>> Aha, looks like this is the page:
>> https://beancount.github.io/docs/installing_beancount_v3.html
>>
>> I'll work from that.  Just sharing the FYI that some of the install
>> instructions / links seem to be misleading.
>>
>> On Sun, Jul 16, 2023 at 10:19 AM Eric Altendorf <
>> ericaltend...@gmail.com> wrote:
>>
>>> On Fri, Jul 14, 2023 at 8:35 PM Martin Blais 
>>> wrote:
>>>


 On Sat, Jul 15, 2023, 11:06 Eric Altendorf 
 wrote:

> On Fri, Jul 14, 2023 at 4:45 PM Martin Blais 
> wrote:
>
>> v3 > v2
>> No less stable; less overall code, many parts moved to
>> subprojects that have been more actively developed. Some c++ bit 
>> present
>> but not used in the main loop.
>> Use v3.
>>
>
> Cool.  FWIW, https://beancount.github.io/ still says v3 "is
> unstable and you want to use version 2 below".
>

 All types of users, this is largely for non technical users. It's
 stable enough for you. I try not to commit build breaking changes 
 (lots of
 tests).

>>>
>>> OK.  Looks like `apt install` just gives me v2, so I removed that
>>> and I'm back to installing from source.  I'd like to install for dev, in
>>> case I want to experiment with writing my own booking algorithm.
>>>

Re: Is v2 > v3 still?

[Daniele Nicolodi]

On 17/07/23 04:26, Eric Altendorf wrote:

Thanks.

make & pip install worked fine.


If you install with "pip install" there is no need to run make.

Cheers,
Dan

--
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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/52f20920-1885-fb1d-1f84-783106402f99%40grinta.net.

Re: Is v2 > v3 still?

[Eric Altendorf]

Got it, thanks.

On Sun, Jul 16, 2023 at 10:07 PM Martin Blais  wrote:

> bean-query, bean-price have  been moved to their own projects in v3.
> See other repos in the same org.
>
> Bean-web has been deleted; use Fava instead.
>
> On Mon, Jul 17, 2023, 10:26 Eric Altendorf 
> wrote:
>
>> Thanks.
>>
>> make & pip install worked fine.  can run bean-check.  Still doesn't seem
>> to be building some of the tools, e.g., `bean-web` is still missing:
>>
>> beancount$ ls bin
>> bean-check  bean-doctor  bean-example  bean-format  BUILD  treeify
>>
>> do i still need to do something with setup.py like in v2?
>>
>>
>> On Sun, Jul 16, 2023 at 5:10 PM Martin Blais  wrote:
>>
>>>
>>>
>>> On Mon, Jul 17, 2023, 06:00 Eric Altendorf 
>>> wrote:
>>>
 On Sun, Jul 16, 2023 at 2:27 PM Martin Blais  wrote:

> Precisely reliable and reproducible packaging and instructions that
> work for everyone all the time are impossible tasks in my experience and I
> tried for 25 years and eventually gave up. Too many environments, to many
> different users and setups. I keep it simple for dev which I think is the
> key, best is to use it like that to get the freshest. Other people do
> packaging. Packages will inevitably be slightly older. Here's the gist:
>

 Sure.  I don't think I'm complaining about the install not working in
 weird corner cases or anything like that.  Mostly remarking that the
 documentation is incorrect/broken/misleading in case you want to fix it for
 the next person who comes along.

 - "make build" will compile a .so in place (in the tree where you can
> import it). Needs a C compiler with Python dev headers and library, bison
> and flex.
>

 The v3 install instructions that I found said to use Bazel, not make.
 Is Bazel just wrapping make here?  Is there some reason to use make
 directly?

>>>
>>> Ignore bazel, this is work in progress you don't need. V3 works fine
>>> with the Python/c parser. There will also be a warning when you run about
>>> missing that library, ignore that too.
>>>
>>>
>>>

> - set your PYTHONPATH to be able to import directly from the tree.
>

 I'll do this with a venv to manage and isolate the dependencies and
 path management (which, FYI, if you wanted a hermetic and 100% reproducible
 build setup, would probably be the way to go, although I'm hardly an expert
 on that, and the last thing I want to do is debate your package's build
 setup :).

>>>
>>> Knock yourself out,
>>> pip install . into your venv should work.
>>>
>>>
 Hope this helps,
>

 Thanks! :)

 eric


>
>
>
>
>
> On Mon, Jul 17, 2023, 02:37 Eric Altendorf 
> wrote:
>
>> Aha, looks like this is the page:
>> https://beancount.github.io/docs/installing_beancount_v3.html
>>
>> I'll work from that.  Just sharing the FYI that some of the install
>> instructions / links seem to be misleading.
>>
>> On Sun, Jul 16, 2023 at 10:19 AM Eric Altendorf <
>> ericaltend...@gmail.com> wrote:
>>
>>> On Fri, Jul 14, 2023 at 8:35 PM Martin Blais 
>>> wrote:
>>>


 On Sat, Jul 15, 2023, 11:06 Eric Altendorf 
 wrote:

> On Fri, Jul 14, 2023 at 4:45 PM Martin Blais 
> wrote:
>
>> v3 > v2
>> No less stable; less overall code, many parts moved to
>> subprojects that have been more actively developed. Some c++ bit 
>> present
>> but not used in the main loop.
>> Use v3.
>>
>
> Cool.  FWIW, https://beancount.github.io/ still says v3 "is
> unstable and you want to use version 2 below".
>

 All types of users, this is largely for non technical users. It's
 stable enough for you. I try not to commit build breaking changes 
 (lots of
 tests).

>>>
>>> OK.  Looks like `apt install` just gives me v2, so I removed that
>>> and I'm back to installing from source.  I'd like to install for dev, in
>>> case I want to experiment with writing my own booking algorithm.
>>>
>>>


 And https://beancount.github.io/docs/installing_beancount.html
> says it is instructions for installing v2.
>
> Also I tried following the "Installing for Development"
> instructions there, running git clone, then `sudo python3 setup.py 
> develop`
> and `python3 setup.py build_ext -i` and this produced a broken 
> install.
>

 This is for development, in just modify your PYTHONPATH to include
 the repo. See beancount/etc/env

>>>
>>> Sorry, I think I'm missing something more basic; things were very
>>> broken just following the instructions.  I do notice there is a 
>>> Makefile in
>>> 

Re: Is v2 > v3 still?

[Martin Blais]

bean-query, bean-price have  been moved to their own projects in v3.
See other repos in the same org.

Bean-web has been deleted; use Fava instead.

On Mon, Jul 17, 2023, 10:26 Eric Altendorf  wrote:

> Thanks.
>
> make & pip install worked fine.  can run bean-check.  Still doesn't seem
> to be building some of the tools, e.g., `bean-web` is still missing:
>
> beancount$ ls bin
> bean-check  bean-doctor  bean-example  bean-format  BUILD  treeify
>
> do i still need to do something with setup.py like in v2?
>
>
> On Sun, Jul 16, 2023 at 5:10 PM Martin Blais  wrote:
>
>>
>>
>> On Mon, Jul 17, 2023, 06:00 Eric Altendorf 
>> wrote:
>>
>>> On Sun, Jul 16, 2023 at 2:27 PM Martin Blais  wrote:
>>>
 Precisely reliable and reproducible packaging and instructions that
 work for everyone all the time are impossible tasks in my experience and I
 tried for 25 years and eventually gave up. Too many environments, to many
 different users and setups. I keep it simple for dev which I think is the
 key, best is to use it like that to get the freshest. Other people do
 packaging. Packages will inevitably be slightly older. Here's the gist:

>>>
>>> Sure.  I don't think I'm complaining about the install not working in
>>> weird corner cases or anything like that.  Mostly remarking that the
>>> documentation is incorrect/broken/misleading in case you want to fix it for
>>> the next person who comes along.
>>>
>>> - "make build" will compile a .so in place (in the tree where you can
 import it). Needs a C compiler with Python dev headers and library, bison
 and flex.

>>>
>>> The v3 install instructions that I found said to use Bazel, not make.
>>> Is Bazel just wrapping make here?  Is there some reason to use make
>>> directly?
>>>
>>
>> Ignore bazel, this is work in progress you don't need. V3 works fine with
>> the Python/c parser. There will also be a warning when you run about
>> missing that library, ignore that too.
>>
>>
>>
>>>
 - set your PYTHONPATH to be able to import directly from the tree.

>>>
>>> I'll do this with a venv to manage and isolate the dependencies and path
>>> management (which, FYI, if you wanted a hermetic and 100% reproducible
>>> build setup, would probably be the way to go, although I'm hardly an expert
>>> on that, and the last thing I want to do is debate your package's build
>>> setup :).
>>>
>>
>> Knock yourself out,
>> pip install . into your venv should work.
>>
>>
>>> Hope this helps,

>>>
>>> Thanks! :)
>>>
>>> eric
>>>
>>>





 On Mon, Jul 17, 2023, 02:37 Eric Altendorf 
 wrote:

> Aha, looks like this is the page:
> https://beancount.github.io/docs/installing_beancount_v3.html
>
> I'll work from that.  Just sharing the FYI that some of the install
> instructions / links seem to be misleading.
>
> On Sun, Jul 16, 2023 at 10:19 AM Eric Altendorf <
> ericaltend...@gmail.com> wrote:
>
>> On Fri, Jul 14, 2023 at 8:35 PM Martin Blais  wrote:
>>
>>>
>>>
>>> On Sat, Jul 15, 2023, 11:06 Eric Altendorf 
>>> wrote:
>>>
 On Fri, Jul 14, 2023 at 4:45 PM Martin Blais 
 wrote:

> v3 > v2
> No less stable; less overall code, many parts moved to subprojects
> that have been more actively developed. Some c++ bit present but not 
> used
> in the main loop.
> Use v3.
>

 Cool.  FWIW, https://beancount.github.io/ still says v3 "is
 unstable and you want to use version 2 below".

>>>
>>> All types of users, this is largely for non technical users. It's
>>> stable enough for you. I try not to commit build breaking changes (lots 
>>> of
>>> tests).
>>>
>>
>> OK.  Looks like `apt install` just gives me v2, so I removed that and
>> I'm back to installing from source.  I'd like to install for dev, in 
>> case I
>> want to experiment with writing my own booking algorithm.
>>
>>
>>>
>>>
>>> And https://beancount.github.io/docs/installing_beancount.html says
 it is instructions for installing v2.

 Also I tried following the "Installing for Development"
 instructions there, running git clone, then `sudo python3 setup.py 
 develop`
 and `python3 setup.py build_ext -i` and this produced a broken install.

>>>
>>> This is for development, in just modify your PYTHONPATH to include
>>> the repo. See beancount/etc/env
>>>
>>
>> Sorry, I think I'm missing something more basic; things were very
>> broken just following the instructions.  I do notice there is a Makefile 
>> in
>> the directory, is running `make` supposed to be part of the
>> install-from-source or install-for-dev process?
>>
>> The instructions just say to run setup.py but that doesn't seem to do
>> much.
>>
>> I'm also not 

Re: Is v2 > v3 still?

[Eric Altendorf]

Oh, grepping around in the source reveals a note about Fava replacing
bean-web?  (bean-web is still what the docs discuss)

Sorry -- you've written such extensive and well-written documentation I've
been taking it as truth :)

On Sun, Jul 16, 2023 at 7:26 PM Eric Altendorf 
wrote:

> Thanks.
>
> make & pip install worked fine.  can run bean-check.  Still doesn't seem
> to be building some of the tools, e.g., `bean-web` is still missing:
>
> beancount$ ls bin
> bean-check  bean-doctor  bean-example  bean-format  BUILD  treeify
>
> do i still need to do something with setup.py like in v2?
>
>
> On Sun, Jul 16, 2023 at 5:10 PM Martin Blais  wrote:
>
>>
>>
>> On Mon, Jul 17, 2023, 06:00 Eric Altendorf 
>> wrote:
>>
>>> On Sun, Jul 16, 2023 at 2:27 PM Martin Blais  wrote:
>>>
 Precisely reliable and reproducible packaging and instructions that
 work for everyone all the time are impossible tasks in my experience and I
 tried for 25 years and eventually gave up. Too many environments, to many
 different users and setups. I keep it simple for dev which I think is the
 key, best is to use it like that to get the freshest. Other people do
 packaging. Packages will inevitably be slightly older. Here's the gist:

>>>
>>> Sure.  I don't think I'm complaining about the install not working in
>>> weird corner cases or anything like that.  Mostly remarking that the
>>> documentation is incorrect/broken/misleading in case you want to fix it for
>>> the next person who comes along.
>>>
>>> - "make build" will compile a .so in place (in the tree where you can
 import it). Needs a C compiler with Python dev headers and library, bison
 and flex.

>>>
>>> The v3 install instructions that I found said to use Bazel, not make.
>>> Is Bazel just wrapping make here?  Is there some reason to use make
>>> directly?
>>>
>>
>> Ignore bazel, this is work in progress you don't need. V3 works fine with
>> the Python/c parser. There will also be a warning when you run about
>> missing that library, ignore that too.
>>
>>
>>
>>>
 - set your PYTHONPATH to be able to import directly from the tree.

>>>
>>> I'll do this with a venv to manage and isolate the dependencies and path
>>> management (which, FYI, if you wanted a hermetic and 100% reproducible
>>> build setup, would probably be the way to go, although I'm hardly an expert
>>> on that, and the last thing I want to do is debate your package's build
>>> setup :).
>>>
>>
>> Knock yourself out,
>> pip install . into your venv should work.
>>
>>
>>> Hope this helps,

>>>
>>> Thanks! :)
>>>
>>> eric
>>>
>>>





 On Mon, Jul 17, 2023, 02:37 Eric Altendorf 
 wrote:

> Aha, looks like this is the page:
> https://beancount.github.io/docs/installing_beancount_v3.html
>
> I'll work from that.  Just sharing the FYI that some of the install
> instructions / links seem to be misleading.
>
> On Sun, Jul 16, 2023 at 10:19 AM Eric Altendorf <
> ericaltend...@gmail.com> wrote:
>
>> On Fri, Jul 14, 2023 at 8:35 PM Martin Blais  wrote:
>>
>>>
>>>
>>> On Sat, Jul 15, 2023, 11:06 Eric Altendorf 
>>> wrote:
>>>
 On Fri, Jul 14, 2023 at 4:45 PM Martin Blais 
 wrote:

> v3 > v2
> No less stable; less overall code, many parts moved to subprojects
> that have been more actively developed. Some c++ bit present but not 
> used
> in the main loop.
> Use v3.
>

 Cool.  FWIW, https://beancount.github.io/ still says v3 "is
 unstable and you want to use version 2 below".

>>>
>>> All types of users, this is largely for non technical users. It's
>>> stable enough for you. I try not to commit build breaking changes (lots 
>>> of
>>> tests).
>>>
>>
>> OK.  Looks like `apt install` just gives me v2, so I removed that and
>> I'm back to installing from source.  I'd like to install for dev, in 
>> case I
>> want to experiment with writing my own booking algorithm.
>>
>>
>>>
>>>
>>> And https://beancount.github.io/docs/installing_beancount.html says
 it is instructions for installing v2.

 Also I tried following the "Installing for Development"
 instructions there, running git clone, then `sudo python3 setup.py 
 develop`
 and `python3 setup.py build_ext -i` and this produced a broken install.

>>>
>>> This is for development, in just modify your PYTHONPATH to include
>>> the repo. See beancount/etc/env
>>>
>>
>> Sorry, I think I'm missing something more basic; things were very
>> broken just following the instructions.  I do notice there is a Makefile 
>> in
>> the directory, is running `make` supposed to be part of the
>> install-from-source or install-for-dev process?
>>
>> The instructions just say to 

Re: Is v2 > v3 still?

[Eric Altendorf]

Thanks.

make & pip install worked fine.  can run bean-check.  Still doesn't seem to
be building some of the tools, e.g., `bean-web` is still missing:

beancount$ ls bin
bean-check  bean-doctor  bean-example  bean-format  BUILD  treeify

do i still need to do something with setup.py like in v2?


On Sun, Jul 16, 2023 at 5:10 PM Martin Blais  wrote:

>
>
> On Mon, Jul 17, 2023, 06:00 Eric Altendorf 
> wrote:
>
>> On Sun, Jul 16, 2023 at 2:27 PM Martin Blais  wrote:
>>
>>> Precisely reliable and reproducible packaging and instructions that work
>>> for everyone all the time are impossible tasks in my experience and I tried
>>> for 25 years and eventually gave up. Too many environments, to many
>>> different users and setups. I keep it simple for dev which I think is the
>>> key, best is to use it like that to get the freshest. Other people do
>>> packaging. Packages will inevitably be slightly older. Here's the gist:
>>>
>>
>> Sure.  I don't think I'm complaining about the install not working in
>> weird corner cases or anything like that.  Mostly remarking that the
>> documentation is incorrect/broken/misleading in case you want to fix it for
>> the next person who comes along.
>>
>> - "make build" will compile a .so in place (in the tree where you can
>>> import it). Needs a C compiler with Python dev headers and library, bison
>>> and flex.
>>>
>>
>> The v3 install instructions that I found said to use Bazel, not make.  Is
>> Bazel just wrapping make here?  Is there some reason to use make directly?
>>
>
> Ignore bazel, this is work in progress you don't need. V3 works fine with
> the Python/c parser. There will also be a warning when you run about
> missing that library, ignore that too.
>
>
>
>>
>>> - set your PYTHONPATH to be able to import directly from the tree.
>>>
>>
>> I'll do this with a venv to manage and isolate the dependencies and path
>> management (which, FYI, if you wanted a hermetic and 100% reproducible
>> build setup, would probably be the way to go, although I'm hardly an expert
>> on that, and the last thing I want to do is debate your package's build
>> setup :).
>>
>
> Knock yourself out,
> pip install . into your venv should work.
>
>
>> Hope this helps,
>>>
>>
>> Thanks! :)
>>
>> eric
>>
>>
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Jul 17, 2023, 02:37 Eric Altendorf 
>>> wrote:
>>>
 Aha, looks like this is the page:
 https://beancount.github.io/docs/installing_beancount_v3.html

 I'll work from that.  Just sharing the FYI that some of the install
 instructions / links seem to be misleading.

 On Sun, Jul 16, 2023 at 10:19 AM Eric Altendorf <
 ericaltend...@gmail.com> wrote:

> On Fri, Jul 14, 2023 at 8:35 PM Martin Blais  wrote:
>
>>
>>
>> On Sat, Jul 15, 2023, 11:06 Eric Altendorf 
>> wrote:
>>
>>> On Fri, Jul 14, 2023 at 4:45 PM Martin Blais 
>>> wrote:
>>>
 v3 > v2
 No less stable; less overall code, many parts moved to subprojects
 that have been more actively developed. Some c++ bit present but not 
 used
 in the main loop.
 Use v3.

>>>
>>> Cool.  FWIW, https://beancount.github.io/ still says v3 "is
>>> unstable and you want to use version 2 below".
>>>
>>
>> All types of users, this is largely for non technical users. It's
>> stable enough for you. I try not to commit build breaking changes (lots 
>> of
>> tests).
>>
>
> OK.  Looks like `apt install` just gives me v2, so I removed that and
> I'm back to installing from source.  I'd like to install for dev, in case 
> I
> want to experiment with writing my own booking algorithm.
>
>
>>
>>
>> And https://beancount.github.io/docs/installing_beancount.html says
>>> it is instructions for installing v2.
>>>
>>> Also I tried following the "Installing for Development" instructions
>>> there, running git clone, then `sudo python3 setup.py develop` and 
>>> `python3
>>> setup.py build_ext -i` and this produced a broken install.
>>>
>>
>> This is for development, in just modify your PYTHONPATH to include
>> the repo. See beancount/etc/env
>>
>
> Sorry, I think I'm missing something more basic; things were very
> broken just following the instructions.  I do notice there is a Makefile 
> in
> the directory, is running `make` supposed to be part of the
> install-from-source or install-for-dev process?
>
> The instructions just say to run setup.py but that doesn't seem to do
> much.
>
> I'm also not sure if I'm even following the right instructions since,
> as I mentioned, the document itself says it's for installing v2, and the
> link to instructions for installing v3 is broken (links to
> https://beancount.github.io/docs/installing_beancount_v3.md )
>
>
>>
>>
>>> Backing out of that and just running `apt install 

Re: Is v2 > v3 still?

[Martin Blais]

On Mon, Jul 17, 2023, 06:00 Eric Altendorf  wrote:

> On Sun, Jul 16, 2023 at 2:27 PM Martin Blais  wrote:
>
>> Precisely reliable and reproducible packaging and instructions that work
>> for everyone all the time are impossible tasks in my experience and I tried
>> for 25 years and eventually gave up. Too many environments, to many
>> different users and setups. I keep it simple for dev which I think is the
>> key, best is to use it like that to get the freshest. Other people do
>> packaging. Packages will inevitably be slightly older. Here's the gist:
>>
>
> Sure.  I don't think I'm complaining about the install not working in
> weird corner cases or anything like that.  Mostly remarking that the
> documentation is incorrect/broken/misleading in case you want to fix it for
> the next person who comes along.
>
> - "make build" will compile a .so in place (in the tree where you can
>> import it). Needs a C compiler with Python dev headers and library, bison
>> and flex.
>>
>
> The v3 install instructions that I found said to use Bazel, not make.  Is
> Bazel just wrapping make here?  Is there some reason to use make directly?
>

Ignore bazel, this is work in progress you don't need. V3 works fine with
the Python/c parser. There will also be a warning when you run about
missing that library, ignore that too.



>
>> - set your PYTHONPATH to be able to import directly from the tree.
>>
>
> I'll do this with a venv to manage and isolate the dependencies and path
> management (which, FYI, if you wanted a hermetic and 100% reproducible
> build setup, would probably be the way to go, although I'm hardly an expert
> on that, and the last thing I want to do is debate your package's build
> setup :).
>

Knock yourself out,
pip install . into your venv should work.


> Hope this helps,
>>
>
> Thanks! :)
>
> eric
>
>
>>
>>
>>
>>
>>
>> On Mon, Jul 17, 2023, 02:37 Eric Altendorf 
>> wrote:
>>
>>> Aha, looks like this is the page:
>>> https://beancount.github.io/docs/installing_beancount_v3.html
>>>
>>> I'll work from that.  Just sharing the FYI that some of the install
>>> instructions / links seem to be misleading.
>>>
>>> On Sun, Jul 16, 2023 at 10:19 AM Eric Altendorf 
>>> wrote:
>>>
 On Fri, Jul 14, 2023 at 8:35 PM Martin Blais  wrote:

>
>
> On Sat, Jul 15, 2023, 11:06 Eric Altendorf 
> wrote:
>
>> On Fri, Jul 14, 2023 at 4:45 PM Martin Blais  wrote:
>>
>>> v3 > v2
>>> No less stable; less overall code, many parts moved to subprojects
>>> that have been more actively developed. Some c++ bit present but not 
>>> used
>>> in the main loop.
>>> Use v3.
>>>
>>
>> Cool.  FWIW, https://beancount.github.io/ still says v3 "is unstable
>> and you want to use version 2 below".
>>
>
> All types of users, this is largely for non technical users. It's
> stable enough for you. I try not to commit build breaking changes (lots of
> tests).
>

 OK.  Looks like `apt install` just gives me v2, so I removed that and
 I'm back to installing from source.  I'd like to install for dev, in case I
 want to experiment with writing my own booking algorithm.


>
>
> And https://beancount.github.io/docs/installing_beancount.html says
>> it is instructions for installing v2.
>>
>> Also I tried following the "Installing for Development" instructions
>> there, running git clone, then `sudo python3 setup.py develop` and 
>> `python3
>> setup.py build_ext -i` and this produced a broken install.
>>
>
> This is for development, in just modify your PYTHONPATH to include the
> repo. See beancount/etc/env
>

 Sorry, I think I'm missing something more basic; things were very
 broken just following the instructions.  I do notice there is a Makefile in
 the directory, is running `make` supposed to be part of the
 install-from-source or install-for-dev process?

 The instructions just say to run setup.py but that doesn't seem to do
 much.

 I'm also not sure if I'm even following the right instructions since,
 as I mentioned, the document itself says it's for installing v2, and the
 link to instructions for installing v3 is broken (links to
 https://beancount.github.io/docs/installing_beancount_v3.md )


>
>
>> Backing out of that and just running `apt install beancount` worked
>> fine though :-D
>>
>>
>>
>>> (Apologies for the little warning in every invocation.)
>>>
>>> On Sat, Jul 15, 2023, 07:42 Eric Altendorf 
>>> wrote:
>>>
 I'd like to get started with Beancount, and it wasn't clear to me
 if the docs have been updated recently.  Is v3 still considered 
 unstable,
 and it's best to use v2?

 thanks,
 eric

 --
 You received this message because you are subscribed to the Google
 

Re: Is v2 > v3 still?

[Eric Altendorf]

On Sun, Jul 16, 2023 at 2:27 PM Martin Blais  wrote:

> Precisely reliable and reproducible packaging and instructions that work
> for everyone all the time are impossible tasks in my experience and I tried
> for 25 years and eventually gave up. Too many environments, to many
> different users and setups. I keep it simple for dev which I think is the
> key, best is to use it like that to get the freshest. Other people do
> packaging. Packages will inevitably be slightly older. Here's the gist:
>

Sure.  I don't think I'm complaining about the install not working in weird
corner cases or anything like that.  Mostly remarking that the
documentation is incorrect/broken/misleading in case you want to fix it for
the next person who comes along.

- "make build" will compile a .so in place (in the tree where you can
> import it). Needs a C compiler with Python dev headers and library, bison
> and flex.
>

The v3 install instructions that I found said to use Bazel, not make.  Is
Bazel just wrapping make here?  Is there some reason to use make directly?


> - set your PYTHONPATH to be able to import directly from the tree.
>

I'll do this with a venv to manage and isolate the dependencies and path
management (which, FYI, if you wanted a hermetic and 100% reproducible
build setup, would probably be the way to go, although I'm hardly an expert
on that, and the last thing I want to do is debate your package's build
setup :).

Hope this helps,
>

Thanks! :)

eric


>
>
>
>
>
> On Mon, Jul 17, 2023, 02:37 Eric Altendorf 
> wrote:
>
>> Aha, looks like this is the page:
>> https://beancount.github.io/docs/installing_beancount_v3.html
>>
>> I'll work from that.  Just sharing the FYI that some of the install
>> instructions / links seem to be misleading.
>>
>> On Sun, Jul 16, 2023 at 10:19 AM Eric Altendorf 
>> wrote:
>>
>>> On Fri, Jul 14, 2023 at 8:35 PM Martin Blais  wrote:
>>>


 On Sat, Jul 15, 2023, 11:06 Eric Altendorf 
 wrote:

> On Fri, Jul 14, 2023 at 4:45 PM Martin Blais  wrote:
>
>> v3 > v2
>> No less stable; less overall code, many parts moved to subprojects
>> that have been more actively developed. Some c++ bit present but not used
>> in the main loop.
>> Use v3.
>>
>
> Cool.  FWIW, https://beancount.github.io/ still says v3 "is unstable
> and you want to use version 2 below".
>

 All types of users, this is largely for non technical users. It's
 stable enough for you. I try not to commit build breaking changes (lots of
 tests).

>>>
>>> OK.  Looks like `apt install` just gives me v2, so I removed that and
>>> I'm back to installing from source.  I'd like to install for dev, in case I
>>> want to experiment with writing my own booking algorithm.
>>>
>>>


 And https://beancount.github.io/docs/installing_beancount.html says it
> is instructions for installing v2.
>
> Also I tried following the "Installing for Development" instructions
> there, running git clone, then `sudo python3 setup.py develop` and 
> `python3
> setup.py build_ext -i` and this produced a broken install.
>

 This is for development, in just modify your PYTHONPATH to include the
 repo. See beancount/etc/env

>>>
>>> Sorry, I think I'm missing something more basic; things were very broken
>>> just following the instructions.  I do notice there is a Makefile in the
>>> directory, is running `make` supposed to be part of the install-from-source
>>> or install-for-dev process?
>>>
>>> The instructions just say to run setup.py but that doesn't seem to do
>>> much.
>>>
>>> I'm also not sure if I'm even following the right instructions since, as
>>> I mentioned, the document itself says it's for installing v2, and the link
>>> to instructions for installing v3 is broken (links to
>>> https://beancount.github.io/docs/installing_beancount_v3.md )
>>>
>>>


> Backing out of that and just running `apt install beancount` worked
> fine though :-D
>
>
>
>> (Apologies for the little warning in every invocation.)
>>
>> On Sat, Jul 15, 2023, 07:42 Eric Altendorf 
>> wrote:
>>
>>> I'd like to get started with Beancount, and it wasn't clear to me if
>>> the docs have been updated recently.  Is v3 still considered unstable, 
>>> and
>>> it's best to use v2?
>>>
>>> thanks,
>>> eric
>>>
>>> --
>>> 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 beancount+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/beancount/1f684516-bd76-4ff5-adcb-b2b15b28b6a6n%40googlegroups.com
>>> 

Re: Is v2 > v3 still?

[Martin Blais]

Precisely reliable and reproducible packaging and instructions that work
for everyone all the time are impossible tasks in my experience and I tried
for 25 years and eventually gave up. Too many environments, to many
different users and setups. I keep it simple for dev which I think is the
key, best is to use it like that to get the freshest. Other people do
packaging. Packages will inevitably be slightly older. Here's the gist:

- "make build" will compile a .so in place (in the tree where you can
import it). Needs a C compiler with Python dev headers and library, bison
and flex.
- set your PYTHONPATH to be able to import directly from the tree.

Hope this helps,





On Mon, Jul 17, 2023, 02:37 Eric Altendorf  wrote:

> Aha, looks like this is the page:
> https://beancount.github.io/docs/installing_beancount_v3.html
>
> I'll work from that.  Just sharing the FYI that some of the install
> instructions / links seem to be misleading.
>
> On Sun, Jul 16, 2023 at 10:19 AM Eric Altendorf 
> wrote:
>
>> On Fri, Jul 14, 2023 at 8:35 PM Martin Blais  wrote:
>>
>>>
>>>
>>> On Sat, Jul 15, 2023, 11:06 Eric Altendorf 
>>> wrote:
>>>
 On Fri, Jul 14, 2023 at 4:45 PM Martin Blais  wrote:

> v3 > v2
> No less stable; less overall code, many parts moved to subprojects
> that have been more actively developed. Some c++ bit present but not used
> in the main loop.
> Use v3.
>

 Cool.  FWIW, https://beancount.github.io/ still says v3 "is unstable
 and you want to use version 2 below".

>>>
>>> All types of users, this is largely for non technical users. It's stable
>>> enough for you. I try not to commit build breaking changes (lots of tests).
>>>
>>
>> OK.  Looks like `apt install` just gives me v2, so I removed that and I'm
>> back to installing from source.  I'd like to install for dev, in case I
>> want to experiment with writing my own booking algorithm.
>>
>>
>>>
>>>
>>> And https://beancount.github.io/docs/installing_beancount.html says it
 is instructions for installing v2.

 Also I tried following the "Installing for Development" instructions
 there, running git clone, then `sudo python3 setup.py develop` and `python3
 setup.py build_ext -i` and this produced a broken install.

>>>
>>> This is for development, in just modify your PYTHONPATH to include the
>>> repo. See beancount/etc/env
>>>
>>
>> Sorry, I think I'm missing something more basic; things were very broken
>> just following the instructions.  I do notice there is a Makefile in the
>> directory, is running `make` supposed to be part of the install-from-source
>> or install-for-dev process?
>>
>> The instructions just say to run setup.py but that doesn't seem to do
>> much.
>>
>> I'm also not sure if I'm even following the right instructions since, as
>> I mentioned, the document itself says it's for installing v2, and the link
>> to instructions for installing v3 is broken (links to
>> https://beancount.github.io/docs/installing_beancount_v3.md )
>>
>>
>>>
>>>
 Backing out of that and just running `apt install beancount` worked
 fine though :-D



> (Apologies for the little warning in every invocation.)
>
> On Sat, Jul 15, 2023, 07:42 Eric Altendorf 
> wrote:
>
>> I'd like to get started with Beancount, and it wasn't clear to me if
>> the docs have been updated recently.  Is v3 still considered unstable, 
>> and
>> it's best to use v2?
>>
>> thanks,
>> eric
>>
>> --
>> 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 beancount+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beancount/1f684516-bd76-4ff5-adcb-b2b15b28b6a6n%40googlegroups.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Beancount" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beancount/LVBQ4cD0PYc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beancount+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beancount/CAK21%2BhOasM-ix1nUcL5LwykQpmQefjrtD9RNRVy53K_VPthCrQ%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 

Re: Is v2 > v3 still?

[Eric Altendorf]

Aha, looks like this is the page:
https://beancount.github.io/docs/installing_beancount_v3.html

I'll work from that.  Just sharing the FYI that some of the install
instructions / links seem to be misleading.

On Sun, Jul 16, 2023 at 10:19 AM Eric Altendorf 
wrote:

> On Fri, Jul 14, 2023 at 8:35 PM Martin Blais  wrote:
>
>>
>>
>> On Sat, Jul 15, 2023, 11:06 Eric Altendorf 
>> wrote:
>>
>>> On Fri, Jul 14, 2023 at 4:45 PM Martin Blais  wrote:
>>>
 v3 > v2
 No less stable; less overall code, many parts moved to subprojects that
 have been more actively developed. Some c++ bit present but not used in the
 main loop.
 Use v3.

>>>
>>> Cool.  FWIW, https://beancount.github.io/ still says v3 "is unstable
>>> and you want to use version 2 below".
>>>
>>
>> All types of users, this is largely for non technical users. It's stable
>> enough for you. I try not to commit build breaking changes (lots of tests).
>>
>
> OK.  Looks like `apt install` just gives me v2, so I removed that and I'm
> back to installing from source.  I'd like to install for dev, in case I
> want to experiment with writing my own booking algorithm.
>
>
>>
>>
>> And https://beancount.github.io/docs/installing_beancount.html says it
>>> is instructions for installing v2.
>>>
>>> Also I tried following the "Installing for Development" instructions
>>> there, running git clone, then `sudo python3 setup.py develop` and `python3
>>> setup.py build_ext -i` and this produced a broken install.
>>>
>>
>> This is for development, in just modify your PYTHONPATH to include the
>> repo. See beancount/etc/env
>>
>
> Sorry, I think I'm missing something more basic; things were very broken
> just following the instructions.  I do notice there is a Makefile in the
> directory, is running `make` supposed to be part of the install-from-source
> or install-for-dev process?
>
> The instructions just say to run setup.py but that doesn't seem to do much.
>
> I'm also not sure if I'm even following the right instructions since, as I
> mentioned, the document itself says it's for installing v2, and the link to
> instructions for installing v3 is broken (links to
> https://beancount.github.io/docs/installing_beancount_v3.md )
>
>
>>
>>
>>> Backing out of that and just running `apt install beancount` worked fine
>>> though :-D
>>>
>>>
>>>
 (Apologies for the little warning in every invocation.)

 On Sat, Jul 15, 2023, 07:42 Eric Altendorf 
 wrote:

> I'd like to get started with Beancount, and it wasn't clear to me if
> the docs have been updated recently.  Is v3 still considered unstable, and
> it's best to use v2?
>
> thanks,
> eric
>
> --
> 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 beancount+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beancount/1f684516-bd76-4ff5-adcb-b2b15b28b6a6n%40googlegroups.com
> 
> .
>
 --
 You received this message because you are subscribed to a topic in the
 Google Groups "Beancount" group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/beancount/LVBQ4cD0PYc/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beancount+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/beancount/CAK21%2BhOasM-ix1nUcL5LwykQpmQefjrtD9RNRVy53K_VPthCrQ%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 beancount+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/beancount/CAFXPr0vzhgK2oJihR8eZLfwboFpaQWvm8wR%3Dj0sBUd3TMmOkzQ%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 beancount+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beancount/CAK21%2BhN5vkWmTc2D2RUBCT2hJ_b6WZqO7W986cLhCsLSkJE4sg%40mail.gmail.com
>> 

Re: Is v2 > v3 still?

[Eric Altendorf]

On Fri, Jul 14, 2023 at 8:35 PM Martin Blais  wrote:

>
>
> On Sat, Jul 15, 2023, 11:06 Eric Altendorf 
> wrote:
>
>> On Fri, Jul 14, 2023 at 4:45 PM Martin Blais  wrote:
>>
>>> v3 > v2
>>> No less stable; less overall code, many parts moved to subprojects that
>>> have been more actively developed. Some c++ bit present but not used in the
>>> main loop.
>>> Use v3.
>>>
>>
>> Cool.  FWIW, https://beancount.github.io/ still says v3 "is unstable and
>> you want to use version 2 below".
>>
>
> All types of users, this is largely for non technical users. It's stable
> enough for you. I try not to commit build breaking changes (lots of tests).
>

OK.  Looks like `apt install` just gives me v2, so I removed that and I'm
back to installing from source.  I'd like to install for dev, in case I
want to experiment with writing my own booking algorithm.


>
>
> And https://beancount.github.io/docs/installing_beancount.html says it is
>> instructions for installing v2.
>>
>> Also I tried following the "Installing for Development" instructions
>> there, running git clone, then `sudo python3 setup.py develop` and `python3
>> setup.py build_ext -i` and this produced a broken install.
>>
>
> This is for development, in just modify your PYTHONPATH to include the
> repo. See beancount/etc/env
>

Sorry, I think I'm missing something more basic; things were very broken
just following the instructions.  I do notice there is a Makefile in the
directory, is running `make` supposed to be part of the install-from-source
or install-for-dev process?

The instructions just say to run setup.py but that doesn't seem to do much.

I'm also not sure if I'm even following the right instructions since, as I
mentioned, the document itself says it's for installing v2, and the link to
instructions for installing v3 is broken (links to
https://beancount.github.io/docs/installing_beancount_v3.md )


>
>
>> Backing out of that and just running `apt install beancount` worked fine
>> though :-D
>>
>>
>>
>>> (Apologies for the little warning in every invocation.)
>>>
>>> On Sat, Jul 15, 2023, 07:42 Eric Altendorf 
>>> wrote:
>>>
 I'd like to get started with Beancount, and it wasn't clear to me if
 the docs have been updated recently.  Is v3 still considered unstable, and
 it's best to use v2?

 thanks,
 eric

 --
 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 beancount+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/beancount/1f684516-bd76-4ff5-adcb-b2b15b28b6a6n%40googlegroups.com
 
 .

>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Beancount" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/beancount/LVBQ4cD0PYc/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> beancount+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/beancount/CAK21%2BhOasM-ix1nUcL5LwykQpmQefjrtD9RNRVy53K_VPthCrQ%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 beancount+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beancount/CAFXPr0vzhgK2oJihR8eZLfwboFpaQWvm8wR%3Dj0sBUd3TMmOkzQ%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 beancount+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beancount/CAK21%2BhN5vkWmTc2D2RUBCT2hJ_b6WZqO7W986cLhCsLSkJE4sg%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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Re: Is v2 > v3 still?

[Martin Blais]

On Sat, Jul 15, 2023, 11:06 Eric Altendorf  wrote:

> On Fri, Jul 14, 2023 at 4:45 PM Martin Blais  wrote:
>
>> v3 > v2
>> No less stable; less overall code, many parts moved to subprojects that
>> have been more actively developed. Some c++ bit present but not used in the
>> main loop.
>> Use v3.
>>
>
> Cool.  FWIW, https://beancount.github.io/ still says v3 "is unstable and
> you want to use version 2 below".
>

All types of users, this is largely for non technical users. It's stable
enough for you. I try not to commit build breaking changes (lots of tests).


And https://beancount.github.io/docs/installing_beancount.html says it is
> instructions for installing v2.
>
> Also I tried following the "Installing for Development" instructions
> there, running git clone, then `sudo python3 setup.py develop` and `python3
> setup.py build_ext -i` and this produced a broken install.
>

This is for development, in just modify your PYTHONPATH to include the
repo. See beancount/etc/env


> Backing out of that and just running `apt install beancount` worked fine
> though :-D
>
>
>
>> (Apologies for the little warning in every invocation.)
>>
>> On Sat, Jul 15, 2023, 07:42 Eric Altendorf 
>> wrote:
>>
>>> I'd like to get started with Beancount, and it wasn't clear to me if the
>>> docs have been updated recently.  Is v3 still considered unstable, and it's
>>> best to use v2?
>>>
>>> thanks,
>>> eric
>>>
>>> --
>>> 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 beancount+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/beancount/1f684516-bd76-4ff5-adcb-b2b15b28b6a6n%40googlegroups.com
>>> 
>>> .
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Beancount" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beancount/LVBQ4cD0PYc/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beancount+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beancount/CAK21%2BhOasM-ix1nUcL5LwykQpmQefjrtD9RNRVy53K_VPthCrQ%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 beancount+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beancount/CAFXPr0vzhgK2oJihR8eZLfwboFpaQWvm8wR%3Dj0sBUd3TMmOkzQ%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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/CAK21%2BhN5vkWmTc2D2RUBCT2hJ_b6WZqO7W986cLhCsLSkJE4sg%40mail.gmail.com.

Re: Is v2 > v3 still?

[Eric Altendorf]

On Fri, Jul 14, 2023 at 4:45 PM Martin Blais  wrote:

> v3 > v2
> No less stable; less overall code, many parts moved to subprojects that
> have been more actively developed. Some c++ bit present but not used in the
> main loop.
> Use v3.
>

Cool.  FWIW, https://beancount.github.io/ still says v3 "is unstable and
you want to use version 2 below".  And
https://beancount.github.io/docs/installing_beancount.html says it is
instructions for installing v2.

Also I tried following the "Installing for Development" instructions there,
running git clone, then `sudo python3 setup.py develop` and `python3
setup.py build_ext -i` and this produced a broken install.

Backing out of that and just running `apt install beancount` worked fine
though :-D



> (Apologies for the little warning in every invocation.)
>
> On Sat, Jul 15, 2023, 07:42 Eric Altendorf 
> wrote:
>
>> I'd like to get started with Beancount, and it wasn't clear to me if the
>> docs have been updated recently.  Is v3 still considered unstable, and it's
>> best to use v2?
>>
>> thanks,
>> eric
>>
>> --
>> 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 beancount+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beancount/1f684516-bd76-4ff5-adcb-b2b15b28b6a6n%40googlegroups.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Beancount" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beancount/LVBQ4cD0PYc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beancount+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beancount/CAK21%2BhOasM-ix1nUcL5LwykQpmQefjrtD9RNRVy53K_VPthCrQ%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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/CAFXPr0vzhgK2oJihR8eZLfwboFpaQWvm8wR%3Dj0sBUd3TMmOkzQ%40mail.gmail.com.

Re: Is v2 > v3 still?

[Martin Blais]

v3 > v2
No less stable; less overall code, many parts moved to subprojects that
have been more actively developed. Some c++ bit present but not used in the
main loop.
Use v3.

(Apologies for the little warning in every invocation.)

On Sat, Jul 15, 2023, 07:42 Eric Altendorf  wrote:

> I'd like to get started with Beancount, and it wasn't clear to me if the
> docs have been updated recently.  Is v3 still considered unstable, and it's
> best to use v2?
>
> thanks,
> eric
>
> --
> 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 beancount+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beancount/1f684516-bd76-4ff5-adcb-b2b15b28b6a6n%40googlegroups.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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/CAK21%2BhOasM-ix1nUcL5LwykQpmQefjrtD9RNRVy53K_VPthCrQ%40mail.gmail.com.