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

Fix pip build #779

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

jonas-eschle
Copy link

As discussed in #776

I tried but actually run into the issue that layers/experimental cannot be used as a build target, as the builds inside experimental require layers -> circular deps. The other folders in layers circumvent this by specifying only the specific build targets.

Instead of changing the logic (i.e. is experimental meant to be dev-built only?), I did what the error advertised and added it to the ignored builds, as it's seemingly not made to be built

Copy link
Contributor

@haifeng-jin haifeng-jin left a comment

Choose a reason for hiding this comment

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

Thanks for the PR!

@jonas-eschle
Copy link
Author

jonas-eschle commented Jul 3, 2024

@tilakrayal as I am not familiar with the merging process of tf-keras, can this get merged? Or is there more action needed from my side?

@jonas-eschle
Copy link
Author

hi @haifeng-jin can this be merged? It's blocking us downstreams in spack to release new TFP versions

@bernhardkaindl
Copy link

bernhardkaindl commented Oct 15, 2024

FYI / For response: @tilakrayal

@sachinprasadhs or @tilakrayal and @haifeng-jin:

What does it take to get this approved PR merged?

As the submitter @jonas-eschle pointed out in July, this would be ready for merge (for 5 months now).

It blocks a stack of pull requests of the spack package manager project, starting with this PR: spack/spack#43688

@sachinprasadhs sachinprasadhs added the ready to pull Ready to be merged into the codebase label Oct 15, 2024
copybara-service bot pushed a commit that referenced this pull request Oct 15, 2024
Imported from GitHub PR #779

As discussed in #776

I tried but actually run into the issue that layers/experimental cannot be used as a build target, as the builds _inside_ experimental _require_ layers -> circular deps. The other folders in `layers` circumvent this by specifying only the specific build targets.

Instead of changing the logic (i.e. is experimental meant to be dev-built only?), I did what the error advertised and added it to the ignored builds, as it's seemingly not made to be built
Copybara import of the project:

--
9d3bb64 by Jonas Eschle <[email protected]>:

docs: update CONTRIBUTING.md with new name tf-keras

(cherry picked from commit fb79960)

--
7bd7b3d by Jonas Eschle <[email protected]>:

fix: python build ignore experimental due to circular refs

(cherry picked from commit 9b349e3)

Merging this change closes #779

FUTURE_COPYBARA_INTEGRATE_REVIEW=#779 from jonas-eschle:fix_pip_build 7bd7b3d
PiperOrigin-RevId: 685927076
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready to pull Ready to be merged into the codebase size:S
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants