Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kuuef-000577-3k for pgadmin-hackers@arkaria.postgresql.org; Thu, 31 Dec 2020 09:54:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kuue6-0006Jp-52 for pgadmin-hackers@arkaria.postgresql.org; Thu, 31 Dec 2020 09:53:26 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kuue5-0006Ji-TF for pgadmin-hackers@lists.postgresql.org; Thu, 31 Dec 2020 09:53:26 +0000 Received: from mail-lf1-x12d.google.com ([2a00:1450:4864:20::12d]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kuue1-0000BE-Vd for pgadmin-hackers@postgresql.org; Thu, 31 Dec 2020 09:53:25 +0000 Received: by mail-lf1-x12d.google.com with SMTP id h22so43153649lfu.2 for ; Thu, 31 Dec 2020 01:53:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2aCYyDUMYRhQAZZKP/XN3eD89hxA7jzxa+h201YKzks=; b=D2R412XfNf5ttelZwiQntOruD0NnFRy1wDxRHgC2pZn6LeS9nousNUIdng05+7XTNW R/5i2dHGZ+ZnSqHFTYJbMPYRzmFSd6nq4lcGXN+1SbQLLjPqeCinb4qvu57s+hJ4IMT6 o8K+keDyHbNm8tDiAQTi4JARRBd0HntYmBei8bsEwvq9GwO1qGfeXsIelufrMyLXI4N7 efieyj3+/hXFBsytmoBXHB0s7+zsZPYr7pvjDKTzWb90fouX5IaP6msS3YcxEoKqNfYk htRS0kA75KCjFbr8IRvP44XrIsSLSnRZjKQWd/U/x4GXWbyVM2sBv8Gt3p/7uNhxK0yD /CzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2aCYyDUMYRhQAZZKP/XN3eD89hxA7jzxa+h201YKzks=; b=a09i0ofnPTZf1tBQc2n3aZE7pPCLCvglTHqoiQQl7FpzAD69Now66gtvaiZvSMgGA/ Xk9wwnHyt7XoDC0dAJSN5Qrb8S2Bc84141rhfEiSDPc0g1BJEFwmAfE8W4VQkcyJql6w SnTNCb03x1JMs+LIiLNPp6MLBWXd1iR3+OAOIUIF9iXxV6u/1ulM7SLe1iszXFzshyQv M/iT76KP4kuYXDhksNUf8nyqlGpSnWPUwnb3W+LSo/AKf49WTT/wv02qjeD42bkByYEV ScKAjL188PIbzBfUJLAhre0b7zPnB8tchojujG+/cDgiMyIKGeUhDn7u5W1fJAuwmQj7 Scww== X-Gm-Message-State: AOAM530lOPlqIX1q/EtWzBjhDUl+pmAL8wRl3Wjdv9ZX6U5FjAuLhgWr ahAN1BOd5VhiAOqs+T55g5yGd082acOuKKZEGFw7g7YVKcLfekeEKTU9ElArPEwEMCFEbGcXquB qnxgJOcWMq3yDF+rgUgbpkZD4UOKD1S26ujbReX0llaBlKefzA1XVpKVo7coqMaU7f0zWZjYwlP MHSXyCoiBcvWA7nfCkLbezV6LX7hWyAsE1HyD+yH1KC4fTouXaYLy1zKLXVw== X-Google-Smtp-Source: ABdhPJy+9Q2bhiufizwAgYLwoYI8vxxwuW1mBXokZxA94jlZOmTxBw7Vc/c/skUIPYguVQs3Cd8xeJlhq/IMTRXWVd8= X-Received: by 2002:ac2:47fb:: with SMTP id b27mr23673106lfp.548.1609408400725; Thu, 31 Dec 2020 01:53:20 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Khushboo Vashi Date: Thu, 31 Dec 2020 15:23:18 +0530 Message-ID: Subject: Re: [pgAdmin][RM-6088]: Migrate pgadmin4 from Flask-BabelEx to Flask-Babel >= 2.0 To: Nikhil Mohite Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000062f4505b7bf9806" X-CLOUD-SEC-AV-Info: enterprisedb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000062f4505b7bf9806 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Dec 30, 2020 at 12:29 PM Nikhil Mohite < nikhil.mohite@enterprisedb.com> wrote: > Hi Team, > > I found one issue related to Flask-Babel migration. > > Flask-Babel and Flask-BabelEx are causing the issue if we install them in > the same environment. > Flask-BabelEx gets installed as a dependency of Flask-Security-Too librar= y > and currently, Flask-Security-Too doesn=E2=80=99t support Flask-Babel, bu= t the > latest version (4.0 Not yet released) of Flask-Security-Too will shift to > Flask-Babel. > ref: https://github.com/Flask-Middleware/flask-security/issues/353 > > So I think we should hold Flask-Babel migration for now. but we can updat= e > the FLask-BabelEx to the latest version as there is one issue related to = it > this https://redmine.postgresql.org/issues/5997 > we can fix it first by > adding the Flask-BabelEx minimum version in our requirements. > > > +1 > > Regards, > Nikhil Mohite. > > On Tue, Dec 29, 2020 at 4:36 PM Nikhil Mohite < > nikhil.mohite@enterprisedb.com> wrote: > >> Hi Team, >> >> Please find the attached patch for RM-6088 >> : Migrate pgadmin4 from >> Flask-BabelEx to Flask-Babel >=3D 2.0. >> >> >> -- >> *Thanks & Regards,* >> *Nikhil Mohite* >> *Software Engineer.* >> *EDB Postgres* >> *Mob.No: +91-7798364578.* >> > --000000000000062f4505b7bf9806 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, Dec 30, 2020 at 12:29 PM Nikh= il Mohite <nikhil.mohi= te@enterprisedb.com> wrote:
Hi Team,

I found one issue = related to Flask-Babel migration.

Flask-Babel and = Flask-BabelEx are causing=C2=A0the issue if we install them in the same env= ironment.
Flask-BabelEx gets installed as a dependency of Flask-S= ecurity-Too library and currently, Flask-Security-Too doesn=E2=80=99t suppo= rt Flask-Babel, but the latest version (4.0 Not yet released) of Flask-Secu= rity-Too will shift to Flask-Babel.
<= br>
So I think we should hold Flask-Babel migration for now. but = we can update the=C2=A0FLask-BabelEx to the latest version as there is one = issue related to it this=C2=A0https://redmine.postgresql.org/issues/5997=C2= =A0=C2=A0we can fix it first by adding the Flask-BabelEx minimum versio= n in our requirements.


+1=C2=A0

Regards,
Nikhil Mohit= e.

On Tue, Dec 29, 2020 at 4:36 PM Nikhil Mohite <nikhil.mohite@enterprise= db.com> wrote:
Hi Team,

Please find the attached= patch for RM-6088:=C2=A0Migrate pgadmin4 from Flask-BabelEx to Flask-Bab= el >=3D 2.0.


--
Thanks & Regards,
Nikhil Mohite
Software Engineer.
Mob.No: +91-7798364578.
--000000000000062f4505b7bf9806--