(sorry for the very late response, I only noticed your message just now)
I did come to the conclusion that Werkzeug 2.3.x has some bigger changes
that will break most of the existing packages in some way. The main
differences to Werkzeug 3.x than isn't that big.
Ok, that makes sense!
Hello Julian,
Am 04.01.24 um 10:23 schrieb Julian Gilbey:
...
The build of src:flask is depending on python3-werkzeug >= 3.x, which has
itself a dependency on python3-markupsafe, so if you spot a missing direct
dependency I'm interested how this comes to play as Markupsafe should be
around at
On Thu, Jan 04, 2024 at 08:28:53PM +, Julian Gilbey wrote:
> Hi all,
>
> A quick update
> [...]
>
> Updates:
> [...]
>
> (2) It appears that all of the autopkgtests triggered by
> python3-werkzeug 2.3.8 have passed (though most are no longer showing
> on tracker.d.o). The only package
Hi all,
A quick update
On Thu, Jan 04, 2024 at 12:13:19PM +0100, Thomas Goirand wrote:
> On 1/3/24 22:22, Julian Gilbey wrote:
> > On Fri, Dec 22, 2023 at 12:04:48AM +0100, Gregor Riepl wrote:
> > > Hi Carsten,
> > > [...]
> > >
> > > My point was that if, for whatever reason, werkzeug
On Thu, Jan 04, 2024 at 12:13:19PM +0100, Thomas Goirand wrote:
> On 1/3/24 22:22, Julian Gilbey wrote:
> > On Fri, Dec 22, 2023 at 12:04:48AM +0100, Gregor Riepl wrote:
> > > Hi Carsten,
> > > [...]
> > >
> > > My point was that if, for whatever reason, werkzeug 3.0.1 is not yet fit
> > > for
>
On 1/3/24 22:22, Julian Gilbey wrote:
On Fri, Dec 22, 2023 at 12:04:48AM +0100, Gregor Riepl wrote:
Hi Carsten,
[...]
My point was that if, for whatever reason, werkzeug 3.0.1 is not yet fit for
release, it should be enough to upgrade to 2.3.5 to address these unit test
failures.
[...]
That
On Thu, Jan 04, 2024 at 09:23:58AM +, Julian Gilbey wrote:
> Hello Carsten,
> [...]
> There are other packages that currently FTBFS because werkzeug 2.2.x
> is not compatible with Python 3.12 in some small ways. It would fix
> those FTBFS bugs now; 6 months is a long time to wait! I've
Hello Carsten,
On Thu, Jan 04, 2024 at 07:07:01AM +0100, Carsten Schoenert wrote:
> Hello Julian,
>
> Am 03.01.24 um 22:22 schrieb Julian Gilbey:
> > Just to throw in: these werkzeug failures are also causing a similar
> > FTBFS in debugpy; I've temporarily addressed it by skipping these unit
>
Hello Julian,
Am 03.01.24 um 22:22 schrieb Julian Gilbey:
Just to throw in: these werkzeug failures are also causing a similar
FTBFS in debugpy; I've temporarily addressed it by skipping these unit
tests, but that's not a great solution.
I just took a quick look at upgrading the
Hello Gregor,
Am 22.12.23 um 00:04 schrieb Gregor Riepl:
My point was that if, for whatever reason, werkzeug 3.0.1 is not yet fit
for release, it should be enough to upgrade to 2.3.5 to address these
unit test failures.
I did come to the conclusion that Werkzeug 2.3.x has some bigger changes
On Fri, Dec 22, 2023 at 12:04:48AM +0100, Gregor Riepl wrote:
> Hi Carsten,
> [...]
>
> My point was that if, for whatever reason, werkzeug 3.0.1 is not yet fit for
> release, it should be enough to upgrade to 2.3.5 to address these unit test
> failures.
> [...]
>
> That doesn't make any sense
Hi Carsten,
I can see that 3.0.1 is currently in experimental, but it would be enough to
upgrade to the latest 2.x to fix this issue.
this makes not really sense to me. Flask 3.0.0 and Werkzeug 3.0.0 was
released on 09-30-2023, so almost three months before. Putting energy
into Flask 2.3.5
Hello Gregor,
Am Thu, Dec 21, 2023 at 02:00:40PM +0100 schrieb Gregor Riepl:
> I don't see any other errors in the log except for the ast.Str deprecation
> warnings, and they all come from python-werkezug and not this package.
>
> Reassiging the bug.
> Upstream has already fixed this in in
I don't see any other errors in the log except for the ast.Str
deprecation warnings, and they all come from python-werkezug and not
this package.
Reassiging the bug.
Upstream has already fixed this in in 2.3.5, by the way:
https://github.com/pallets/werkzeug/issues/2704
I can see that 3.0.1
14 matches
Mail list logo
