CVXPY 1.7
This release is consistent with our semantic versioning guarantee. It comes packed with many new features, bug fixes, and performance improvements.
This version of CVXPY supports Python 3.9 through 3.13. While working on the next release, we continue to officially support CVXPY 1.6.
New GPU solvers
CVXPY begins supporting GPU solvers in this release. The following solvers are supported:
MPAX runs on a GPU device specified by the JAX environment. MPAX, cuOpt, and CuClarabel are new solver interfaces that can be used with CVXPY. SCS has a new backend based on cuDSS that can be used through the existing SCS interface.
Sparse array support
SciPy is deprecating the sparse matrix API in favor of sparse arrays. See the migration guide here.
CVXPY 1.7 supports the new sparse array API but continues to support the sparse matrix API for backwards compatibility.
Update on reshape order
In CVXPY 1.6, we began raising warnings for the default reshape order being Fortran ('F'),
which differs from NumPy's default order ('C'). We also mentioned that we would raise an error
if the order was not specified in CVXPY 1.7, and switch the default order to 'C' in CVXPY 1.8.
However, we have decided to postpone these changes to CVXPY 2.0, the next major release.
We believe that raising errors could break existing code and cause confusion among users.
We encourage users to continue explicitly specifying the order when using reshape, vec, and flatten atoms.
New features
- Multiple attributes for variables and parameters
- New QOCO solver interface
- New atom:
broadcast_to - New atom:
transpose(expr, axes) - New atom:
swapaxes - New atom:
moveaxis - New atom:
permute_dims - Add warm-start support for HiGHS
- Add warm-start support for PIQP
Summary
This new release totaled 84 PRs from 27 users.
- @563925743 | #2683
- @akshayka | #2711
- @andresliszt | #2634
- @bstellato | #2769
- @dependabot[bot] | #2638, #2639, #2650, #2659, #2757, #2795, #2819, #2827, #2831, #2832, #2848
- @dschult | #2689, #2710
- @goulart-paul | #2697, #2737
- @govindchari | #2670, #2712, #2719, #2720, #2730, #2744, #2761, #2762, #2763
- @jonathanberthias | #2740
- @klobucar | #2648
- @kydonian | #2796
- @kylematoba | #2726
- @maxschaller | #2635, #2693, #2694, #2734
- @mbataillou | #2745
- @mlubin | #2636
- @napinoco | #2846
- @PTNobel | #2692, #2701, #2702, #2717, #2718, #2803, #2812, #2815, #2839, #2844
- @rileyjmurray | #2834, #2847
- @RSchwan | #2797
- @samuela | #2798
- @senhalil | #2691, #2785, #2810, #2838
- @smachen42 | #2695
- @SteveDiamond | #2647, #2705, #2765, #2778, #2792, #2824
- @tasseff | #2714
- @Transurgeon | #2361, #2637, #2654, #2658, #2667, #2690, #2724, #2756, #2760, #2768, #2772, #2784, #2805, #2817, #2829
- @tschm | #2676, #2678, #2680
- @ZedongPeng | #2802
Special shoutout to @PTNobel for leading the integration of GPU solver interfaces into CVXPY.