Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#43095 closed defect (fixed)

py27-dateutil: Please upgrade to 2.2 for Python 2.7

Reported by: wichert@… Owned by: skymoo (Adam Mercer)
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: Cc: dh@…
Port: py-dateutil

Description

dateutil 2.2 works perfectly on Python 2.7, so I see no reason to stick to 1.5 all Python versions <3.0 (which happened in r100134). This is currently preventing me from using libraries requiring a recent dateutil on Python 2.7.

Attachments (1)

dateutil-Portfile (2.0 KB) - added by wichert@… 6 years ago.
Updated Portfile

Download all attachments as: .zip

Change History (5)

Changed 6 years ago by wichert@…

Attachment: dateutil-Portfile added

Updated Portfile

comment:1 Changed 6 years ago by wichert@…

I have added a modified Portfile which:

  • uses python-dateutil 2.2 for all python versions
  • downloads from pypi over https

This seems to work for me.

comment:2 Changed 6 years ago by skymoo (Adam Mercer)

Cc: ram@… openmaintainer@… removed
Owner: changed from macports-tickets@… to ram@…
Status: newassigned

The reason why python versions less than 3.0 are stuck with 1.5 is because python-dateutil homepage says as such:

http://labix.org/python-dateutil#head-2f49784d6b27bae60cde1cff6a535663cf87497b

The home page doesn't mention anything about dateutil-2.2, according to that version 2.0 is the latest. However, looking at the VCS:

http://bazaar.launchpad.net/~dateutil/dateutil/trunk/view/head:/NEWS

It seems that the codebase was unified in the 2.1 release. This patch looks fine to me, I'll try to take a closer look tonight and get it comitted.

comment:3 Changed 6 years ago by skymoo (Adam Mercer)

Resolution: fixed
Status: assignedclosed

comment:4 Changed 6 years ago by wichert@…

Thanks for the quick response!

Note: See TracTickets for help on using tickets.