Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: Random832 <random832@fastmail.com>
Newsgroups: comp.lang.python
Subject: Re: ANN: intervalset Was: Set type for datetime intervals
Date: Mon, 04 Apr 2016 11:09:57 -0400
Lines: 65
Message-ID: <mailman.21.1459782605.32530.python-list@python.org>
References: <56FE0625.5030901@shopzeus.com> <1459523394.2611014.565840994.593DD99A@webmail.messagingengine.com> <570213CB.8040101@shopzeus.com> <1459782597.3444051.568344234.048046C6@webmail.messagingengine.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <570213CB.8040101@shopzeus.com>
Precedence: list
Xref: csiph.com comp.lang.python:106445

On Mon, Apr 4, 2016, at 03:12, Nagy L=C3=A1szl=C3=B3 Zsolt wrote:
>=20
>   Hi All,
>=20
> If anyone is interested, a module was born:
>=20
> https://bitbucket.org/nagylzs/intervalset
> https://pypi.python.org/pypi/intervalset/0.1.1

I don't know if I like it being immutable. Maybe have separate mutable
and immutable versions.

Like I said before, I don't think the set-like operations on Intervals
are useful - what can you accomplish with them rather than by making a
set consisting of only one interval and doing operations on that?

> I have some unit tests, but testers and comments are welcome.
>=20
> Also see below.
>=20
> Yes, you are right. It is a set of non-intersecting intervals.
>=20
> > It could
> > also be useful to have one for numbers (the datetime version could even
> > maybe be implemented in terms of it)
> Well, please check sources on bitbucket. You are more than welcome to
> join the project.
> >
> >> element ::=3D (start_point_in_time, end_point_in_time)
> >> intervalset ::=3D { element1, element2, .... }
> > Are these open intervals or closed intervals?
> Closed. In my particular implementation, there is a singleton for all
> empty intervals. It is not possible to create an arbitrary interval with
> the same starting and ending time (the singleton being the only
> exception).

An "arbitrary interval with the same starting and ending time" would be
more like an isolated datetime (i.e. 00:00 is in the set but 23:59 or
00:01 is not)

> I think that implementing open intervals would be much more
> difficult, and we would have to know and use the smallest possible
> increment (resolution) of the date/time type. Which may be platform
> dependent.

My suggestion was to use boolean flags, and to use that to control
whether to use < or <=3D to test for membership.

An open interval is more like an hour where 00:00 is included and
00:59:59.999999 is included but 01:00 is not. With discrete resolution
it's as simple as just moving the endpoint off by one unit, but I think
it'd be cleaner to use flags (you'd need it for numeric intervals, since
numeric types can have any resolution).

>    def __contains__(self, other):
>        """Containment relation.
>
>        Tell if `other` is contained *completely* in this set. The argumen=
t can either be an Interval or an
>        IntervalSet.
>        """

I don't think this is appropriate for this operation; this should be
__gt__. __contains__ should test a datetime (or whatever type item), not
another Interval/IntervalSet.