Skip to content

Pin alpha-engine-lib to v0.1.1 for Python 3.9 compat#29

Merged
cipher813 merged 1 commit into
mainfrom
fix/pin-alpha-engine-lib-v011
Apr 14, 2026
Merged

Pin alpha-engine-lib to v0.1.1 for Python 3.9 compat#29
cipher813 merged 1 commit into
mainfrom
fix/pin-alpha-engine-lib-v011

Conversation

@cipher813
Copy link
Copy Markdown
Owner

Summary

One-line pin bump from v0.1.0 → v0.1.1 in requirements.txt. v0.1.1 relaxes the lib's Python floor to `>=3.9` so it installs on the EC2 micro instance. No code change needed on this side.

Why

First manual EC2 test after #28 merged failed with `ModuleNotFoundError: No module named 'alpha_engine_lib'`. Root cause: v0.1.0 declared `requires-python = >=3.11`, and EC2 runs 3.9 — pip silently skipped the install.

Test plan

  • EC2: re-run the same `ae-dashboard` command that failed earlier. `pip install -r requirements.txt` must succeed. weekly_collector.py must hit the preflight and proceed (or fail at the preflight's actual check, not the import).

🤖 Generated with Claude Code

v0.1.0 had requires-python = >=3.11, which caused pip to silently
skip the install on EC2 (running Python 3.9) and surfaced as
ModuleNotFoundError on weekly_collector import.

v0.1.1 relaxes the floor to >=3.9. No runtime code changes needed
on the consumer side — only the pinned tag.

Verified locally: tests pass, import resolves from the v0.1.1 tag.
Next step: re-run manual DailyData on EC2 — pip install should now
succeed.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@cipher813 cipher813 merged commit 2008e3d into main Apr 14, 2026
1 check passed
@cipher813 cipher813 deleted the fix/pin-alpha-engine-lib-v011 branch April 14, 2026 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant