[INLONG-12016][SDK] Add Python Dataproxy SDK compile Dockerfile #12018
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
doleyzi
previously approved these changes
Oct 17, 2025
luchunliang
previously approved these changes
Oct 17, 2025
yfsn666
force-pushed
the
INLONG-12016
branch
from
6781a50 to
9e55d5c
Compare
yfsn666
force-pushed
the
INLONG-12016
branch
from
9e55d5c to
cfe1413
Compare
luchunliang
approved these changes
Dec 15, 2025
doleyzi
approved these changes
Dec 15, 2025
dockerzhang
approved these changes
Dec 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #12016
Motivation
Provides a Python Dataproxy SDK compile Dockerfile to help users quickly build the Python SDK.
Modifications
Add a directory
dockerindataproxy-sdk-pythonwhich contains Dockerfile and related files. And optimize the relevant build files.Verifying this change
(Please pick either of the following options)
This change is a trivial rework/code cleanup without any test coverage.
This change is already covered by existing tests, such as:
(please describe tests)
This change added tests and can be verified as follows:
(example:)
Documentation