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

Why create a (native) R API client library? #49

Open
jonmcalder opened this issue Nov 21, 2019 · 1 comment
Open

Why create a (native) R API client library? #49

jonmcalder opened this issue Nov 21, 2019 · 1 comment
Assignees

Comments

@jonmcalder
Copy link
Contributor

Pretty sure I know some / most of the reasons why, but thought maybe asking the question could surface some valuable considerations / responses (both for this use case and others like it).

Given the relative ease with which one can use reticulate to call Python functions from R, why not rely on a Python package like hapipy or hubspot3 to retrieve data rather than creating an R package?

i.e. Assuming that (a) the end goal is to retrieve data via an API and use it in R, and (b) a Python API client library exists but no R API client library exists; when should one go to the effort of creating an R API client library?

@stephlocke
Copy link
Collaborator

Mostly dependency management - being able to move at our own speed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants