From d0bfb17caaaaca4d6d200fba8b0e6043a16fc87f Mon Sep 17 00:00:00 2001
From: Michael Krotscheck <krotscheck@gmail.com>
Date: Tue, 3 Mar 2015 14:52:57 -0800
Subject: [PATCH] Added python-dateutil

Inside WSME's parse_isodatetime there's a switch that checks for the
existence of python_dateutil. If this does not exist, it falls back
on its own ISO parsing, which does not support timezones, and causes
havoc in our API. This adds the python_datetime dependency
(BSD License) that triggers this switch.

An unrelated change has been submitted to the WSME project to handle
timezone parsing: https://review.openstack.org/#/c/161013/

Change-Id: Ib1bbe1118cc04f7622d1d0ef3993594d5bd102f7
---
 requirements-py3.txt | 1 +
 requirements.txt     | 1 +
 2 files changed, 2 insertions(+)

diff --git a/requirements-py3.txt b/requirements-py3.txt
index 001d5bc7..314c73ca 100644
--- a/requirements-py3.txt
+++ b/requirements-py3.txt
@@ -26,3 +26,4 @@ tzlocal>=1.1.2
 Jinja2>=2.7.3
 PyMySQL>=0.6.2,!=0.6.4
 apscheduler>=3.0.1
+python_dateutil>=2.4.0
diff --git a/requirements.txt b/requirements.txt
index 300d4041..6927e238 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -27,3 +27,4 @@ email>=4.0.2
 Jinja2>=2.7.3
 PyMySQL>=0.6.2,!=0.6.4
 apscheduler>=3.0.1
+python_dateutil>=2.4.0
\ No newline at end of file