You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a timeline for a legitimate R package for synapse instead of this daisy chain of conda -> mamba -> reticulate dependencies? It has to be way harder to support this over time than just building a good R port.
Apologies for the troubles @rbutleriii. First, thank you for the feedback! We have seen requests here and there over the years to maintain a sole R client but the Python client is still mainly used over synapser. Docs here: https://python-docs.synapse.org/
For some context, there was a sole R client years ago, but synapser was created due to the mismatches in feature space between the sole R and Python client and the Python client became more maintained than the R client. The development of synapser meant that features like caching, asynchronous multi-part downloads being implemented within the Python client will automatically be used in the R client. To build and maintain a sole R client would require us to prioritize our resources in that context and actually takes more time to develop than maintaining this.
As for these issues, the Python client currently doesn't support Python 3.11, so I would downgrade the Python version and please follow the installation guide here: https://r-docs.synapse.org/articles/installation.html. We tested the installation of this package across linux, windows and mac with 4 separate R minor versions (R 4.1, 4.2, 4.3, 4.4). Please let us know if you have any other questions.
Is there a timeline for a legitimate R package for synapse instead of this daisy chain of conda -> mamba -> reticulate dependencies? It has to be way harder to support this over time than just building a good R port.
The text was updated successfully, but these errors were encountered: