Conversation
Zouxxyy
force-pushed
the
xinyu/dev-pypaimon
branch
from
September 27, 2026 16:43
acab245 to
96560cc
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose
Centralize PyPaimon's core, optional, development, and build dependencies in
pyproject.toml, removing the two requirements files and duplicate CI dependency lists. Development groups reuse the public extras.Use
python -m buildand generate the source distribution and wheel with the same date-stamped development version. Preserve commit provenance across source-distribution rebuilds and retain Python 3.6 compatibility. Update release workflows, installation docs, and lint exclusions for generated files.Remove the obsolete
packaging<26cap so current Twine and PyPaimon can coexist in the same environment.Tests
pip check.git diff --checkpassed.Full CI and mixed Java/Python E2E will run on GitHub.