aboutsummaryrefslogtreecommitdiff
path: root/lang/python/django1
Commit message (Collapse)AuthorAge
* django1: bump to version 1.11.27Alexandru Ardelean2020-01-22
| | | | Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* django1: bump to version 1.11.26Alexandru Ardelean2019-11-18
| | | | Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* treewide: Use pypi.mk for Python packagesJeffery To2019-10-30
| | | | | | | | | | | | | This updates all Python packages that download their source from PyPi to use pypi.mk. This will allow future improvements/changes to pypi.mk to affect all relevant packages. This also makes it easier for future Python packages to start using pypi.mk, when it's clear how it is used in existing packages. Signed-off-by: Jeffery To <jeffery.to@gmail.com>
* django1: bump to version 1.11.25Alexandru Ardelean2019-10-29
| | | | Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* django: split django1 package and update to 2.2.6Alexandru Ardelean2019-10-24
After many failed attempts at upgrading Django to 2.2.6, the solution seems to be to split a `python-django1` package that works with Python2 and upgrade `python3-django` to the latest 2.2[.6] LTS release. This also means that all Python2 Django packages will be stuck & based on Django 1.11[.24] LTS release. But, it's currently the sanest approach I could find to be able to perform an upgrade of Django to 2.2, and not break Seafile. Upgrading Seafile is also pretty difficult, as their Python3 support is not yet finished & released. And in the meantime, we want to allow people to use newer Django versions. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>