robjhornby

Just looking out of interest. This is handled by [_parse_iso8601_duration](https://github.com/sdispater/pendulum/blob/411d0aa41a5f39c5f4a2f43a3c369c2dd24787db/pendulum/parsing/iso8601.py#L262). The number of digits after the decimal marker is unlimited in the regex to capture minutes: https://github.com/sdispater/pendulum/blob/411d0aa41a5f39c5f4a2f43a3c369c2dd24787db/pendulum/parsing/iso8601.py#L74 but is assumed...

The IANA timezone `Etc/GMT+3` is defined as a UTC offset of `-03:00` - [Wikipedia page](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones); the original source is the [IANA database](https://www.iana.org/time-zones). i.e. I don't think this is a bug

Hope you're doing well too. I'm not affiliated with Pendulum by the way. I agree it's odd and can be confusing that `Etc/GMT+x` is the other way round. At least...

Making it different for 2 or more nodes sounds good - the 1 node case already looks ideal. Here are a couple of more streamlined ideas. I'm not sure how...

I just realised it's also very similar to AlternatingSequence, with 2 parts disconnected: