sympy 1.6.1 ?

[FabioLuporini]

Hi, is there any plan on releasing 1.6.1, just like we had 1.5.1 shortly after 1.5? We're unfortunately stuck with 1.5.1, but the patches we've submitted have already been merged into SymPy master, and we're looking forward to jump to 1.6. Thanks!

[oscarbenjamin]

Which patches are you referring to?

[FabioLuporini]

Strictly speaking, the only one we actually need is #19431 . #19533 is the other one (though this one is more of a "I'd really like to have it, but I can survive without for the time being)

the bug fixed in #19431 really kills our code

[FabioLuporini]

Note: edited my previous reply (wrong PR numbers before, now it should be fine)

[oscarbenjamin]

The normal plan is we would only make a bugfix release (i.e. 1.6.1) if regressions were identified in 1.6 (relative to 1.5.1). Also 1.6.1 would be based off the 1.6 branch rather than master so any fixes need to be cherry-picked to that branch. It's important to say when opening an issue that represents a regression that it is a regression so that any fix could be included in a bugfix release.

Until now the only regression I knew of was #19532.

[FabioLuporini]

#19431 was a regression AFAICT? apologies if it wasn't made clear in the PR description. Looping in @mloubout (who wrote the actual patch)

[mloubout]

Yes this was a regression, I apologize if I haven't tagged it correctly, I tried to follow the guidelines but was the first time I PRed into sympy so I may have missed some parts.
As @FabioLuporini this is somethign that forces us to be fixed at 1.5.1 as this is an issue that make 1.6 unusable for us due to the presence of the Dummy object after collection.

[oscarbenjamin]

No need to apologise. It's just best to explicitly say if something is a regression and since what version.

We can do a 1.6.1 release but I think we need a fix for #19532 first.

[oscarbenjamin]

I've start preparing for the release (#19598). The issue tracking the release is #19599

[oscarbenjamin]

#19601 applies #19431 to the 1.6 branch for release in 1.6.1 and will close this issue.