Oscar Gustafsson

Thanks @mrclary for the exhaustive investigation! I can clearly see @ccordoba12's worry about users having files with standard names in the path. It may lead to an increased number of...

> If you mean the base `sys.path` to remain as a contiguous block Yes, that is what I meant. Although the alternative may be "nice", I cannot really see any...

I'd say that it is systematic in the sense that it always behave like this, but to actually trigger it require some specific searches. However, searching for `class` in the...

I had a go of extracting some highlights and summarize the deprecations and removals (with the idea that one can find the details in the long list). Feel free to...

This should probably be fixed in the SymPy-printer (and all printers...) similar to https://github.com/sympy/sympy/pull/20806

Probably the best place is to change here: https://github.com/sympy/sympy/blob/68c37df362e8585d72fc7ef490013bb8eff16e3e/sympy/printing/codeprinter.py#L397-L408 In that way, all code printers would benefit from it (under the assumption that {} cannot be part of a variable...

This also means that at least the `_print_Symbol` method added in https://github.com/sympy/sympy/pull/20806 can be removed (actually that method is exactly what the above should be replaced with). Possibly this holds...

Sort of. However, there is a PR solving it that is not yet merged. So if you want to work on something there are probably better issues.

This would need to be updated to being deprecated in 1.12 (as 1.11 is just released, sort of). Also, "the aforementioned issue" will not make sense when you see it...

This needs more thinking. Currently: ``` n = Symbol('n', integer=True) (Eq(n, 2) | (n>= 3)).simplify() ``` gives ``` (Eq(n, 2) | Eq(n, 3) | (n>= 4)) ``` Which breaks a...