Skip to content

Add Python 3.10, 3.11, 3.12 compatibility#4041

Closed
mhabedank wants to merge 70 commits into
ludwig-ai:masterfrom
mhabedank:hatch_dev_mh
Closed

Add Python 3.10, 3.11, 3.12 compatibility#4041
mhabedank wants to merge 70 commits into
ludwig-ai:masterfrom
mhabedank:hatch_dev_mh

Conversation

@mhabedank

@mhabedank mhabedank commented Nov 17, 2024

Copy link
Copy Markdown
Collaborator

This PR tries to solve the dependency problems we have when going forward to modern Python version.

Things currently done:

  • moved from outdated build system and requirements files to hatch and pyproject.toml
  • removed torchtext, rewrote lots of tokenizer code.
  • removed importlib
  • bumped numpy, torch, scikit-learn and several other dependencies.

@github-actions

github-actions Bot commented Nov 17, 2024

Copy link
Copy Markdown

Unit Test Results

0 tests   0 ✔️  0s ⏱️
0 suites  0 💤
0 files    0

Results for commit 063fe3b.

♻️ This comment has been updated with latest results.

@mhabedank mhabedank changed the title Hatch dev mh Add Python 3.10, 3.11, 3.12 compatibility Nov 20, 2024
@thc1006

thc1006 commented Nov 1, 2025

Copy link
Copy Markdown

Dear @mhabedank and @ethanreidel,

First of all, thank you both for the excellent work on PR #4041! I've carefully studied your technical approach, and I'm impressed by how well-designed the tokenizer refactoring is.

I've recently tested these tokenizer changes in my environment and found they work beautifully. I was wondering if I could contribute some test validation results to help move this PR forward.

I'd be happy to assist in whatever way works best for you:

Option A: If it's convenient, you could add me as a collaborator

  • This way I can directly push test-related improvements
  • All work would stay within this PR
  • You would, of course, remain the primary authors—I'd just be assisting with testing and validation

Option B: I can submit PRs to your branch

  • You could review and decide what to merge
  • This would be more structured, though it might add some review overhead

Here's what I've already completed:

  • ✅ Tested all 5 tokenizers in Docker (Python 3.10)
  • ✅ Verified backward compatibility
  • ✅ Created test results documentation (TEST_RESULTS.md)
  • ✅ All tests passing (5/5)

I noticed the CI shows "0 tests executed"—I'm not sure if it's a configuration issue, but if needed, I'd be happy to help with test-related setup as well.

My intention is purely to help this PR move forward—I have absolutely no desire to take credit or compete. If you don't need additional help or have other considerations, I completely understand and respect that.

Thank you again for your hard work! I look forward to potentially collaborating.

Best regards,

@thc1006 thc1006 mentioned this pull request Nov 1, 2025
@w4nderlust

Copy link
Copy Markdown
Collaborator

Thanks for the significant effort here @mhabedank! Adding Python 3.10–3.12 compatibility was much needed.

This has been fully addressed in #4059, which modernizes the entire codebase to Python 3.12 and upgrades all major dependencies:

  • PyTorch 1.x → 2.6
  • Ray 2.3 → 2.54
  • transformers 4.x → 5.x
  • NumPy 1.x → 2.x
  • Dask 2023.x → 2026.1.2
  • Plus removal of torchtext, Horovod, Neuropod, and GBM/LightGBM

All 4,564 tests pass in CI. Closing as superseded by #4059.

@w4nderlust w4nderlust closed this Feb 27, 2026
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.

5 participants