Re: Classic OOP in Python

Newsgroups	comp.lang.python
Date	2015-11-12 03:03 -0800
References	<23b2fae3-91d5-486b-9898-78b34bee486f@googlegroups.com> <16dc8c92-50e3-4fc8-ae25-cbc5b13e8971@googlegroups.com> <01adfef5-7edf-447c-9397-853c4fd65e53@googlegroups.com>
Message-ID	<6b0d08b3-5599-4952-85d2-a43c72ee71b2@googlegroups.com> (permalink)
Subject	Re: Classic OOP in Python
From	jongiddy <jongiddy@gmail.com>

Show all headers | View raw

On Thursday, 18 June 2015 12:21:29 UTC+1, Jason P.  wrote:
> 
> I'm aware of duck typing. The point in using interfaces is to be explicit about the boundaries of a system.
> 
> Quite a red "Growing Object-Oriented Software, Guided by Tests", by the way. In fact interfaces are key components in the style of building software they propose, in good company with TDD.
> 
> Thx!

Late to the party, but I have added a package `jute` to PyPI which provides interface checking closer to the model used in Java (and other compiled OO languages). See https://github.com/jongiddy/jute

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Classic OOP in Python jongiddy <jongiddy@gmail.com> - 2015-11-12 03:03 -0800

csiph-web