@kral: .@LakshyAAAgrawal what would this imply for GEPA ?
Summary
DSPy 3.4 release candidate is announced, moving off litellm to improve import speed and reduce dependencies.
View Cached Full Text
Cached at: 09/13/26, 11:19 PM
.@LakshyAAAgrawal what would this imply for GEPA ?
Maxime Rivest 🧙♂️🦙🐧 (@MaximeRivest): DSPy 3.4 release candidate it out, we are moving off litellm.
It always bothered me how slow dspy was to import and how many deps it had because of litellm.
No longer the case!
Similar Articles
@MaximeRivest: DSPy 3.4 release candidate it out, we are moving off litellm. It always bothered me how slow dspy was to import and how…
The DSPy 3.4 release candidate is announced, moving away from litellm to improve import speed and reduce dependencies. Community members like Drew Breunig have praised the improvements.
@lateinteraction: man, we’re so extremely lucky to have @isaacbmiller1 as lead maintainer! also wow it took me longer than i’d like to ad…
DSPy 3.3.0 is released, featuring dspy.Flex for GEPA-optimized code and prompts, and dspy.ReActV2 with native parallel tool calling, with praise for lead maintainer Isaac Miller.
@isaacbmiller1: DSPy 3.2.0 is out! Here are a few highlights: - dspy.RLM improvements around parsing, tool execution, and failure recov…
DSPy 3.2.0 improves dspy.RLM parsing, tool execution, and failure recovery, plus ongoing work to decouple from LiteLLM.
@dbreunig: It’s a @DSPyOSS patch release, but it’s packed! CodeInterpreter fixes & features, MCP 2.0 support, GEPA bump, better er…
A patch release for DSPy includes CodeInterpreter fixes, MCP 2.0 support, GEPA bump, and improvements to errors and callbacks.
@harold_matmul: dspy.GEPA used in pretraining data curation in the new Microsoft AI effort :-)
The article explains how GEPA (Genetic-Pareto Optimization) within DSPy is used for efficient prompt tuning, specifically applied to pretraining data curation at Microsoft AI, allowing researchers to replace manual prompt engineering with automated compute-driven optimization.