Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider Migrating from alpaca-trade-api to alpaca-py #742

Open
ASRagab opened this issue Aug 13, 2024 · 1 comment
Open

Consider Migrating from alpaca-trade-api to alpaca-py #742

ASRagab opened this issue Aug 13, 2024 · 1 comment

Comments

@ASRagab
Copy link

ASRagab commented Aug 13, 2024

First, thank you for your work and efforts in maintaining this framework.

I would like to change the dependency on alpaca-trade-api to alpaca-py as the former library has been officially deprecated for some time.

Deprecation notice:
https://github.com/alpacahq/alpaca-trade-api-python?tab=readme-ov-file#deprecation-notice

The reason is that some libraries are starting to get stale, specifically the websockets library, and I encountered some dependency conflict warnings.

Here is pipdevtree's report

╰─ pipdeptree --reverse --packages alpaca-trade-api                                                                                                                                                                                                       
Warning!!! Possibly conflicting dependencies found:
* alpaca-trade-api==3.2.0
 - websockets [required: >=9.0,<11, installed: 12.0]

Currently alpaca-py depends on these libraries, which I do not believe conflict with anything in vectorbt

requests = "^2.30.0"
pydantic = "^2.0.3"
pandas = ">=1.5.3"
msgpack = "^1.0.3"
websockets = ">=10.4"
sseclient-py = "^1.7.2"

The changes, I believe, would restricted mostly to a single class and a few supporting files and presumably some documentation. Let me know if you believe this change would be prudent.

@polakowo
Copy link
Owner

Good idea!

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

No branches or pull requests

2 participants