Permalink
Commits on Sep 28, 2017
  1. Merge pull request #242 from collective/MStimezones

    thet committed Sep 28, 2017
    Accept Windows timezone identifiers as valid.
  2. Accept Windows timezone identifiers as valid.

    geier committed Sep 28, 2017
    Currently we accept Olson timezone identifiers (tzids) as valid, even
    when no matching VTIMEZONE component is present.  Windows tzids are
    different from Olson tzids, but also far spread.  Some software produces
    .ics files using those Windows tzids with missing VTIMEZONE components.
    While in general our stance is to only support standard compliant .ics
    files and try to get the issuer of the invalid .ics files to fix their
    software, I believe our chances here are very slim.  On the other hand,
    a lot of those .ics files exist in the wild and not supporting those
    Windows tzids is a source of major inconvenience for our users.  We
    should there accept Windows tzids as we do for Olson tzids.  The unicode
    consortium has a suggested mapping from Windows tzids to Olson tzids
    [0], which we now make use of.
    
    [0] http://www.unicode.org/cldr/charts/29/supplemental/zone_tzid.html
  3. Merge pull request #238 from clivest/fix/237

    geier committed Sep 28, 2017
    Fix non-ascii TZID and TZNAME handling in python 2
  4. Merge branch 'master' into fix/237

    geier committed Sep 28, 2017
Commits on Sep 23, 2017
  1. Update install.rst (#240)

    Ekran committed with untitaker Sep 23, 2017
    * Update install.rst
    
    change to pip install instead of not referenced setup.py
    
    * Update CHANGES.rst
    
    add a line for changed install instruction in wiki to use pip
Commits on Aug 27, 2017
  1. Back to development: 3.11.8

    esteele committed Aug 27, 2017
    [ci skip]
  2. Preparing release 3.11.7

    esteele committed Aug 27, 2017
    [ci skip]
  3. Cleaned up empty headers from changelog.

    esteele committed Aug 27, 2017
    [ci skip]
Commits on Aug 17, 2017
  1. Fix non-ascii TZID and TZNAME handling in python 2

    clivest committed Aug 17, 2017
    Zone needs to be a python 2 str because it's used as the timezone type name.
    Zone name is a python 2 str for consistency with pytz. Needs to be made
    unique if the conversion is inexact
Commits on Aug 16, 2017
  1. Merge pull request #235 from collective/fix/155

    geier committed Aug 16, 2017
    Allow ignoring of TZ offsets > 24h
Commits on Aug 4, 2017
  1. Back to development: 3.11.7

    mauritsvanrees committed Aug 4, 2017
    [ci skip]
  2. Preparing release 3.11.6

    mauritsvanrees committed Aug 4, 2017
    [ci skip]
  3. Added changelog entry for last change.

    mauritsvanrees committed Aug 4, 2017
    [ci skip]
Commits on Jul 25, 2017
  1. Merge pull request #234 from collective/fix/timezone_count

    geier committed Jul 25, 2017
    Fix VTIMEZONEs including RDATEs
Commits on Jul 18, 2017
  1. Allow ignoring of TZ offsets > 24h

    geier committed Jul 18, 2017
    fixes #155
Commits on Jul 3, 2017
  1. Back to development: 3.11.6

    esteele committed Jul 3, 2017
    [ci skip]
  2. Preparing release 3.11.5

    esteele committed Jul 3, 2017
    [ci skip]
Commits on Jul 2, 2017
  1. fix timezone count

    geier committed Jun 22, 2017
  2. Test for VTIMEZONES with RDATEs

    geier committed Jul 2, 2017
Commits on Jun 25, 2017
  1. Merge pull request #232 from polyzen/patch-1

    geier committed Jun 25, 2017
    readme: Touch up
  2. readme: Touch up

    polyzen committed Jun 25, 2017
Commits on Jun 20, 2017
  1. Merge pull request #228 from geier/fix/227

    geier committed Jun 20, 2017
    Fix dealing with non unique VTIMEZONE components
  2. Fix handling of non-unique VTIMEZONEs.

    geier committed May 26, 2017
    We should probably choose a better system for generating unique TZNAMEs.
  3. Reproduce #227

    geier committed May 26, 2017
    The issue here is that both VTIMEZONE subcomponents have the same
    TZOFFSETFROM, TZOFFSETTO and DTSTART, but one is a DAYLIGHT and the
    other is a STANDARD component. While this makes them pretty
    useless and, if it is standard compliant, it probably shouldn't be.
  4. Merge pull request #229 from collective/fix/218

    geier committed Jun 20, 2017
    Assertion for VTIMEZONE sub-components' DTSTART
Commits on Jun 19, 2017
Commits on May 26, 2017
  1. Assertion for VTIMEZONE sub-components' DTSTART

    geier committed May 26, 2017
Commits on May 10, 2017
  1. Back to development: 3.11.5

    esteele committed May 10, 2017
    [ci skip]
  2. Preparing release 3.11.4

    esteele committed May 10, 2017
    [ci skip]
Commits on Apr 18, 2017
  1. Merge pull request #220 from collective/fix/217

    geier committed Apr 18, 2017
    Fix handling of VTIMEZONEs with subcomponents with the same DTSTARTs
    
    fixes #217
  2. Fix handling of VTIMEZONEs with subcomponents with the same DTSTARTs

    geier committed Mar 22, 2017
    For VTIMEZONE subcomponents without a TZNAME we would construct a
    TZNAME from their shared TZID and DTSTART, if their DTSTART was equal,
    this would lead to the same TZNAME and with that to a broken timezone
    object.
    
    Fixes #217.
  3. Reproduce #217

    geier committed Mar 22, 2017
  4. Merge pull request #207 from geier/fix_base64_equal

    geier committed Apr 18, 2017
    Allow `=` in parameter values.
  5. Extend tests

    untitaker committed with geier Jan 19, 2017