Skip to content

Upgrade Ludic from 0.5 to 1.0#1

Merged
paveldedik merged 3 commits intomainfrom
claude/ludic-1.0-migration-011CUt8dQ2JhPwf7sHMxPShj
Nov 7, 2025
Merged

Upgrade Ludic from 0.5 to 1.0#1
paveldedik merged 3 commits intomainfrom
claude/ludic-1.0-migration-011CUt8dQ2JhPwf7sHMxPShj

Conversation

@paveldedik
Copy link
Member

Update documentation to reflect Ludic 1.0 requirements:

  • Change Python version requirement from 3.12+ to 3.14+
  • Update all references from f-strings to t-strings
  • Update Python badge to show 3.14+
  • Update getting started guide to use Python 3.14

These changes align with Ludic 1.0's new requirements for Python 3.14+ and its adoption of t-strings (new Python 3.14 feature).

claude and others added 3 commits November 7, 2025 07:31
Update documentation to reflect Ludic 1.0 requirements:
- Change Python version requirement from 3.12+ to 3.14+
- Update all references from f-strings to t-strings
- Update Python badge to show 3.14+
- Update getting started guide to use Python 3.14

These changes align with Ludic 1.0's new requirements for Python 3.14+
and its adoption of t-strings (new Python 3.14 feature).
Add informational notes to documentation about Ludic 0.5.x:
- Clarify that Ludic 0.5.x supports Python 3.12+ with f-strings
- Help users understand version differences between 0.5.x and 1.0
- Provide guidance for users on older Python versions

This helps users make informed decisions about which version to use
based on their Python version and whether they want to use t-strings.
@paveldedik paveldedik merged commit 97bf706 into main Nov 7, 2025
2 checks passed
@paveldedik paveldedik deleted the claude/ludic-1.0-migration-011CUt8dQ2JhPwf7sHMxPShj branch November 7, 2025 08:04
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