owlplanner 2025.2.14__tar.gz → 2025.2.19__tar.gz

{owlplanner-2025.2.14 → owlplanner-2025.2.19}/.github/workflows/github-actions-runtests.yml

@@ -11,7 +11,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        python-version: ["3.9", "3.10", "3.12"]
+        python-version: ["3.9", "3.10", "3.12", "3.13"]
 
     steps:
     - uses: actions/checkout@v4

{owlplanner-2025.2.14 → owlplanner-2025.2.19}/INSTALL.md

@@ -1,18 +1,21 @@
-## Installation steps
+# Owl
 
-### To install and run a Docker image, please see these [instructions](docker/README.md).
+## A retirement exploration tool based on linear programming
+
+<img align=right src="https://raw.github.com/mdlacasse/Owl/main/docs/images/owl.png" width="250">
+
+------------------------------------------------------------------------------------
+### About
+This document is aimed at software developers desiring to install the Owl source code
+and run it locally on their computer.
+
+For end-users, we suggest accessing Owl from the [Streamlit Community Server](http://owlplanner.streamlit.app)
+or, if one prefers to have everything on their own computer,
+to install and run a Docker image as described in these [instructions](docker/README.md).
 
 ### Requirements
-These instructions are for installing the Python source code for Owl and run it on your computer.
 You will need Python and `pip` installed on your computer for that purpose.
 
-### Installation steps for end-users
-You can install the Owl package directly from the [Python Package Index](http://pypi.org).
-The following command will install the current version of owlplanner and all its dependencies:
-```shell
-pip install -r ui/requirements.txt
-```
-
 ### Installation steps for developers
 These instructions are command-line instructions.
 You will need the latest version of Owl from GitHub.
@@ -27,12 +30,13 @@ python -m build
 pip install -e .
 ```
 The -e instructs Python to load the live version in the current directory tree. 
+
 ### Running the streamlit frontend 
 Running the Owl user interface locally from Windows:
 ```shell
 ./owlplanner.cmd
 ```
-From Linux or MacOS:
+Running the Owl user interface locally from Linux or MacOS:
 ```shell
 ./owlplanner.sh
 ```
@@ -50,3 +54,11 @@ python -m build
 twine upload --repository [repo] dist/*
 ```
 where [repo] is *testpypi* or *pypi* depending on the type of release.
+
+### Installation steps for Python package only
+You can install the Owl package directly from the [Python Package Index](http://pypi.org).
+The following command will install the current version of owlplanner and all its dependencies:
+```shell
+pip install -r ui/requirements.txt
+```
+

{owlplanner-2025.2.14 → owlplanner-2025.2.19}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: owlplanner
-Version: 2025.2.14
+Version: 2025.2.19
 Summary: Owl: Retirement planner with great wisdom
 Project-URL: HomePage, https://github.com/mdlacasse/owl
 Project-URL: Repository, https://github.com/mdlacasse/owl
@@ -708,7 +708,7 @@ Description-Content-Type: text/markdown
 
 <img align=right src="https://raw.github.com/mdlacasse/Owl/main/docs/images/owl.png" width="250">
 
------
+-------------------------------------------------------------------------------------
 
 ### TL;DR
 Owl is a planning tool that uses a linear programming optimization algorithm to provide guidance on retirement decisions. There are a few ways to run Owl.
@@ -719,10 +719,10 @@ Owl is a planning tool that uses a linear programming optimization algorithm to
 Follow these [instructions](docker/README.md) for this option.
 
 - Run locally on your computer using Python code and libraries.
-Follow there [instructions](INSTALL.md) to install Owl from the source code and run it on your computer.
-
------
+Follow these [instructions](INSTALL.md) to install Owl from the source code and run it on your computer.
 
+-------------------------------------------------------------------------------------
+## Overview
 This package is a retirement modeling framework for exploring the sensitivity of retirement financial decisions.
 Strictly speaking, it is not a planning tool, but more an environment for exploring *what if* scenarios.
 It provides different realizations of a financial strategy through the rigorous
@@ -789,7 +789,7 @@ Other asset classes can easily be added, but would add complexity while only pro
 Historical data used are from
 [Aswath Damodaran](https://pages.stern.nyu.edu/~adamodar/) at the Stern School of Business.
 Asset allocations are selected for the duration of the plan, and these can glide linearly
-or along a configurable s-curve from now to the last year of the plan.
+or along a configurable s-curve over the lifespan of the individual.
 
 Spending profiles are adjusted for inflation, and so are all other indexable quantities. Proflies can be
 flat or follow a *smile* curve which is also adjustable through two simple parameters.
@@ -800,10 +800,10 @@ the statistical characteristics (means and covariance matrix) of
 a selected historical year range. Pure *stochastic* rates can also be generated
 if the user provides means, volatility (expressed as standard deviation), and optionally
 the correlations between the different assets return rates provided as a matrix, or a list of
-the off-diagonal elements (see the notebook tutorial for details).
+the off-diagonal elements (see documentation for details).
 Average rates calculated over a historical data period can also be chosen.
 
-Monte Carlo simulations capabilities are included  and provide a probability of success and a histogram of
+Monte Carlo simulations capabilities are included and provide a probability of success and a histogram of
 outcomes. These simulations can be used for either determining the probability distribution of the
 maximum net spending amount under
 the constraint of a desired bequest, or the probability distribution of the maximum
@@ -812,33 +812,36 @@ simulators, Owl uses an optimization algorithm for every new scenario, which res
 calculations being performed. As a result, the number of cases to be considered should be kept
 to a reasonable number. For a few hundred cases, a few minutes of calculations can provide very good estimates
 and reliable probability distributions.
-Optimizing each solution is more representative in the sense that optimal solutions
+
+Optimizing each solution is more representative than event-base simulators
+in the sense that optimal solutions
 will naturally adjust to the return scenarios being considered.
 This is more realistic as retirees would certainly re-evaluate
 their expectations under severe market drops or gains.
-This optimal approach provides a net benefit over event-based simulations,
+This optimal approach provides a net benefit over event-based simulators,
 which maintain a distribution strategy either fixed, or within guardrails for capturing the
- retirees' reactions to the market.
+retirees' reactions to the market.
 
-Basic input parameters are given through function calls while optional additional time series can be read from
+Basic input parameters can be entered through the user interface
+while optional additional time series can be read from
 an Excel spreadsheet that contains future wages, contributions
 to savings accounts, and planned *big-ticket items* such as the purchase of a lake house,
 the sale of a boat, large gifts, or inheritance.
 
 Three types of savings accounts are considered: taxable, tax-deferred, and tax-exempt,
 which are all tracked separately for married individuals. Asset transition to the surviving spouse
-is done according to beneficiary fractions for each account type.
+is done according to beneficiary fractions for each type of savings account.
 Tax status covers married filing jointly and single, depending on the number of individuals reported.
 
-Medicare and IRMAA calculations are performed through a self-consistent loop on cash flow constraints. Future
-values are simple projections of current values with the assumed inflation rates.
+Medicare and IRMAA calculations are performed through a self-consistent loop on cash flow constraints.
+Future values are simple projections of current values with the assumed inflation rates.
 
 ### Limitations
 Owl is work in progress. At the current time:
 - Only the US federal income tax is considered (and minimized through the optimization algorithm).
 Head of household filing status has not been added but can easily be.
 - Required minimum distributions are calculated, but tables for spouses more than 10 years apart are not included.
-An error message will be generated for these cases.
+These cases are detected and will generate an error message.
 - Social security rule for surviving spouse assumes that benefits were taken at full retirement age.
 - Current version has no optimization of asset allocations between individuals and/or types of savings accounts.
 If there is interest, that could be added in the future.
@@ -847,12 +850,12 @@ If there is interest, that could be added in the future.
 This means that the Medicare premiums are calculated after an initial solution is generated,
 and then a new solution is re-generated with these premiums as a constraint.
 In some situations, when the income (MAGI) is near an IRMAA bracket, oscillatory solutions can arise.
-Owl will detect these cases and inform the user.
-While the solutions generated are very close to one another, Owl will pick the smallest one
+While the solutions generated are very close to one another, Owl will pick the smallest solution
 for being conservative.
-- Part D is not included in the IRMAA calculations. Being considerably more, only Part B is taken into account. 
-- Future tax brackets are pure speculations derived from the little we know now and projected to the next 30 years. Your guesses are as good as mine.
-Having a knob to adjust future rates might be an interesting feature to add for measuring the impact on Roth conversions.
+- Part D is not included in the IRMAA calculations. Being considerably more significant,
+only Part B is taken into account. 
+- Future tax brackets are pure speculations derived from the little we know now and projected to the next 30 years.
+Your guesses are as good as mine.
 
 The solution from an optimization algorithm has only two states: feasible and infeasible.
 Therefore, unlike event-driven simulators that can tell you that your distribution strategy runs
@@ -867,7 +870,7 @@ assets to support, even with no estate being left.
 
 - Documentation for the app user interface is available from the interface itself.
 - Installation guide and software requirements can be found [here](INSTALL.md).
-- User guide for the underlying library to be used in a Jupyter notebook can be found [here](USER_GUIDE.md).
+- User guide for the underlying Python package as used in a Jupyter notebook can be found [here](USER_GUIDE.md).
 
 ---------------------------------------------------------------------
 
@@ -876,13 +879,14 @@ assets to support, even with no estate being left.
 - Image from [freepik](https://freepik.com)
 - Optimization solver from [HiGHS](https://highs.dev)
 - Streamlit Community Cloud [Streamlit](https://streamlit.io)
-- Other contributors: Josh (noimjosh@gmail.com) for Docker image code
+- Contributors: Josh (noimjosh@gmail.com) for Docker image code
 
 ---------------------------------------------------------------------
 
 Copyright &copy; 2024 - Martin-D. Lacasse
 
-Disclaimers: I am not a financial planner. You make your own decisions. This program comes with no guarantee. Use at your own risk.
+Disclaimers: I am not a financial planner. You make your own decisions.
+This program comes with no guarantee. Use at your own risk.
 
 --------------------------------------------------------
 

{owlplanner-2025.2.14 → owlplanner-2025.2.19}/README.md

@@ -5,7 +5,7 @@
 
 <img align=right src="https://raw.github.com/mdlacasse/Owl/main/docs/images/owl.png" width="250">
 
------
+-------------------------------------------------------------------------------------
 
 ### TL;DR
 Owl is a planning tool that uses a linear programming optimization algorithm to provide guidance on retirement decisions. There are a few ways to run Owl.
@@ -16,10 +16,10 @@ Owl is a planning tool that uses a linear programming optimization algorithm to
 Follow these [instructions](docker/README.md) for this option.
 
 - Run locally on your computer using Python code and libraries.
-Follow there [instructions](INSTALL.md) to install Owl from the source code and run it on your computer.
-
------
+Follow these [instructions](INSTALL.md) to install Owl from the source code and run it on your computer.
 
+-------------------------------------------------------------------------------------
+## Overview
 This package is a retirement modeling framework for exploring the sensitivity of retirement financial decisions.
 Strictly speaking, it is not a planning tool, but more an environment for exploring *what if* scenarios.
 It provides different realizations of a financial strategy through the rigorous
@@ -86,7 +86,7 @@ Other asset classes can easily be added, but would add complexity while only pro
 Historical data used are from
 [Aswath Damodaran](https://pages.stern.nyu.edu/~adamodar/) at the Stern School of Business.
 Asset allocations are selected for the duration of the plan, and these can glide linearly
-or along a configurable s-curve from now to the last year of the plan.
+or along a configurable s-curve over the lifespan of the individual.
 
 Spending profiles are adjusted for inflation, and so are all other indexable quantities. Proflies can be
 flat or follow a *smile* curve which is also adjustable through two simple parameters.
@@ -97,10 +97,10 @@ the statistical characteristics (means and covariance matrix) of
 a selected historical year range. Pure *stochastic* rates can also be generated
 if the user provides means, volatility (expressed as standard deviation), and optionally
 the correlations between the different assets return rates provided as a matrix, or a list of
-the off-diagonal elements (see the notebook tutorial for details).
+the off-diagonal elements (see documentation for details).
 Average rates calculated over a historical data period can also be chosen.
 
-Monte Carlo simulations capabilities are included  and provide a probability of success and a histogram of
+Monte Carlo simulations capabilities are included and provide a probability of success and a histogram of
 outcomes. These simulations can be used for either determining the probability distribution of the
 maximum net spending amount under
 the constraint of a desired bequest, or the probability distribution of the maximum
@@ -109,33 +109,36 @@ simulators, Owl uses an optimization algorithm for every new scenario, which res
 calculations being performed. As a result, the number of cases to be considered should be kept
 to a reasonable number. For a few hundred cases, a few minutes of calculations can provide very good estimates
 and reliable probability distributions.
-Optimizing each solution is more representative in the sense that optimal solutions
+
+Optimizing each solution is more representative than event-base simulators
+in the sense that optimal solutions
 will naturally adjust to the return scenarios being considered.
 This is more realistic as retirees would certainly re-evaluate
 their expectations under severe market drops or gains.
-This optimal approach provides a net benefit over event-based simulations,
+This optimal approach provides a net benefit over event-based simulators,
 which maintain a distribution strategy either fixed, or within guardrails for capturing the
- retirees' reactions to the market.
+retirees' reactions to the market.
 
-Basic input parameters are given through function calls while optional additional time series can be read from
+Basic input parameters can be entered through the user interface
+while optional additional time series can be read from
 an Excel spreadsheet that contains future wages, contributions
 to savings accounts, and planned *big-ticket items* such as the purchase of a lake house,
 the sale of a boat, large gifts, or inheritance.
 
 Three types of savings accounts are considered: taxable, tax-deferred, and tax-exempt,
 which are all tracked separately for married individuals. Asset transition to the surviving spouse
-is done according to beneficiary fractions for each account type.
+is done according to beneficiary fractions for each type of savings account.
 Tax status covers married filing jointly and single, depending on the number of individuals reported.
 
-Medicare and IRMAA calculations are performed through a self-consistent loop on cash flow constraints. Future
-values are simple projections of current values with the assumed inflation rates.
+Medicare and IRMAA calculations are performed through a self-consistent loop on cash flow constraints.
+Future values are simple projections of current values with the assumed inflation rates.
 
 ### Limitations
 Owl is work in progress. At the current time:
 - Only the US federal income tax is considered (and minimized through the optimization algorithm).
 Head of household filing status has not been added but can easily be.
 - Required minimum distributions are calculated, but tables for spouses more than 10 years apart are not included.
-An error message will be generated for these cases.
+These cases are detected and will generate an error message.
 - Social security rule for surviving spouse assumes that benefits were taken at full retirement age.
 - Current version has no optimization of asset allocations between individuals and/or types of savings accounts.
 If there is interest, that could be added in the future.
@@ -144,12 +147,12 @@ If there is interest, that could be added in the future.
 This means that the Medicare premiums are calculated after an initial solution is generated,
 and then a new solution is re-generated with these premiums as a constraint.
 In some situations, when the income (MAGI) is near an IRMAA bracket, oscillatory solutions can arise.
-Owl will detect these cases and inform the user.
-While the solutions generated are very close to one another, Owl will pick the smallest one
+While the solutions generated are very close to one another, Owl will pick the smallest solution
 for being conservative.
-- Part D is not included in the IRMAA calculations. Being considerably more, only Part B is taken into account. 
-- Future tax brackets are pure speculations derived from the little we know now and projected to the next 30 years. Your guesses are as good as mine.
-Having a knob to adjust future rates might be an interesting feature to add for measuring the impact on Roth conversions.
+- Part D is not included in the IRMAA calculations. Being considerably more significant,
+only Part B is taken into account. 
+- Future tax brackets are pure speculations derived from the little we know now and projected to the next 30 years.
+Your guesses are as good as mine.
 
 The solution from an optimization algorithm has only two states: feasible and infeasible.
 Therefore, unlike event-driven simulators that can tell you that your distribution strategy runs
@@ -164,7 +167,7 @@ assets to support, even with no estate being left.
 
 - Documentation for the app user interface is available from the interface itself.
 - Installation guide and software requirements can be found [here](INSTALL.md).
-- User guide for the underlying library to be used in a Jupyter notebook can be found [here](USER_GUIDE.md).
+- User guide for the underlying Python package as used in a Jupyter notebook can be found [here](USER_GUIDE.md).
 
 ---------------------------------------------------------------------
 
@@ -173,13 +176,14 @@ assets to support, even with no estate being left.
 - Image from [freepik](https://freepik.com)
 - Optimization solver from [HiGHS](https://highs.dev)
 - Streamlit Community Cloud [Streamlit](https://streamlit.io)
-- Other contributors: Josh (noimjosh@gmail.com) for Docker image code
+- Contributors: Josh (noimjosh@gmail.com) for Docker image code
 
 ---------------------------------------------------------------------
 
 Copyright &copy; 2024 - Martin-D. Lacasse
 
-Disclaimers: I am not a financial planner. You make your own decisions. This program comes with no guarantee. Use at your own risk.
+Disclaimers: I am not a financial planner. You make your own decisions.
+This program comes with no guarantee. Use at your own risk.
 
 --------------------------------------------------------
 

{owlplanner-2025.2.14 → owlplanner-2025.2.19}/USER_GUIDE.md

@@ -1,10 +1,14 @@
-
-# Owl   
+# Owl
 
 ## A retirement exploration tool based on linear programming
 
 <img align=right src="https://raw.github.com/mdlacasse/Owl/main/docs/images/owl.png" width="250">
 
+------------------------------------------------------------------------------------
+### About
+This document describes the underlying Owl package and how to use it within
+Python scripts or in Jupyter notebooks.
+
 -----------------------------------------------------------------------
 ## An example of Owl's functionality
 With about 10 lines of Python code, one can generate a full case study.

owlplanner-2025.2.19/docker/Dockerfile

@@ -0,0 +1,34 @@
+# docker/Dockerfile
+
+FROM python:3.13-slim
+
+WORKDIR /app
+
+RUN apt-get update; \
+    apt-get upgrade; \
+    apt-get install -y --no-install-recommends \
+        curl \
+        git \
+    ; \
+    rm -rf /var/lib/apt/lists/*
+
+COPY fastentrypoint.sh /usr/bin/entrypoint.sh
+
+RUN chmod 555 /usr/bin/entrypoint.sh
+
+# Build in the container for faster starts.
+RUN python -m pip install --no-cache-dir --upgrade pip
+
+RUN pip install --no-cache-dir build
+
+RUN git clone --depth 1 https://github.com/mdlacasse/Owl.git owl
+
+RUN cd /app/owl && python -m build
+
+RUN cd /app/owl && pip install --no-cache-dir .
+
+EXPOSE 8501
+
+HEALTHCHECK CMD curl --fail http://localhost:8501/_stcore/health
+
+ENTRYPOINT ["/bin/bash", "/usr/bin/entrypoint.sh"]

owlplanner-2025.2.19/docker/README.md

@@ -0,0 +1,74 @@
+# Owl
+
+## A retirement exploration tool based on linear programming
+
+<img align=right src="https://raw.github.com/mdlacasse/Owl/main/docs/images/owl.png" width="250">
+
+------------------------------------------------------------------------------------
+### About
+This document describes how to run Owl using a Docker container.
+
+------------------------------------------------------------------------------------
+### Run Owl without the source code
+Using this approach only requires downloading the Docker image from
+the [Docker Hub](http://hub.docker.com) and having the [Docker](http://docker.com)
+application installed on your computer.
+
+Downloading the Docker image from the command line:
+```
+docker pull owlplanner/owldocker
+```
+Then the container can be started (and stopped) from the command line:
+```
+docker run -p 8501:8501 --rm owlplanner/owldocker
+```
+
+Just point your browser to http://localhost:8501 to access the Owl user interface.
+Owl will run locally and safely through a container on your computer.
+
+One can also use the Docker Desktop graphical user interface for performing the same steps.
+The image *owlplanner/owldocker* can be searched for and downloaded in the 
+*Docker Hub* section of Docker Desktop. Then, on the *Images* section,
+click on the run icon for the image, and use host port 8501 to map to container port 8501.
+
+------------------------------------------------------------------------------------
+### Building the docker image
+This approach requires cloning the Owl package from GitHub,
+and having both Python and Docker installed on your computer.
+
+##### Docker image
+First build the Docker image from the `docker` directory:
+```shell
+cd docker
+docker build --no-cache -t owldocker .
+```
+
+#### Running the container
+The container can be run directly from the command line,
+with the desired port mapping.
+
+```shell
+docker run -p 8501:8501 --rm owldocker
+```
+
+#### Running with docker-compose
+Alternatively, the container can be started using `docker-compose` as follows
+```shell
+docker-compose up
+```
+The compose file maps the host-side port to the container-side port.
+```yml
+services:
+  owl:
+    image: owldocker
+    restart: always
+    ports:
+      - 8501:8501
+networks: {}
+```
+As before, just point your browser to http://localhost:8501 to access the Owl user interface.
+
+------------------------------------------------------------------------------------
+
+#### Credits
+Josh (noimjosh@gmail.com)

{owlplanner-2025.2.14 → owlplanner-2025.2.19}/docker/docker-compose.yml

@@ -1,9 +1,7 @@
 services:
   owl:
-    image: owldocker
+    image: owlplanner/owldocker
     restart: always
     ports:
       - 8501:8501
-    volumes:
-      - /tmp/owl:/app
 networks: {}

owlplanner-2025.2.19/docker/fastentrypoint.sh

@@ -0,0 +1,9 @@
+#/bin/bash
+
+echo "Owl is now running locally: Point your browser to http://localhost:8501"
+if type -P streamlit >& /dev/null; then
+    streamlit run /app/owl/ui/main.py --server.port=8501 --server.address=0.0.0.0 --browser.gatherUsageStats=false
+else
+    python3 -m streamlit run /app/owl/ui/main.py --server.port=8501 --server.address=0.0.0.0 --browser.gatherUsageStats=false
+fi
+

{owlplanner-2025.2.14 → owlplanner-2025.2.19}/examples/case_jack+jill.toml

@@ -28,6 +28,7 @@ Names = [ "Jack", "Jill",]
 "Heirs rate on tax-deferred estate" = 30.0
 "Long-term capital gain tax rate" = 15.0
 "Dividend tax rate" = 2.0
+"TCJA expiration year" = 2026
 Method = "historical"
 From = 1969
 To = 2002

{owlplanner-2025.2.14 → owlplanner-2025.2.19}/examples/case_joe.toml

@@ -26,6 +26,7 @@ Names = [ "Joe",]
 "Heirs rate on tax-deferred estate" = 30.0
 "Long-term capital gain tax rate" = 15.0
 "Dividend tax rate" = 2.0
+"TCJA expiration year" = 2026
 Method = "historical average"
 From = 1969
 To = 2002

{owlplanner-2025.2.14 → owlplanner-2025.2.19}/examples/case_john+sally.toml

@@ -28,6 +28,7 @@ Names = [ "John", "Sally",]
 "Heirs rate on tax-deferred estate" = 30.0
 "Long-term capital gain tax rate" = 15.0
 "Dividend tax rate" = 2.0
+"TCJA expiration year" = 2026
 Method = "historical average"
 From = 1990
 To = 2023

{owlplanner-2025.2.14 → owlplanner-2025.2.19}/examples/case_kim+sam-bequest.toml

@@ -28,6 +28,7 @@ Names = [ "Kim", "Sam",]
 "Heirs rate on tax-deferred estate" = 33.0
 "Long-term capital gain tax rate" = 15.0
 "Dividend tax rate" = 2.0
+"TCJA expiration year" = 2026
 Method = "conservative"
 From = 1922
 To = 2023

{owlplanner-2025.2.14 → owlplanner-2025.2.19}/examples/case_kim+sam-spending.toml

@@ -28,6 +28,7 @@ Names = [ "Kim", "Sam",]
 "Heirs rate on tax-deferred estate" = 33.0
 "Long-term capital gain tax rate" = 15.0
 "Dividend tax rate" = 2.0
+"TCJA expiration year" = 2026
 Method = "conservative"
 From = 1922
 To = 2023

owlplanner-2025.2.19/owlplanner.cmd

@@ -0,0 +1,20 @@
+@ECHO OFF
+:: Change to suit your specific installation of Python
+set root=C:\Users\%username%\Anaconda3
+call %root%\Scripts\activate.bat
+
+cd ui
+where /q streamlit
+if ERRORLEVEL 1 (
+    where /q python3
+    if ERRORLEVEL 1 (
+        echo Application cannot be started.
+        exit /B
+    ) else (
+        echo Hit Ctrl-C to terminate the server.
+        call python3 -m streamlit run main.py --browser.gatherUsageStats=false --browser.serverAddress=localhost
+    )
+) else (
+    echo Hit Ctrl-C to terminate the Streamlit server.
+    call streamlit run main.py --browser.gatherUsageStats=false --browser.serverAddress=localhost
+)

owlplanner-2025.2.19/owlplanner.sh

@@ -0,0 +1,9 @@
+#!/bin/bash
+
+echo Hit Ctrl-C to terminate the server.
+cd ui
+if type -P streamlit; then
+    streamlit run main.py --browser.gatherUsageStats=false --browser.serverAddress=localhost
+else
+    python3 -m streamlit run main.py --browser.gatherUsageStats=false --browser.serverAddress=localhost
+fi

{owlplanner-2025.2.14 → owlplanner-2025.2.19}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "owlplanner"
-version = "2025.02.14"
+version = "2025.02.19"
 authors = [
   { name="Martin-D. Lacasse", email="martin.d.lacasse@gmail.com" },
 ]

{owlplanner-2025.2.14 → owlplanner-2025.2.19}/src/owlplanner/config.py

@@ -64,6 +64,7 @@ def saveConfig(plan, file, mylog):
         "Heirs rate on tax-deferred estate": float(100 * plan.nu),
         "Long-term capital gain tax rate": float(100 * plan.psi),
         "Dividend tax rate": float(100 * plan.mu),
+        "TCJA expiration year": plan.yTCJA,
         "Method": plan.rateMethod,
     }
     if plan.rateMethod in ["user", "stochastic"]:
@@ -226,6 +227,7 @@ def readConfig(file, *, verbose=True, logstreams=None, readContributions=True):
     p.setDividendRate(float(diconf["Rates Selection"]["Dividend tax rate"]))
     p.setLongTermCapitalTaxRate(float(diconf["Rates Selection"]["Long-term capital gain tax rate"]))
     p.setHeirsTaxRate(float(diconf["Rates Selection"]["Heirs rate on tax-deferred estate"]))
+    p.yTCJA = int(diconf["Rates Selection"]["TCJA expiration year"])
 
     frm = None
     to = None