Re: Moving forward with more Python 2 removal, plus upgrading to markupsafe 2.0, jinja2 3.0, werkzeug 2.0 and flask 2.0

2021-09-20 Thread Thomas Goirand
On 9/18/21 3:02 PM, Thomas Goirand wrote: > Dear Python Team, Dear Piotr, > > As I was packaging Cloudkitty (that is: OpenStack rating of resources, > typically used in a public cloud) for the next Xena release, I went into > this chain of dependency: > > cloudkitty: needs flask 2.0 > Flask 2.0:

Re: Moving forward with more Python 2 removal, plus upgrading to markupsafe 2.0, jinja2 3.0, werkzeug 2.0 and flask 2.0

2021-09-18 Thread Mattia Rizzolo
On Sat, Sep 18, 2021 at 03:02:01PM +0200, Thomas Goirand wrote: > During the python BoF of the last Debconf, we decided to go ahead with > full removal of Python 2, so doing this looks like a move to the right > direction. Yes indeed. > Is it fine for everyone (including Piotr, who's the only

Moving forward with more Python 2 removal, plus upgrading to markupsafe 2.0, jinja2 3.0, werkzeug 2.0 and flask 2.0

2021-09-18 Thread Thomas Goirand
Dear Python Team, Dear Piotr, As I was packaging Cloudkitty (that is: OpenStack rating of resources, typically used in a public cloud) for the next Xena release, I went into this chain of dependency: cloudkitty: needs flask 2.0 Flask 2.0: needs werkeug 2.0, jinja2 3.0 jinja2: needs markupsafe