Skip to content

doc: update epidatr and epidatpy info #1080

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

Merged
merged 1 commit into from
Apr 22, 2025
Merged

doc: update epidatr and epidatpy info #1080

merged 1 commit into from
Apr 22, 2025

Conversation

dshemetov
Copy link
Collaborator

@dshemetov dshemetov commented Apr 22, 2025

Saw some out of date bits on this page while making a QR code link to it on the tooling poster.

Small updates to the client language:

  • take WIP tag out of epidatpy
  • improve the blurb about each client

Copy link

netlify bot commented Apr 22, 2025

Deploy Preview for cmu-delphi-main ready!

Name Link
🔨 Latest commit 0d64e1d
🔍 Latest deploy log https://app.netlify.com/sites/cmu-delphi-main/deploys/6807e6f3c6b0bf0008595d7a
😎 Deploy Preview https://deploy-preview-1080--cmu-delphi-main.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@dshemetov dshemetov merged commit 5151dc2 into dev Apr 22, 2025
7 checks passed
@dshemetov dshemetov deleted the dshemetov-patch-1 branch April 22, 2025 19:43
@melange396
Copy link
Contributor

I'm not convinced we want to take "WIP" off of epidatpy: its overly complicated, it doesnt get much if any internal use, and its not even on PyPI (among other downsides). I think we should still be promoting the delphi-epidata python client: its simple[r], it gets used continually in our integration tests, and its trivial to install.

@dshemetov
Copy link
Collaborator Author

I put a decent bit of effort into shaping up epidatpy and I think it has distinct advantages over the other client, namely in outputting dataframes with reasonably inferred data types for the columns, signal discoverability, and better documentation. I wouldn't say it's 100% perfect, but I'm happy to fix whatever issues users run into. Putting epidatpy on PyPI is also trivial and can be done when a user asks for it.

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.

3 participants