attoparsec-iso8601: Parsing of ISO 8601 dates, originally from aeson.

This is a package candidate release! Here you can preview how this package release will appear once published to the main package index (which can be accomplished via the 'maintain' link below). Please note that once a package has been published to the main package index it cannot be undone! Please consult the package uploading documentation for more information.

[maintain] [Publish]

Warnings:

Parsing of ISO 8601 dates, originally from aeson.


[Skip to Readme]

Properties

Versions 1.0.0.0, 1.0.0.0, 1.0.1.0, 1.0.2.0
Change log None available
Dependencies attoparsec (>=0.13.0.1), base (>=4.5 && <5), base-compat (>=0.9.1 && <0.10), text (>=1.1.1.0), time (>=1.1.1.4) [details]
License BSD-3-Clause
Copyright (c) 2011-2016 Bryan O'Sullivan (c) 2011 MailRank, Inc.
Author Bryan O'Sullivan <bos@serpentine.com>
Maintainer Adam Bergmark <adam@bergmark.nl>
Category Parsing
Home page https://github.com/bos/aeson
Bug tracker https://github.com/bos/aeson/issues
Source repo head: git clone git://github.com/bos/aeson.git
Uploaded by AdamBergmark at 2017-04-20T08:05:30Z

Modules

[Index]

Manual Flags

NameDescriptionDefault
developer

operate in developer mode

Disabled
fast

compile without optimizations

Disabled
Automatic Flags
NameDescriptionDefault

Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info

Downloads

Maintainer's Corner

For package maintainers and hackage trustees


Readme for attoparsec-iso8601-1.0.0.0

[back to package description]

Parsing of ISO 8601 dates.

This package is used to parse dates in aeson. It is split into a separate package to be shared by other projects that want to parse dates like aeson does.

For now, this project is located in the aeson repository and aeson itself uses the source of this package without pulling in the package as a dependency.

Stability

Since aeson depends on this package we want to be very careful about changing the format.

There may be breaking changes if we find that the format is incorrectly too lenient. We consider widening of the allowed input a non-breaking addition since all previously valid input will still parse correctly.