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 1kuVSj-0007Dq-6C for pgadmin-hackers@arkaria.postgresql.org; Wed, 30 Dec 2020 07:00: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 1kuVSg-0008VF-Vs for pgadmin-hackers@arkaria.postgresql.org; Wed, 30 Dec 2020 06:59:58 +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 1kuVSg-0008V7-Q0 for pgadmin-hackers@lists.postgresql.org; Wed, 30 Dec 2020 06:59:58 +0000 Received: from mail-yb1-xb2c.google.com ([2607:f8b0:4864:20::b2c]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kuVSd-0007tt-UV for pgadmin-hackers@postgresql.org; Wed, 30 Dec 2020 06:59:58 +0000 Received: by mail-yb1-xb2c.google.com with SMTP id w127so14183169ybw.8 for ; Tue, 29 Dec 2020 22:59:55 -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; bh=PQW0pAfCI6r6IQzIwz10VVuSXyfT5KOaXFvbKYtCl24=; b=ZiFrwzxFNawsQPUBdLuAW0+j/LVuIxx1P5sBm4HCeyAPiu6JP/aXu12RvvRlhlIb6v /zaVGDhc0KJvvgLudAd8bS8MpfTNhm/54NhGlDKQyDFDTHFHrht+Inf8yDFO3crPxifC /JC1gMn8Qno+YXrZQrW0d7AVfKJBHjvoKqeYhJOh6rRJ+zSorWWT4njCirell6Uthqr/ CD0ALy6W7IXBBuFVEUQBq9iE9ZNThpbMKi+lhrTchJ40yb/lrNP3G0Hofel8S9G8aWIZ mw9yL8rznEKIrxzhNsWU5YCD5xhae3ARBEHJSClZ6X5g0yPFQBzKt7ez5RH4Ewa+l3i6 sqNA== 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; bh=PQW0pAfCI6r6IQzIwz10VVuSXyfT5KOaXFvbKYtCl24=; b=ZmImO6JsztZ7qoC3q8CwryOd3I39jNi2vAokvMiRY4tKSYLFmC0u/+61PMwLGPAuoa aqPTQTzcYQz+fOsBbGCj8krkOIcYhqR9VLD7Ri1sw+66GSDsVXFUOoLJwtGD5TFBfznd u6XuNh52yPwX8Lj3qOsHXO2EB8h2YNOi6KMbNXu4MAzOY/ojSeGG/FkMmMx5XKGFSW8A dSgHXcEzG/tbzHJfLLePlh9eZcohPLE01aX6xfBfpl0VgNInu+MhjjBKTUC9DR7rrQ0q gxOilmi/0Q6D4yheVlM4SHcvRhsm2/MQ27b3XtWlGwDda7tf5txlQV/dA1Gz3KOl/rO3 kIaw== X-Gm-Message-State: AOAM533R0lc3+QZN8rVb2bHg9+4hkMR5ZeWiZw8RBGEEQyKIUNmqD7a2 0B8sDE27ZAwoZgaZq1L3FnIz8D27J48NjvFVkzRYDNayPFrU48LLOdmhvhRZpMGAAXVe4z8sXJf sd2w9tW4cEhenMzukLOWlUbtr4CiHKxjAaE0X0NkkvCt0FxuhzsmCFlpJEyJHa1JEcrB4sheR03 x8te80Y48B2j/buvr0x7zoS5Ce29fsnf9XQ9LMy4xPUuTQvkLxEcMsVltaP0BFntd94H1yf2I= X-Google-Smtp-Source: ABdhPJw5boAYvit+lI58d/dqAZY9y5FFbsi0z9yQ7UJ034ueAUVY4Jc7XeM/sKdwGGroTWK1RAnMiAYui8kOrXGI7g4= X-Received: by 2002:a25:7682:: with SMTP id r124mr71694580ybc.416.1609311593827; Tue, 29 Dec 2020 22:59:53 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Nikhil Mohite Date: Wed, 30 Dec 2020 12:29:42 +0530 Message-ID: Subject: Re: [pgAdmin][RM-6088]: Migrate pgadmin4 from Flask-BabelEx to Flask-Babel >= 2.0 To: pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000e22d0905b7a90d6b" 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 --000000000000e22d0905b7a90d6b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 library and currently, Flask-Security-Too doesn=E2=80=99t support Flask-Babel, but = 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 update 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. 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.* > --000000000000e22d0905b7a90d6b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Team,

I found one issue related to Flask-Ba= bel migration.

Flask-Babel and Flask-BabelEx are c= ausing=C2=A0the issue if we install them in the same environment.
Flask-BabelEx gets installed as a dependency of Flask-Security-Too library= and currently, Flask-Security-Too doesn=E2=80=99t support Flask-Babel, but= the latest version (4.0 Not yet released) of Flask-Security-Too will shift= to Flask-Babel.

So I think we should ho= ld 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-Babe= lEx minimum version in our requirements.



Regards,
Nikhil Mohite.

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

<= /div>
Please find the attached patch for RM-6088:=C2=A0Migrate pgadmi= n4 from Flask-BabelEx to Flask-Babel >=3D 2.0.


--
Thanks & Regards,
Nikhil Mohite
Software Engineer.
Mob.N= o: +91-7798364578.
--000000000000e22d0905b7a90d6b--