On 03/03/2023 06:00, Andreas Tille wrote:
Ahh, so aesara is not really a "fork" but a "rename"?
The original is abandoned (no new development since 2017, and now mostly
unmaintained, which is probably why it has this kind of bug). Aesara is
a continuation by a new upstream (possibly one
Hi Rebecca,
Am Thu, Mar 02, 2023 at 09:00:14PM + schrieb Rebecca N. Palmer:
>
> 1.1.2 isn't the latest version, just the latest that calls the module theano
> rather than aesara. (I chose it to package because I didn't want to fully
> break compatibility, then abandoned it because I didn't
On 02/03/2023 10:38, Andreas Tille wrote:
I admit I do not see any good reason to stick to the old version if we
decided before that keras/deepnano are no real blockers to even drop
theano. Thus I was considering it more promising to spent my time on
the latest version.
1.1.2 isn't the latest
Hi Rebecca,
Am Wed, Mar 01, 2023 at 10:41:23PM + schrieb Rebecca N. Palmer:
> I agree that switching to Aesara is probably the only reasonable option
> other than removal. (I'd given up on trying to fix 1.0, and was intending
> to let removal happen.)
>
> However, it's a much bigger change
I agree that switching to Aesara is probably the only reasonable option
other than removal. (I'd given up on trying to fix 1.0, and was
intending to let removal happen.)
However, it's a much bigger change than is normally allowed in bookworm
at this point. (1.1 includes multiple breaking
Control: tags -1 pending
Hi,
> Andrius Merkys wrote:
> That said, it is OK to omit keras in bookworm if need be, but I would
> like to see it back for trixie.
I've spent some time into theano and it builds and runs its test suite
in Salsa CI[1]. Since despite some tests are failing in my
Hi Thiago,
Am Mon, Jan 16, 2023 at 11:08:35AM -0300 schrieb Thiago Franco Moraes:
> Done! I removed both python3-theano and python3-keras.
Thanks for the quick response. Autopkgtest currently fails due to
Bug #1027851 pytorch FTBFS with Python 3.11 as default version
I think, I'll wait a
Hi Andreas,
Done! I removed both python3-theano and python3-keras.
Best regards.
Em seg., 16 de jan. de 2023 às 09:54, Andreas Tille
escreveu:
> Hi Thiago,
>
> Am Sat, Jan 14, 2023 at 07:50:27PM -0300 schrieb Thiago Franco Moraes:
> > Hi Rebecca,
> >
> > InVesalius can work without Theano
Hi Thiago,
Am Sat, Jan 14, 2023 at 07:50:27PM -0300 schrieb Thiago Franco Moraes:
> Hi Rebecca,
>
> InVesalius can work without Theano (and Keras). It will use Pytorch.
Would you mind updating the packaging without Theano? Currently its in
its Build-Depends. Would it be sufficient to drop
Hello,
On 2023-01-14 13:12, Rebecca N. Palmer wrote:
theano has been mostly abandoned upstream since 2018. (The Aesara fork
is not abandoned, but includes interface changes including the import
name, so would break reverse dependencies not specifically altered for it.)
Its reverse
Hi Rebecca,
InVesalius can work without Theano (and Keras). It will use Pytorch.
Best regards.
Em sáb., 14 de jan. de 2023 às 08:12, Rebecca N. Palmer <
rebecca_pal...@zoho.com> escreveu:
> theano has been mostly abandoned upstream since 2018. (The Aesara fork
> is not abandoned, but includes
Currently, I'd say PyTorch and TensorFlow are the two most
popular libraries. And I even worry google is trying to
write something new like Jax to replace TensorFlow in some aspects.
On Sat, 2023-01-14 at 11:12 +, Rebecca N. Palmer wrote:
> theano has been mostly abandoned upstream since
On Sat, Jan 14, 2023 at 11:12:07AM +, Rebecca N. Palmer wrote:
> theano has been mostly abandoned upstream since 2018. (The Aesara fork is
> not abandoned, but includes interface changes including the import name, so
> would break reverse dependencies not specifically altered for it.)
>
>
theano has been mostly abandoned upstream since 2018. (The Aesara fork
is not abandoned, but includes interface changes including the import
name, so would break reverse dependencies not specifically altered for it.)
Its reverse dependencies are keras, deepnano and invesalius.
It is
14 matches
Mail list logo
