I'm the lead developer/manager of the Aesara project and a core developer in the PyMC group.
Theano has officially stopped development <https://groups.google.com/g/theano-users/c/7Poq8BZutbY/m/rNCIfvAEAwAJ> and currently exists in an effectively frozen state. As stated in Theano's README <https://github.com/Theano/Theano/blob/8e9611715b33672d4b65b3fe232988c4adac970a/README.rst#L4>, its successor is our fork, Aesara <https://github.com/pymc-devs/aesara>. If there are users who still rely on legacy Theano and SymPy's Theano features, then it would make sense to maintain the existing Theano code. I'm not personally aware of any projects that do, so I can't say, but I *do* know that Aesara has considerably more potential for developing SymPy interactions (e.g. see some preliminary symbolic work here <https://github.com/pymc-devs/symbolic-pymc>) in the nearterm. On Monday, March 15, 2021 at 3:53:02 PM UTC-5 [email protected] wrote: > I would also like more context on what the status of Theano and Aesara > is. The pull request as it is breaks compatibility by renaming the > function and making it no longer work with theano. I think it would be > better to add a new function, aesara_code, and keep the old > theano_code() intact. I'm not clear if it should also be deprecated. > Theano is currently installed in the tests, meaning it presumably > still works. Do we know at what point it will stop working? > > Perhaps someone can forward this thread to one of the Aesara > developers so they can comment here. > > Aaron Meurer > > On Mon, Mar 15, 2021 at 2:16 PM Oscar Benjamin > <[email protected]> wrote: > > > > Hi all, > > > > Does anyone use SymPy with Theano? > > > > There is a PR which proposes to drop Theano support in favour of Aesara: > > https://github.com/sympy/sympy/pull/21087 > > > > The PR looks fine to me but I don't actually know what Theano/Aesara > > are. Apparently Theano is no longer actively maintained and Aesara is > > a fork that should be considered a natural successor. > > > > If anyone has any thoughts on this then please say so (here or on the > > PR). Otherwise I'm inclined to merge the PR because the author clearly > > knows more than I do about this and says that this is a reasonable > > approach. > > > > Oscar > > > > -- > > You received this message because you are subscribed to the Google > Groups "sympy" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/CAHVvXxTCV3U2YxE5%3D3-us5RbtkfF8ZaqmvKA-8oM9QkPdXJUxg%40mail.gmail.com > . > -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/d079659c-e249-4d22-a231-8caa2a101716n%40googlegroups.com.
