Skip to content

#42 Simplify Import Paths by Exposing Core Classes at Package Root #43

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

Merged
merged 2 commits into from
Mar 20, 2025

Conversation

chenghuichen
Copy link
Contributor

@chenghuichen chenghuichen commented Feb 23, 2025

Purpose

Linked issue: close #42

Simplify import paths, to avoid exposing internal technical details and avoid unnecessary coupling between user code and the py4j implementation mechanism. That also means, we can have a flexibility for future refactoring - we can change the underlying implementation without breaking user code.

This change maintains backward compatibility while providing a better developer experience.

Tests

API and Format

Documentation

Better to update Doc too.

Copy link
Contributor

@yuzelin yuzelin left a comment

Choose a reason for hiding this comment

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

+1

@yuzelin yuzelin merged commit 08d0bb3 into apache:main Mar 20, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Enhancement] Simplify Import Paths by truncating py4j
2 participants