Skip to content

Splitting off Jupyter yet again #1095

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 12 commits into from
Mar 16, 2025
Merged

Splitting off Jupyter yet again #1095

merged 12 commits into from
Mar 16, 2025

Conversation

Jolanrensen
Copy link
Collaborator

@Jolanrensen Jolanrensen commented Mar 13, 2025

Fixes #775

…t some codegen logic. Refactored codegen paths from org.jetbrains.dataframe -> org.jetbrains.kotlinx.dataframe
@Jolanrensen Jolanrensen marked this pull request as ready for review March 14, 2025 13:39
@@ -28,3 +25,6 @@ public data class CodeWithConverter(val declarations: Code, val converter: (Vari
else -> declarations + "\n" + converter(name)
}
}

public typealias Code = String
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is it an option to not have these in public api?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think they're part of our codegen api. CodeWithConverter is public too after all

@@ -26,7 +26,8 @@ repositories {
fun ExternalModuleDependency.excludeJaiCore() = exclude("javax.media", "jai_core")

dependencies {
api(project(":core"))
api(projects.core)
implementation(projects.dataframeJupyter)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why do we need geo to depend on impl jupyter?

Copy link
Collaborator Author

@Jolanrensen Jolanrensen Mar 14, 2025

Choose a reason for hiding this comment

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

It uses useSchema<>() in its jupyter integration

Copy link
Collaborator

Choose a reason for hiding this comment

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

If we expect to use geo Integration to work only when jupyter Integration is configured (which should be), dependency can be compileOnly here

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I'm not 100% sure, @AndreiKingsley ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Let's fix this after merging, so we can revert back to java 8 sooner

@Jolanrensen Jolanrensen merged commit 63be9a8 into master Mar 16, 2025
7 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.

Move Jupyter integration in new dataframe-jupyter module
2 participants