Opened 10 years ago

Closed 9 years ago

#47390 closed update (fixed)

py-django: Update to latest version

Reported by: my@… Owned by: petrrr
Priority: Normal Milestone:
Component: ports Version:
Keywords: haspatch Cc: jgoldstein22@…, kobayos, jeabraham, petrrr
Port: py-django

Description

Since Django 1.8 was released on April 2, please update it to the latest version. Thanks!!

Attachments (3)

Portfile.patch (946 bytes) - added by kobayos 9 years ago.
Portfile2.patch (946 bytes) - added by kobayos 9 years ago.
Portfile3.patch (940 bytes) - added by kobayos 9 years ago.
26 and 33 are removed from python.versions

Download all attachments as: .zip

Change History (16)

comment:1 Changed 10 years ago by mf2k (Frank Schima)

Cc: nomaintainer@… removed
Keywords: django removed
Version: 2.3.3

Please do not Cc nomaintainer@… because it is not a valid email address.

comment:2 Changed 9 years ago by mf2k (Frank Schima)

Cc: jgoldstein22@… added
Summary: Upgrade Django to 1.8py-django: Update to latest version

Cc reporter of #50086.

Changed 9 years ago by kobayos

Attachment: Portfile.patch added

comment:3 Changed 9 years ago by kobayos

I made a patch to upgrade py-django from 1.7.1 to 1.9.1. (Just update version number and checksums.)

I confirmed this patch enables to install django 1.9.1 on python 3.5.1 without any errors.

However, I have not checked it on the other versions of python, and further, I also have not checked whether it works correctly or not as well.

Are there anyone who check it?

comment:4 Changed 9 years ago by kobayos

Cc: kobayos@… added

Cc Me!

comment:5 Changed 9 years ago by mf2k (Frank Schima)

Cc: jea@… added
Keywords: haspatch added

Cc reporter of duplicate #50842.

comment:6 Changed 9 years ago by petrrr

Cc: petr@… added

Cc Me!

comment:7 Changed 9 years ago by kobayos

I made a patch to upgrade py-django from 1.7.1 to 1.9.4 by changing version number, checksums and python.versions and confirmed it was successfully installed with python 3.5.1. I wish someone would check it.

Changed 9 years ago by kobayos

Attachment: Portfile2.patch added

comment:8 Changed 9 years ago by petrrr

Can we retire py26 and py33 as well? There are some py26 dependents which would need to be retired as well.

comment:9 Changed 9 years ago by kobayos

According to the following link, Django 1.9 requires python 2.7, 3.4 or 3.5. https://docs.djangoproject.com/en/1.9/faq/install/

It seems that 1.7 should be kept for the dependencies if the dependencies are really necessary although even security patch is not supplied for this release anymore according to following site. https://www.djangoproject.com/download/

Should we make a new port for Django 1.9.4? Even in the case, I am wondering that py-django should be updated to 1.7.11 that is the latest version of 1.7 series.

Last edited 9 years ago by kobayos (previous) (diff)

Changed 9 years ago by kobayos

Attachment: Portfile3.patch added

26 and 33 are removed from python.versions

comment:10 Changed 9 years ago by petrrr

Fine to remove py26 and py33, we are retiring py26 and py33 anyway.

Just need to make sure all depending ports are removed as well. And all these ports need graveyarding ...

comment:11 Changed 9 years ago by petrrr

Owner: changed from macports-tickets@… to petr@…

comment:12 Changed 9 years ago by petrrr

Committed in r147075. Thanks a lot for contributing!

comment:13 Changed 9 years ago by petrrr

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.