Replies: 2 comments
-
|
So far: Pro
Contra
Another option would be to have two installment scripts for pip, one with the SDK (default) and one without it. Generally, the goal of this whole discussion is to make it easier for users to apply integrations, etc. to the application. We're going to make the SDK a crucial part of the application. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
So, we decided to keep them separate, at least for now, mainly for dependency reasons. But we will keep this an open discussion, as this isn't set in stone. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The Python SDK is an integral part of refinery, as it allows you to both push and pull data directly and further will give some other helpful features such as pushing heuristic results, etc.
We'll arguably commit to Python for a long, long time. So my idea is, should we just move the Python SDK into this repository, so that you have access to the SDK right away? Or at least add it as a dependency so you can use it right out of the box?
Are there any major drawbacks I'm forgetting?
Beta Was this translation helpful? Give feedback.
All reactions