| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Kalvin Eng <kalvin(dot)eng(at)ualberta(dot)ca>, pgsql-www(at)lists(dot)postgresql(dot)org |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Subject: | Re: Upgrading to newer Django? Reason for including django-selectable library in repo? |
| Date: | 2020-03-03 22:10:18 |
| Message-ID: | 98c0c5b8-6ac7-1df0-f71b-507e79a27174@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Hi Kalvin,
On 3/3/20 12:57 PM, Kalvin Eng wrote:
> Hi there,
>
> I'm new to the community and looking to send a GSoC proposal for the
> performance farm project
> (https://wiki.postgresql.org/wiki/GSoC_2020#Develop_Performance_Farm_Benchmarks_and_Website_.282020.29).
Cool :)
> One of the requirements was integrating the performance farm app with
> pgweb to include already registered users.
> So I had a look at the code for pgweb to understand the login flow for
> integration.
>
> Upon looking at the code for pgweb, I'm wondering if these things should
> be patched:
>
> * Upgrading to Django 2.2 LTS since Django 1.11 will no longer be
> supported in April 2020
Seems like a good idea. IIRC Magnus did some testing way back on 2.0
(unless I'm imagining)
> * Remove django-selectable from the repo as it is available in pypi
> (https://pypi.org/project/django-selectable/)
>
>
> Thanks,
> Kalvin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2020-03-03 22:16:09 | Re: Upgrading to newer Django? Reason for including django-selectable library in repo? |
| Previous Message | David Steele | 2020-03-03 18:10:26 | PG14 target version? |