Backtesting and Trading Library, Made by Lumiwealth
Project description
Lumibot - A Backtesting and Trading Library for Stocks, Options, Crypto, Futures, FOREX and More!
Lumibot is a backtesting and trading library for stocks, options, crypto, futures and more. It is made so that the same code you use for backtesting can be used for live trading, making it easy to transition from backtesting to live trading. Lumibot is a highly flexible library that allows you to create your own strategies and indicators, and backtest them on historical data. It is also highly optimized for speed, so you can backtest your strategies quickly and efficiently.
IMPORTANT: This library requires data for backtesting. Our recommended data source is ThetaData because they provide the deepest historical coverage we’ve found and directly support BotSpot. Use the promo code BotSpot10 at checkout for 10% off the first order (the code also tells ThetaData you were referred by us).
Contributor note: Read
AGENTS.mdbefore running anything Theta-related. That file spells out the hard rules—never launch ThetaTerminal or the shared downloader locally, always point LumiBot at the AWS-hosted downloader, and wrap all long commands with/Users/robertgrzesik/bin/safe-timeout. Breaking these rules kills the only licensed Theta session.
Architecture Documentation
docs/BACKTESTING_ARCHITECTURE.md- Detailed documentation of the backtesting data flow (Yahoo, ThetaData, Polygon data sources, caching, and data flow diagrams)docs/ACCEPTANCE_BACKTESTS.md- Manual end-to-end acceptance backtest suite + performance gate (ThetaData)docsrc/environment_variables.rst- Public documentation page for environment variables (update when env vars change)CHANGELOG.md- Deployment/release notes (keep this updated)CLAUDE.md- AI assistant instructions for working with the codebaseAGENTS.md- Critical rules for ThetaData and production safety
Releases / Deployments (internal)
For production deployments (BotSpot / BotManager), keep releases traceable:
- Update
CHANGELOG.mdfor every deploy (include the deploy commit hash) - Tag the deploy commit as
vX.Y.Zand push the tag - Create a GitHub Release from that tag using the
CHANGELOG.mdentry
Documentation - 👇 Start Here 👇
To get started with Lumibot, you can check out our documentation below.
Check out the documentation for the project here: 👉 http://lumibot.lumiwealth.com/ 👈
Build Trading Bots with AI
Want to build trading bots without code? Check out our new platform BotSpot where you can create and deploy trading strategies using AI! BotSpot allows you to:
- Build trading bots using natural language and AI
- Test your strategies with historical data
- Deploy your bots to trade automatically
- Join a community of algorithmic traders
Visit BotSpot.trade to get started building AI-powered trading bots today!
Learn More
Check out example strategies and tutorials on our blog, or use our AI agent to build strategies for you:
Blog: https://lumiwealth.com/blog/ AI Strategy Builder: https://www.botspot.trade/?utm_source=github&utm_medium=referral&utm_campaign=lumibot_readme
Run a backtest
To run a backtest, you can use the following code snippet:
python -m lumibot.example_strategies.stock_buy_and_hold
Backtesting data sources (env override)
You can select a backtesting data source via the BACKTESTING_DATA_SOURCE environment variable (this overrides any explicit datasource_class in code):
# Single-provider backtesting (examples)
export BACKTESTING_DATA_SOURCE=thetadata
export BACKTESTING_DATA_SOURCE=ibkr
Multi-provider routing (by asset type) is supported by setting a JSON mapping:
# Example: ThetaData for stocks/options/indexes, IBKR for futures/crypto
export BACKTESTING_DATA_SOURCE='{"default":"thetadata","stock":"thetadata","option":"thetadata","index":"thetadata","future":"ibkr","crypto":"ibkr"}'
# Example: route crypto to CCXT via a specific exchange id (if desired)
export BACKTESTING_DATA_SOURCE='{"default":"thetadata","crypto":"coinbase"}'
Run an Example Strategy
We made a small example strategy to show you how to use Lumibot in this GitHub repository: Example Algorithm GitHub
To run this example strategy, click on the Deploy to Render button below to deploy the strategy to Render (our recommendation). You can also run the strategy on Repl.it by clicking on the Run on Repl.it button below.
For more information on this example strategy, you can check out the README in the example strategy repository here: Example Algorithm
Contributors
If you want to contribute to Lumibot, you can check how to get started below. We are always looking for contributors to help us out!
Here's a video to help you get started with contributing to Lumibot: Watch The Video
Steps to contribute:
- Watch the video: Watch The Video
- Clone the repository to your local machine
- Create a new branch for your feature
- Run
pip install -r requirements_dev.txtto install the developer dependencies - Install all the requirements from setup.py:
pip install -e . - Make your changes
- Run
pytestto make sure all the tests pass - Create a pull request to merge your branch into master
Running Tests
We use pytest for our testing framework. Some tests require API keys to be in a .env file in the root directory. To run the tests, you can run the following command:
pytest
To run an individual test file, you can run the following command:
pytest tests/test_asset.py
Remote Cache Configuration
Lumibot can mirror its local parquet caches to AWS S3 when you enable the new
backtest cache manager. The feature is optional and defaults to local storage.
To configure the environment variables, understand the key naming convention,
and follow the manual validation checklist, review docs/remote_cache.md.
Showing Code Coverage
To show code coverage, you can run the following command:
coverage run; coverage report; coverage html
Adding an Alias on Linux or MacOS
This will show you the code coverage in the terminal and also create a folder called "htmlcov" which will have a file called "index.html". You can open this file in your browser to see the code coverage in a more readable format.
If you don't want to keep typing out the command, you can add it as an alias in bash. To do this, you can run the following command:
alias cover='coverage run; coverage report; coverage html'
This will now allow you to run the command by just typing "cover" in the terminal.
cover
If you want to also add it to your .bashrc file. You can do this by running the following command:
echo "alias cover='coverage run; coverage report; coverage html'" >> ~/.bashrc
Adding an Alias on Windows
If you are on Windows, you can add an alias by running the following command:
Add to your PowerShell Profile: (profile.ps1)
function cover {
coverage run
coverage report
coverage html
}
Setting Up PyTest in VS Code
To set up in VS Code for debugging, you can add the following to your launch.json file under "configurations". This will allow you to go into "Run and Debug" and run the tests from there, with breakpoints and everything.
NOTE: You may need to change args to the path of your tests folder.
{
"name": "Python: Pytest",
"type": "python",
"request": "launch",
"module": "pytest",
"args": [
"lumibot/tests"
],
"console": "integratedTerminal",
}
Here's an example of an actual launch.json file:
{
"version": "0.2.0",
"configurations": [
{
"name": "Python: Pytest",
"type": "python",
"request": "launch",
"module": "pytest",
"args": [
"lumibot/tests"
],
"console": "integratedTerminal",
}
]
}
Notes on data sources
This table points out some of the differences between the data sources we use in Lumibot. These refer to the data returned in a Bars entity that is returned from calls to get_historical_prices.
| data_source | type | OHLCV | split adjusted | dividends | returns | dividend adjusted returns |
|---|---|---|---|---|---|---|
| yahoo | stock | Yes | Yes | Yes | Yes | Yes |
| alpaca | stock | Yes | Yes | No | Yes | No |
| polygon | stock | Yes | Yes | No | Yes | No |
| Tradier | stock | Yes | Yes | No | Yes | No |
| Pandas* | stock | Yes | Yes | Yes | Yes | Yes |
*Pandas is not a data source per se, but it can load csv files in the same format as Yahoo dataframes, which can contain dividends.
An assortment of git commands our contributors may find useful
Making a new branch and pulling from main:
git checkout -b my-feature
git fetch origin
git merge origin/dev
Committing work to you feature branch:
git add .
git commit -m "my changes"
git push -u origin my-feature
If work on main progressed while you were in another branch, this is how you rebase it into your branch. Note that since you've rebased your local branch, you'll need to force push your changes to update the remote branch. The --force-with-lease option is a safer alternative to --force as it will abort the push if there are any new commits on the remote that you haven't incorporated into your local branch
git checkout dev
git fetch origin
git merge origin/dev
git checkout my-feature
git rebase dev
git checkout my-feature
git push --force-with-lease origin my-feature
When ready to merge the branch into main, go into github, create a pull request, and await review. When your PR is approved it will automatically be merged into the dev branch remotely. Now, you can delete your local branch and the remote branch.
git checkout dev
git fetch origin
git merge origin/dev
git branch -D my-feature
git push origin --delete my-feature
Community
If you want to learn more about Lumibot or Algorithmic Trading then you will love out communities! You can join us on Discord.
Join us on Discord: https://discord.gg/TmMsJCKY3T
Build AI-powered trading bots on BotSpot.trade - Our platform for creating, testing, and deploying trading strategies with AI assistance!
AI Bootcamp
Need hands-on help building your trading bots? Join our AI Bootcamp where you'll learn to build, backtest, and deploy trading strategies using AI—no coding required.
What you'll learn:
- Build stock, crypto, options, and futures bots using plain English prompts
- Master professional tools like VS Code with Copilot and Cursor
- Backtest and deploy your strategies to live brokers
- Join 2,400+ traders in our community
Learn more about the AI Bootcamp
Just want to try the AI? Start your free trial at BotSpot.trade — build strategies in minutes, no coding required.
License
This library is covered by the MIT license for open sourced software which can be found here: https://github.com/Lumiwealth/lumibot/blob/master/LICENSE
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file lumibot-4.4.50.tar.gz.
File metadata
- Download URL: lumibot-4.4.50.tar.gz
- Upload date:
- Size: 37.7 MB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.1.0 CPython/3.13.7
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
0cb21546f79a191146daf70000e176b1841b9209bf4e3f97f7abf1e7595075ec
|
|
| MD5 |
d8346083e616b460932b24676f17d421
|
|
| BLAKE2b-256 |
76c8a65a0a66f0cf2543c373dc64c405cd861ab8bdb19ffdccd9b71687329e7e
|
File details
Details for the file lumibot-4.4.50-py3-none-any.whl.
File metadata
- Download URL: lumibot-4.4.50-py3-none-any.whl
- Upload date:
- Size: 37.4 MB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.1.0 CPython/3.13.7
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
a48ebc47c84663dadfb4440e8d6e65657afd7ca422e3e113c13421c73ac5a343
|
|
| MD5 |
877074a6ad6ab0cfc11a259e6a0750dd
|
|
| BLAKE2b-256 |
c7e486e7bbe09b85d85094091e42688b223d13e82ffac6f772d9d790df14bd22
|