Skip to content

Conversation

@k-dominik
Copy link
Collaborator

@k-dominik k-dominik commented Jul 14, 2025

In order to unlock numpy 2.0 in ilastik, tiktorch is one of the blockers.

In order to allow for newer pytorch versions, also grpcio needed to be updated (blocked via libabseil).

@codecov
Copy link

codecov bot commented Jul 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 62.48%. Comparing base (61d70a8) to head (38fc4b0).
Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #236      +/-   ##
==========================================
+ Coverage   62.40%   62.48%   +0.08%     
==========================================
  Files          47       47              
  Lines        2878     2887       +9     
==========================================
+ Hits         1796     1804       +8     
- Misses       1082     1083       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

switch to conda-forge only (pytorch channel is deprecated, pytorch
packages available on conda-forge for all platforms)

numpy 2
pytorch 2.7
remove cpuonly (not necessary anymore with conda-forge builds)
go to python 311 (current ilastik version)
@k-dominik k-dominik merged commit dbeaac4 into main Jul 14, 2025
8 checks passed
@k-dominik k-dominik deleted the upd-npy branch July 14, 2025 14:25
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