Skip to content

Refactor version retrieval in setup.py to read from __init__.py#986

Merged
mhucka merged 8 commits intotensorflow:masterfrom
whyvineet:chore/unify-version-source
Mar 27, 2026
Merged

Refactor version retrieval in setup.py to read from __init__.py#986
mhucka merged 8 commits intotensorflow:masterfrom
whyvineet:chore/unify-version-source

Conversation

@whyvineet
Copy link
Copy Markdown
Contributor

Resolves #914

@google-cla
Copy link
Copy Markdown

google-cla Bot commented Feb 5, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@mhucka mhucka self-assigned this Feb 5, 2026
@mhucka mhucka added the area/python Involves Python code label Feb 9, 2026
@mhucka mhucka added the area/health Involves general matters of project configuration, health, maintenance, and similar concerns label Feb 25, 2026
@mhucka
Copy link
Copy Markdown
Member

mhucka commented Feb 26, 2026

@whyvineet could you go ahead and look into signing the contributor's license agreement (CLA) mentioned by the google-cla bot comment earlier on this PR?

I realize that the concept of a CLA may be something unfamiliar. It is a common request by companies to external contributors. It allows contributors to Google open-source projects to retain ownership of their code while granting Google the necessary rights to use those contributions. The CLA covers all Google projects, and it only needs to be signed once.

@whyvineet
Copy link
Copy Markdown
Contributor Author

Hey @mhucka, I have already signed the CLA.

@mhucka
Copy link
Copy Markdown
Member

mhucka commented Feb 26, 2026

Hey @mhucka, I have already signed the CLA.

Oh, sorry about that! I should have checked first.

Thanks for taking care of that, and for your work.

@mhucka
Copy link
Copy Markdown
Member

mhucka commented Feb 26, 2026

@whyvineet Could you go ahead and update this branch? (I could also do it, but it's generally better if contributors do it themselves.)

whyvineet and others added 4 commits February 27, 2026 00:27
Changes:

1. Make it use `Path(__file__).resolve().parent` to be more robust about
   resolving file paths.

2. Look for `__init__.py` in a couple of places because of different
   contexts in which setup.py may be called.
@mhucka
Copy link
Copy Markdown
Member

mhucka commented Mar 27, 2026

@whyvineet I took the liberty of making some small changes to the code, and pushed the changes to your branch. Things are testing successfully in CI. If you are happy with the changes, I will merge this PR.

@whyvineet
Copy link
Copy Markdown
Contributor Author

Thanks @mhucka for fixing the CI checks... Feel free to go ahead and merge the PR.

Copy link
Copy Markdown
Member

@mhucka mhucka left a comment

Choose a reason for hiding this comment

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

Thank you for doing this! And for your patience :-).

@mhucka mhucka merged commit b6672db into tensorflow:master Mar 27, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/health Involves general matters of project configuration, health, maintenance, and similar concerns area/python Involves Python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

TFQ version number is defined in two places

2 participants