Biweeklybudget

Latest version: v1.2.0

Safety actively analyzes 625010 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 3

1.2.0

- Add tracking of sales tax paid on each transaction.
- Minor build fixes to get this building again.

1.1.1

- Docker build - don\'t include `-dirty` in version/tag when building in GHA
- Document how to change Plaid environments
- GHA - Push built Docker images to Docker Hub, for builds of master branch
- Document triggering a Plaid update via the `/plaid-update` endpoint.
- Change `/plaid-update` endpoint argument name from `account_ids` to `item_ids`.
- Add `num_days` parameter support to `/plaid-update` endpoint.

1.1.0

Breaking Changes

- Support for Python versions prior to 3.8 have been dropped; Docker image and testing is now done against Python 3.10.
- Valid values for the `PLAID_ENV` setting / environment variable are now the strings \"Production\", \"Development\", or \"Sandbox\" to match the attribute names of `plaid.configuration.Environment`. Previously these were lower-case instead of capitalized.
- The `PLAID_PUBLIC_KEY` setting / environment variable has been removed.
- OFX support is now **deprecated**; going forward, only Plaid will be supported.

All Changes

- **Drop Python 2 Support and Python 3.5 Support** - biweeklybudget no longer supports Python 2 (2.7) or Python 3.5. Python versions 3.6-3.8 are tested, and development is now done on 3.8.
- [Issue 201](https://github.com/jantman/biweeklybudget/issues/201) - Fix **major** bug in calculation of \"Remaining\" amount for pay periods, when one or more periodic budgets have a greater amount spent than allocated and a \$0 starting balance. In that case, we were using the allocated amount instead of the spent amount (i.e. if we had a periodic budget with a \$0 starting balance and a \$2 ScheduledTransaction, and converted that ScheduledTransaction to a \$1000 Transaction, the overall PayPeriod remaining amount would be based on the \$2 not the \$1000).
- Add testing for Python 3.7 and 3.8, and make 3.8 the default for tests and tox environments.
- TravisCI updates for Python 3.7 and 3.8.
- Switch base image for Docker from `python:3.6.4-alpine3.7` to `python:3.8.1-alpine3.11`.
- [Issue 198](https://github.com/jantman/biweeklybudget/issues/198) - Fix broken method of retrieving current US Prime Rate. Previously we used marketwatch.com for this but they\'ve introduced javascript-based bot protection on their site (which is ironic since we were reading a value from the page\'s `meta` tags, which are specifically intended to be read by machines). Switch to using wsj.com instead and (ugh) parsing a HTML table. This *will* break when the format of the table changes. As previously, we cache this value in the DB for 48 hours in order to be a good citizen.
- [Issue 197](https://github.com/jantman/biweeklybudget/issues/197) - Add notification for case where balance of all budget-funding accounts is *more* than sum of standing budgets, current payperiod remaining, and unreconciled. This is the opposite of the similar notification that already exists, intended to detect if there is money in accounts not accounted for in the budgets.
- [Issue 196](https://github.com/jantman/biweeklybudget/issues/196) - Don\'t include inactive budgets in Budget select elements on Transaction Modal form, unless it\'s an existing Transaction using that budget.
- [Issue 204](https://github.com/jantman/biweeklybudget/issues/204) - Add support for account transfer between non-Credit accounts.
- Many dependency updates:
- Upgrade SQLAlchemy from 1.2.0 to 1.2.11 for [python 3 bug fix (4291)](https://docs.sqlalchemy.org/en/latest/changelog/changelog_12.html#change-2cca6c216347ab83d04c766452b48c1a).
- Upgrade SQLAlchemy from 1.2.11 to 1.3.13 for [CVE-2019-7548](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-7548) and [CVE-2019-7164](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-7164).
- Upgrade Flask from 0.12.2 to 1.0.2 for [CVE-2018-1000656](https://nvd.nist.gov/vuln/detail/CVE-2018-1000656).
- Upgrade cryptography from 2.1.4 to 2.3.1 for [CVE-2018-10903](https://nvd.nist.gov/vuln/detail/CVE-2018-10903).
- Upgrade Jinja2 from 2.10 to 2.10.3 for [CVE-2019-10906](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10906).
- Upgrade to latest version for all dependencies.
- Remove `convert_unicode` argument from SQLAlchemy DB engine arguments per SQLAlchemy 1.3 upgrade guide / [SQLAlchemy 4393](https://github.com/sqlalchemy/sqlalchemy/issues/4393).
- Numerous updates to fix `tox` tests.
- Implement transaction downloading via [Plaid](https://plaid.com/).
- Switch tests from deprecated `pep8` / `pytest-pep8` packages to `pycodestyle` / `pytest-pycodestyle`.
- Add optional `VERSIONFINDER_DEBUG` env var; set to `true` to enable logging for versionfinder / pip / git.
- Drop testing for Python 3.6; move default test environment to 3.9.
- Add `git` to Docker image.
- Move testing and runtime to Python 3.10, and get all test environments running successfully.
- Move CI from TravisCI to GitHub Actions and remove all traces of TravisCI.
- Add acceptance test coverage of the Plaid Link process.
- Updates for `tox` 4.0.6.
- Update Plaid API client to latest version
- Valid values for the `PLAID_ENV` setting / environment variable are now the strings \"Production\", \"Development\", or \"Sandbox\" to match the attribute names of `plaid.configuration.Environment`.
- The `PLAID_PUBLIC_KEY` setting / environment variable has been removed.

1.0.0

Not secure
- Fix major logic error in Credit Card Payoff calculations; interest fees were ignored for the current month/statement, resulting in \"Next Payment\" values significantly lower than they should be. Fixed to use the last Interest Charge retrieved via OFX (or, if no interest charges present in OFX statements, prompt users to manually enter the last Interest Charge via a new modal that will create an OFXTransaction for it) as the interest amount on the first month/statement when calculating payoffs. This fix now returns Next Payment values that aren\'t identical to sample cards, but are significantly closer (within 1-2%).
- [Issue \105](https://github.com/jantman/biweeklybudget/issues/105) - Major refactor to the Transaction database model. This is transparent to users, but causes massive database and code changes. This is the first step in supporting Transaction splits between multiple budgets:
- A new BudgetTransaction model has been added, which will support a one-to-many association between Transactions and Budgets. This model associates a Transaction with a Budget, and a currency amount counted against that Budget. This first step only supports a one-to-one relationship, but a forthcoming change will implement the one-to-many budget split for Transactions.
- The database migration for this creates BudgetTransactions for every current Transaction, migrating data to the new format.
- The `budget_id` attribute and `budget` relationship of the Transaction model has been removed, as that information is now in the related BudgetTransactions.
- A new `planned_budget_id` attribute (and `planned_budget` relationship) has been added to the Transaction model. For Transactions that were created from ScheduledTransactions, this attribute/relationship stores the original planned budget (distinct from the actual budget now stored in BudgetTransactions).
- The Transaction model now has a `budget_transactions` back-populated property, containing a list of all associated BudgetTransactions.
- The Transaction model now has a `set_budget_amounts()` method which takes a single dict mapping either integer Budget IDs or Budget objects, to the Decimal amount of the Transaction allocated to that Budget. While the underlying API supports an arbitrary number of budgets, the UI and codebase currently only supports one.
- The Transaction constructor now accepts a `budget_amounts` keyword argument that passes its value through to `set_budget_amounts()`, for ease of creating Transactions in one call.
- `Transaction.actual_amount` is no longer an attribute stored in the database, but now a hybrid property (read-only) generated from the sum of amounts of all related BudgetTransactions.
- Add support to serialize property values of models, in addition to attributes.
- Relatively major and sweeping code refactors to support the above.
- Switch tests from using deprecated pytest-capturelog to using pytest built-in log capturing.
- Miscellaneous fixes to unit and acceptance tests, and docs build.
- Finish converting *all* code, including tests and sample data, from using floats to Decimals.
- Acceptance test fix so that pytest-selenium can take full page screenshots with Chromedriver.
- [PR \180](https://github.com/jantman/biweeklybudget/pull/180) - Acceptance test fix so that the testflask LiveServer fixture captures server logs, and includes them in test HTML reports (this generates a temporary file per-test-run outside of pytest\'s control).
- Fix bug found where simultaneously editing the Amount and Budget of an existing Transaction against a Standing Budget would result in incorrect changes to the balances of the Budgets.
- Add a new `migrations` tox environment that automatically tests all database migrations (forward and reverse) and also validates that the database schema created from the migrations matches the one created from the models.
- Add support for writing tests of data manipulation during database migrations, and write tests for the migration in for Issue 105, above.
- Add support for `BIWEEKLYBUDGET_LOG_FILE` environment variable to cause Flask application logs to go to a file *in addition to* STDOUT.
- Add support for `SQL_POOL_PRE_PING` environment variable to enable SQLAlchemy `pool_pre_ping` feature (see [Disconnect Handling - Pessimistic](http://docs.sqlalchemy.org/en/latest/core/pooling.html#pool-disconnects-pessimistic)) for resource-constrained systems.
- Modify acceptance tests to retry up to 3 times, 3 seconds apart, if a ConnectionError (or subclass thereof) is raised when constructing the Selenium driver instance. This is a workaround for intermittent ConnectionResetErrors in TravisCI.
- [Issue \177](https://github.com/jantman/biweeklybudget/issues/177)
- Add SQL query timing support via `SQL_QUERY_PROFILE` environment variable.
- When running under `flask rundev`, append the number of milliseconds taken to serve the request to the werkzeug access log.
- When running under Docker/Gunicorn, append the decimal number of seconds taken to serve the request to the Gunicorn access log.
- [Issue \184](https://github.com/jantman/biweeklybudget/issues/184) - Redact database password from `/help` view, and change `/help` view to show Version containing git commit hash for pre-release/development Docker builds.
- [Issue \183](https://github.com/jantman/biweeklybudget/issues/183)
- Add UI link to ignore reconciling an OFXTransaction if there will not be a matching Transaction.
- Remove default values for the `Account` model\'s `re_` fields in preparation for actually using them.
- Replace the `Account` model\'s `re_fee` field with separate `re_late_fee` and `re_other_fee` fields.
- Add UI support for specifying Interest Charge, Interest Paid, Payment, Late Fee, and Other Fee regexes on each account.
- Add DB event handler on new or changed OFXTransaction, to set `is_*` fields according to Account `re_*` fields.
- Add DB event handler on change to Account model `re_*` fields, that triggers `OFXTransaction.update_is_fields()` to recalculate using the new regex.
- Change `OFXTransaction.unreconciled` to filter out OFXTransactions with any of the `is_*` set to True.
- Upgrade chromedriver in TravisCI builds from 2.33 to 2.36, to fix failing acceptance tests caused by Ubuntu upgrade from Chrome 64 to 65.
- Fix bug in `/budgets` view where \"Spending By Budget, Per Calendar Month\" chart was showing only inactive budgets instead of only active budgets.
- [Issue \178](https://github.com/jantman/biweeklybudget/issues/178) - UI support for splitting Transactions between multiple Budgets.
- Have frontend forms submit as JSON POST instead of urlencoded.
- Properly capture Chrome console logs during acceptance tests.
- Bump `versionfinder` requirement version to 0.1.3 to work with pip 9.0.2.
- On help view, show long version string if we have it.
- [Issue \177](https://github.com/jantman/biweeklybudget/issues/177) - Fix bug in `flask rundev` logging.
- Many workarounds for flaky acceptance tests, including some for the selenium/Chrome \"Element is not clickable at point\... Other element would receive the click\" error.
- `biweeklybudget.screenscraper.ScreenScraper` - Save webdriver and browser logs on failure, and set Chrome to capture all logs.
- `biweeklybudget.screenscraper.ScreenScraper` - Add option to explicitly set a User-Agent on Chrome or PhantomJS.
- [Issue \192](https://github.com/jantman/biweeklybudget/issues/192) - Fix bug where the `is_` fields weren\'t set on OFXTransactions when created via ofxgetter remote API.
- `ofxgetter` - add support to list all accounts at the Institution of one account
- `ofxgetter` - add ability to specify how many days of data to retrieve

0.7.1

Not secure
- [Issue \170](https://github.com/jantman/biweeklybudget/issues/170) - Upgrade **all** python dependencies to their latest versions.
- [Issue \171](https://github.com/jantman/biweeklybudget/issues/171) - Upgrade Docker base image from `python:3.6.3-alpine3.4` to `python:3.6.4-alpine3.7`.
- [Issue \157](https://github.com/jantman/biweeklybudget/issues/157) - Remove PhantomJS from Docker image, as it\'s broken and shouldn\'t be needed.
- Switch TravisCI builds from Docker (`sudo: false`) to VM (`sudo: enabled`) infrastructure.

0.7.0

Not secure
**This version has a remote OFX upload incompatibility. See below.**

- [Issue \156](https://github.com/jantman/biweeklybudget/issues/156) - Add headless chrome support to `screenscraper.py`.
- Remove `pluggy` transient dependency from requirements.txt; was breaking builds.
- Following pytest, drop testing of and support for Python 3.3.
- [Issue \159](https://github.com/jantman/biweeklybudget/issues/159) - Implement internationalization of volume and distance units for Fuel Log pages. This change introduces five new settings: `FUEL_VOLUME_UNIT`, `FUEL_VOLUME_ABBREVIATION`, `DISTANCE_UNIT`, `DISTANCE_UNIT_ABBREVIATION` and `FUEL_ECO_ABBREVIATION`.
- [Issue \154](https://github.com/jantman/biweeklybudget/issues/154) - Fix documentation errors on the Getting Started page, \"Running ofxgetter in Docker\" section.
- [Issue \152](https://github.com/jantman/biweeklybudget/issues/152) - Fix for bug where new Transactions could be entered against inactive budgets. Ensure that existing transactions against inactive budgets can still be edited, but existing transactions cannot be changed to an inactive budget.
- [Issue \161](https://github.com/jantman/biweeklybudget/issues/161) - Fix bug where Transactions against inactive budgets weren\'t counted towards payperiod overall or per-budget totals.
- [Issue \163](https://github.com/jantman/biweeklybudget/issues/163) - Include next payment amount on Credit Payoffs view.
- [Issue \84](https://github.com/jantman/biweeklybudget/issues/84) - Remove vendored-in `ofxparse` package now that [my PR \#127](https://github.com/jseutter/ofxparse/pull/127) has been merged and released on PyPI. **Important note:** The version of ofxparse is changed in this release. If you are using `ofxgetter -r` (remote API mode), the versions of ofxparse (and therefore biweeklybudget/ofxgetter) must match between the client and server.
- [Issue \165](https://github.com/jantman/biweeklybudget/issues/165) - Remove vendored-in `wishlist` package now that [my PR \#8](https://github.com/Jaymon/wishlist/pull/8) has been merged and released on PyPI.
- [Issue \155](https://github.com/jantman/biweeklybudget/issues/155) - Refactor ofxgetter to fix bug where `SETTINGS_MODULE` was still required even if running remotely.

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.