Closed kaushikcfd closed 1 year ago
What's your take on the CI failures?
Was just fixing those! :)
@inducer: This is ready.
(TIL the ast
package is awfully unstable across versions.)
Thanks! Could you say a bit about the motivation for this, and why it's worth it to deal with the instability of ast
?
Thanks! Could you say a bit about the motivation for this, and why it's worth it to deal with the instability of last?
In PyOP2, we need to cache a part of the Loopy's "host code" on the disk (to be able to compute the computational grid sizes). The other option was to use genpy
for it. But I've generally felt that ast
is more complete and comes with extra batteries to process these trees.
The discussion in https://github.com/OP2/PyOP2/pull/574#discussion_r918938833 has echos of https://github.com/inducer/loopy/pull/650 to me, in the sense that it's indicative of a potentially missing "invoker" level, where these (presumably) grid sizes likely should reside. Could you explain a bit more how they're used?
(Commented there instead of here, since that discussion has very little to do with this PR.)
Thx!
What's your take on the CI failures?