cuemacro/finmarketpy

Python library for backtesting trading strategies & analyzing financial markets (formerly pythalesians)

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Type:Library / SDKCategory(s):Fintech & Quant TradingScience & Industry
Added to GitGenius on September 18th, 2026
Created on February 19th, 2015
Open Issues & Pull Requests: 43 (+0)
GitHub issues: Enabled
Number of forks: 521
Total Stargazers: 3,809 (+0)
Total Subscribers: 207 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 26.8 hours
Mean response time: 6.1 days
90th percentile: 37.2 days
Tracked items: 7

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 11
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 353 days
Stale 30+ days: 11
Stale 90+ days: 11

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

finmarketpy is a Python library for backtesting trading strategies and analyzing financial markets.

The library addresses the need for a unified toolkit to test trading strategies against historical market data and perform quantitative analysis of financial instruments. It provides functionality to construct backtesting workflows, retrieve market data, and evaluate strategy performance across different asset classes and time periods. The tool is designed to streamline the process of moving from strategy conception to empirical validation.

The project suits developers and quantitative analysts building systematic trading systems who need to validate ideas against historical data before deployment. It works well for those analyzing market behavior across multiple instruments and timeframes. The library is particularly relevant for teams that want to avoid building backtesting infrastructure from scratch and prefer a Python-native solution integrated with standard data workflows.

Development activity shows consistent engagement with the codebase. The project maintains regular updates to its core functionality and dependencies. There is ongoing responsiveness to issues raised by users, indicating active maintenance of the tool. The maintainers demonstrate a commitment to keeping the library functional with evolving Python ecosystems and market data sources.