Add deprecation warnings to datacommons and datacommons_pandas packages

[n-h-diaz]

Includes:

• Message at the top of README/long description
• Warning which will be printed when user tries to import the package
• Classifier indicating that the package is no longer in development

Can be viewed on TestPyPI at

• https://test.pypi.org/project/datacommons-nhdiaz/1.4.6/
• https://test.pypi.org/project/datacommons-pandas-nhdiaz/0.0.6/
  (Note that the versions don't align with the PR since I revised the message a few times)

[gemini-code-assist]

Summary of Changes

Hello @n-h-diaz, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request formally deprecates the datacommons and datacommons_pandas Python libraries. The changes introduce clear deprecation warnings in the package documentation and during runtime upon import, alongside metadata updates to reflect their inactive development status. The primary goal is to inform users about the transition to the datacommons_client library and provide guidance for migration, ensuring a smooth transition away from these unmaintained packages.

Highlights

• Deprecation Notices in READMEs: Added a prominent deprecation notice to the README.md files of both datacommons and datacommons_pandas packages, directing users to the new datacommons_client library and a migration guide.
• Runtime Deprecation Warnings: Implemented a DeprecationWarning in the __init__.py files of both packages, ensuring that users receive a warning message upon importing the deprecated libraries.
• Package Metadata Updates: Updated the setup.py files for both datacommons and datacommons_pandas to increment their version numbers and include a Development Status :: 7 - Inactive classifier, signaling that the packages are no longer under active development.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds deprecation warnings to the datacommons and datacommons_pandas packages. The changes correctly add deprecation notices to the READMEs, issue warnings upon import, and update the package classifiers to 'Inactive'. My feedback focuses on improving the warning message shown to users upon import by including a direct link to the migration guide and improving readability, which will enhance the user experience and facilitate a smoother transition to the new library.

[kmoscoe]

Thanks for this!