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

Data bridges client 4.1.0 + wrapper #21

Closed
wants to merge 71 commits into from

Conversation

AlexGherardelli
Copy link
Collaborator

@AlexGherardelli AlexGherardelli commented May 22, 2024

  • Updated data-bridges-client to v4.1.0
  • Created wrapper to simplify loading data into Python and STATA
  • Created example files for wrapper
  • Updated setup.py to include new dependencies
  • Updated README to include usage of wrapper

ValerioGiuffrida and others added 30 commits April 13, 2022 22:18
- added MIT license as agreed with RAM senior management
Auto-generated data_bridges_client, with WFP token refresh workflow
Copy link
Member

@paololucchino paololucchino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @AlexGherardelli and @ValerioGiuffrida, thanks a lot for implementing these features. They are very valuable to make the connection to DataBridges more user-friendly.

I have one substantial design comment that we should consider. At the moment, it seems we are aiming to have one single big package with all the functionality. This can cause some issues: 1) every time we autogenerate the base client package we will need to make sure we are not messing up the other files, 2) users who just want to use the base package will need to install all the dependencies (including STATA).

I would suggest we wrap the utils package around the base one. ie we would have:

  1. base autogenerate python client as a standalone package
  2. utils package that provides helpful wrapper functions and has the base package as a dependency, in two forms:
    • python only
    • an extension that adds the STATA functionality (allowing users who don't need STATA to not install it.

These packages could all live in this repo, in different folders.

What do you think?

cc @delcoker

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.

4 participants