On Wed, Jul 19, 2023 at 15:56 Andrew Ng <[email protected]> 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 [email protected] 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 > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beancount/5e3adf29-c99f-40d4-98ed-65c735f29190n%40googlegroups.com > <https://groups.google.com/d/msgid/beancount/5e3adf29-c99f-40d4-98ed-65c735f29190n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAFXPr0vVJamAP2e6hY0trEW3vTFW-%3DU8kZ2UWwak67wkzf3v0w%40mail.gmail.com.
