Jasper Lievisse Adriaanse - Mon, 20 April 2020 at 09:18:23 > Hi, > > Without a maintainer it seems our django ports were lagging behind a bit. > Here's > an update to the latest versions of the branches we were tracking. > Both of them contain a number of security fixes. > > As the 1.11 LTS branch has gone out of support per April 1 this year, > we should move the 2.2 into the lts branch and add Django 3.0. > But perhaps this should be done after 6.7. > > OK for this update to plug a few holes?
i might be a lone voice in this but i think a django port makes little sense. currently my work involves working with django daily and every django project will have a venv where all the deps will be installed, including django. system packages cannot help with this. another factor is the apps/libraries used with django which sometimes dictate the actual django version, for example some older dep might be not django 3 ready holding back the project to 2.*, etc. to be honest, this is mostly true for a lot of python packages/libs. this is one of the reasons i stopped updating/submitting new python packages to ports. i need them in the venv and ports cannot help me with that. this does not apply to applications proper of course, but django is framework, not a standalone application. -f -- it is easier to catch flies with honey than with vinegar.
