On 11/27/2013 06:46 PM, Alan Pevec wrote:
2013/11/27 Sean Dague s...@dague.net:
The problem is you can't really support both iso8601 was dormant
for years, and the revived version isn't compatible with the old
version. So supporting both means basically forking iso8601 and
maintaining you own
The problem is you can't really support both iso8601 was dormant for
years, and the revived version isn't compatible with the old version.
So supporting both means basically forking iso8601 and maintaining you
own version of it monkey patched in your own tree.
On Wed, Nov 27, 2013 at 1:58 AM,
Yes agreed with Sean, make compatible with both iso8601 is overcomplicated.
This is my abandoned try: https://review.openstack.org/#/c/53186/
zhiyan
On Wed, Nov 27, 2013 at 8:49 PM, Sean Dague s...@dague.net wrote:
The problem is you can't really support both iso8601 was dormant for
years, and
2013/11/27 Sean Dague s...@dague.net:
The problem is you can't really support both iso8601 was dormant for
years, and the revived version isn't compatible with the old version.
So supporting both means basically forking iso8601 and maintaining you
own version of it monkey patched in your own
On 11/27/2013 12:46 PM, Alan Pevec wrote:
2013/11/27 Sean Dague s...@dague.net:
The problem is you can't really support both iso8601 was dormant for
years, and the revived version isn't compatible with the old version.
So supporting both means basically forking iso8601 and maintaining you
own
I'm sorry to restart this topic.
I don't mind if we upgrade to 0.1.8, but then I will need to have
patches for Havana to support version 0.1.8. Otherwise, it's going to be
very difficult on the packaging side: I will need to upload 0.1.8 for
Icehouse, but then it will break everything else (eg:
after update to iso8601=0.1.8, it breaks stable/neutron jenkins tests,
because stable/glance requires iso8601=0.1.4, log info
https://jenkins02.openstack.org/job/periodic-tempest-devstack-vm-neutron-stable-grizzly/43/console
,
I have filed a bug to track this
It seems like adopting 0.1.8 is the right approach. If it doesn't work with
other projects, we should work to help those projects get updated to work
with it.
--Morgan
On Thursday, October 24, 2013, Zhi Yan Liu wrote:
Hi all,
Adopt 0.1.8 as iso8601 minimum version:
Hi folks!
In the images api, we depend on iso8601 to parse some dates and times.
Recently, since version 0.1.4, python-iso8601 added support for a few more
formats, and we finally got some other issues nailed down by 0.1.8. Maybe
the fact that these formats weren't supported before was a bug. I
Hi,
Why not use python-dateutil?
Regards
chuck
On Wed, Oct 23, 2013 at 11:34 AM, Mark Washenberger
mark.washenber...@markwash.net wrote:
Hi folks!
In the images api, we depend on iso8601 to parse some dates and times.
Recently, since version 0.1.4, python-iso8601 added support for a few
+1 to option #1
-- dims
On Wed, Oct 23, 2013 at 2:34 PM, Mark Washenberger
mark.washenber...@markwash.net wrote:
Hi folks!
In the images api, we depend on iso8601 to parse some dates and times.
Recently, since version 0.1.4, python-iso8601 added support for a few more
formats, and we
On 24 October 2013 07:34, Mark Washenberger
mark.washenber...@markwash.net wrote:
Hi folks!
1) Adopt 0.1.8 as the minimum version in openstack-requirements.
2) Do nothing (i.e. let Glance behavior depend on iso8601 in this way, and
just fix the tests so they don't care about these extra
On Wed, Oct 23, 2013 at 2:30 PM, Robert Collins
robe...@robertcollins.netwrote:
On 24 October 2013 07:34, Mark Washenberger
mark.washenber...@markwash.net wrote:
Hi folks!
1) Adopt 0.1.8 as the minimum version in openstack-requirements.
2) Do nothing (i.e. let Glance behavior depend on
13 matches
Mail list logo
