Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In-Item Exchanges taken into account? #17

Open
fdw opened this issue May 4, 2024 · 6 comments
Open

In-Item Exchanges taken into account? #17

fdw opened this issue May 4, 2024 · 6 comments

Comments

@fdw
Copy link

fdw commented May 4, 2024

Hey, I have another question: Is it possible that transactions which should have a net-0-balance are wrongly taken into account as cash flows? I have a stock which was merged with another (so the value didn't change), but the relative value halved at that date. If the exchange transaction is understood as an influx of money, this makes sense, but it's still wrong. Have you seen this behavior before?

@andreasgerstmayr
Copy link
Owner

To be honest I never tested it with a stock merge (never occurred in my private ledger so far), only with stock splits. Does beangrow handle this properly?

@fdw
Copy link
Author

fdw commented May 7, 2024

Good question... How would I test that? I'm running everything in Docker and couldn't find a way to interact with beangrow directly.

@andreasgerstmayr
Copy link
Owner

beangrow-returns ledger.beancount beangrow.pbtxt output

should generate PDF reports and save them in the output folder. If you've installed it in docker, maybe try docker exec <container> beangrow-returns ...

@fdw
Copy link
Author

fdw commented May 10, 2024

Unfortunately, that crashes with an error:

Traceback (most recent call last):
  File "/app/bin/beangrow-returns", line 8, in <module>
    sys.exit(main())
  File "/app/lib/python3.9/site-packages/beangrow/compute_returns.py", line 100, in main
    reports.write_price_directives(path.join(output_prices, "prices.beancount"),
  File "/app/lib/python3.9/site-packages/beangrow/reports.py", line 411, in write_price_directives
    days_late = (required_date - actual_date).days
TypeError: unsupported operand type(s) for -: 'datetime.date' and 'NoneType'

Do I need to set more parameters?

@andreasgerstmayr
Copy link
Owner

That sounds like an error in beangrow or a malformed ledger, maybe you can open an issue for beangrow.

@fdw
Copy link
Author

fdw commented May 30, 2024

fava-portfolio-returns works fine with this ledger, however. Is this expected?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants