Skip to content

Hi, sbrunk please review my code add many feature - #88

Open
mullerhai wants to merge 118 commits into
mainfrom
main
Open

Hi, sbrunk please review my code add many feature#88
mullerhai wants to merge 118 commits into
mainfrom
main

Conversation

@mullerhai

Copy link
Copy Markdown

HI Sbrunk:

    Now  STorch I have extend many feature , it gain so many line code, I cannot say the detail. 

DESKTOP-I12M6AR\jeffsyry and others added 30 commits April 3, 2025 12:37
…t find by and partner object apply and distribute programgroup ,rename core module with storch_core and vision module with storch_vision, and example module with storch_examples for maven release ,and release version 0.2.9-1.15.1
@sbrunk

sbrunk commented Oct 20, 2025

Copy link
Copy Markdown
Collaborator

This is so amazing @mullerhai!

@sbrunk

sbrunk commented Oct 20, 2025

Copy link
Copy Markdown
Collaborator

Let's get CI running again so we can run the tests there. I think we need to update the workflows a bit as the actions are outdated.

@sbrunk

sbrunk commented Oct 28, 2025

Copy link
Copy Markdown
Collaborator

I've started going through the PR. A few initial remarks:

  • storch-core has a lot of dependencies right now like storch-pandas. Ideally I'd like to keep it very small instead and let the other modules depend on storch-core if possible or create integration modules.
    • Related, do we want to keep the storch-* modules all in separate repositories or does it make sense to move some of them into this repo as submodules?
  • The current Scala version is 3.6.3, while LTS, which is recommended for libraries is currently 3.3.7. Can we use the LTS version to improve compatibility?

@mullerhai

Copy link
Copy Markdown
Author

I've started going through the PR. A few initial remarks:

  • storch-core has a lot of dependencies right now like storch-pandas. Ideally I'd like to keep it very small instead and let the other modules depend on storch-core if possible or create integration modules.

    • Related, do we want to keep the storch-* modules all in separate repositories or does it make sense to move some of them into this repo as submodules?
  • The current Scala version is 3.6.3, while LTS, which is recommended for libraries is currently 3.3.7. Can we use the LTS version to improve compatibility?

Hi @sbrunk , I have remove storch-pandas storch-safe-tensors storch-sklearn ,
the scala3 version I think because we need use jupyter notebook, the almond.sh scala kernel is support scala3.6.3 ,it could work normally . if use scala3 3.3.7 I don't know the compatiable with jupyter notebook , it just could make decision by youself , I am not care of the scala version . just could work is ok

@sbrunk

sbrunk commented Nov 2, 2025

Copy link
Copy Markdown
Collaborator

Hi @sbrunk , I have remove storch-pandas storch-safe-tensors storch-sklearn , the scala3 version I think because we need use jupyter notebook, the almond.sh scala kernel is support scala3.6.3 ,it could work normally . if use scala3 3.3.7 I don't know the compatiable with jupyter notebook , it just could make decision by youself , I am not care of the scala version . just could work is ok

almond should work fine with Scala 3.3 LTS, but we also need to make sure that the libraries storch depends on are also compatible.

When storch and its dependencies are compiled with Scala 3.3 LTS, then other libraries using Scala 3.3/3.4,3.5,3.6,3.7 can use it but when it's compiled with 3.7, all libraries that depend on it need also be compiled to 3.7.

I created bytedeco/storch-numpy#2 to move storch-numpy to 3.3, could you look at the PR?

@mullerhai

Copy link
Copy Markdown
Author

HI @sbrunk , I have some idea ,to make more people quickly search storch and try to use storch. we need renamed storch as PyTorch too, how do you think?

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.

2 participants