Andreas Klöckner authored Nov 07, 2024 and Andreas Klöckner committed Nov 07, 2024

(for now, matches existing behavior, but is clearly incorrect)

Andreas Klöckner authored Nov 06, 2024 and Andreas Klöckner committed Nov 06, 2024

This restores compatibility with pymbolic 2022.2

x-ref: https://github.com/firedrakeproject/loopy/issues/27

Nick Koskelo authored Oct 11, 2024 and Andreas Klöckner committed Oct 11, 2024

Documentation defined the unpack argument twice. Now it only defines it once and also defines the pack argument.

* Require that happens_after is not mutable

* Tweak type tests for happens_after

---------

Co-authored-by: Andreas Kloeckner <inform@tiker.net>

Andreas Klöckner authored Feb 16, 2024 and Andreas Klöckner committed Aug 25, 2024

On Python 3.12, this provokes a stack overflow in the scheduler. It is
not quite clear why that's the case; pure-Python recursion even with
generators seems to respond well to setrecursionlimit():

```py
def f(n):
    if n:
        yield from f(n-1)
    else:
        yield 5

import sys
sys.setrecursionlimit(3500)
print(list(f(3400)))
```

That said, there have been [behavior](https://github.com/python/cpython/pull/96510)
[changes](https://github.com/python/cpython/issues/112215)
in Py3.12 in this regard, but it is not clear what exactly
about Loopy's behavior makes it fall into the 'bad' case.

Kaushik Kulkarni authored Aug 24, 2024 and Andreas Klöckner committed Aug 24, 2024

This is a typed version of the code from this commit:
https://github.com/inducer/loopy/pull/690/commits/be5a31849c8ea16670a416c83b7b86a0cc5f71ae



Co-authored-by: Andreas Kloeckner <inform@tiker.net>