Repository navigation
Finalytics 1.0.0-rc.7
Pre-releaseAdded
-
A sample universe for screening:
datasets::universe()in Rust,fl.datasets.universe()in
Python anddatasets.universe()in JavaScript (also through the worker, as
engine.static("datasets", "universe")). It holds 200 fictional companies in eleven sectors,
with six years of daily closes, volumes and quarterly dividends to October 2026, up to five
fields each (name,sector,market_cap,trailing_peandprice_to_book) and a market
index,INDEX, as the benchmark. The library draws it with a fixed seed, the same on every
platform. -
set_show_handlerin Python andsetShowHandlerin JavaScript say whatshow()does with a
report's page: the handler receives the page's HTML instead of a notebook or a browser showing
it. For programs that show pages themselves, such as Python running on Pyodide, which has no
browser to open and raised an error before, or an engine in a worker, which has no page. -
Guides with examples in Python, JavaScript and Rust, in
docs/guidesanddocs/examples.
scripts/guides.pyruns every example in each of its languages and checks that they print
the same, that the output is the one recorded and that every number in a page's prose is one
its examples print; CI runs it on every change. -
The Pyodide build of the Python package runs in CI, and the Release workflow builds and tests
it on each version tag, ready to attach to the GitHub release. PyPI does not take Pyodide
wheels.
Fixed
- Equal weight, inverse volatility, risk parity, risk budgeting and hierarchical risk parity
refusedbenchmark_weightsthat held cash in another currency, such asportfolio.weights()
with itsEUR cash, saying that they "take no other constraints"; so did a comparison or
backtest with one of them and such a benchmark. The engine held that cash at zero in their
problem so that the tracking error counted its risk. They now solve without it, and their
report measures the tracking error with it, as for the other methods.