Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion requirements.txt
Original file line number Diff line number Diff line change
Expand Up @@ -8,4 +8,4 @@ pytest
pytz
requests
quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@0063af3b4a974650ea58a7d3f26dd1b94f65d3e8
us-equity-strategies @ git+https://github.com/QuantStrategyLab/UsEquityStrategies.git@64342a1e95a687c29a2be6f0b771e4a7be15b8b8
us-equity-strategies @ git+https://github.com/QuantStrategyLab/UsEquityStrategies.git@46887bc3f5454d5b59623b1f5efb7c65912c6b8b

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep constraints in sync with strategy pin

This updates requirements.txt to UsEquityStrategies commit 46887bc..., but constraints.txt still constrains us-equity-strategies to 64342a... even though it is labeled the single source of truth for git-based SHAs and prior strategy-pin updates changed both files. Any install path that applies the repo constraints alongside these requirements via pip's -c/--constraint option now supplies two different direct refs for the same package, so the dependency pin can be rejected or installed inconsistently; update constraints.txt with the same strategy SHA.

Useful? React with 👍 / 👎.

Loading