<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Got it. Thanks.<br>
<br>
<div class="moz-cite-prefix">On 10.09.2015 05:40, Jukka Lehtosalo
wrote:<br>
</div>
<blockquote
cite="mid:CAA_f+LxA+SVnK5S8q+kG+7g_47MFYGgu1Hb1thCM8ws7O9+hww@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Wed, Sep 9, 2015 at 2:16 PM, Sven
R. Kunze <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:srkunze@mail.de" target="_blank">srkunze@mail.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Thanks for sharing,
Guido. Some random thoughts:<br>
<br>
- "classes should need to be explicitly marked as
protocols"<br>
If so, why are they classes in the first place? Other
languages has dedicated keywords like "interface".<br>
</div>
</blockquote>
<div><br>
</div>
<div>I want to preserve compatibility with earlier Python
versions (down to 3.2), and this makes it impossible to
add any new syntax. Also, there is no need to add a
keyword as there are other existing mechanisms which are
good enough, including base classes (as in the proposal)
and class decorators. I don't think that this will become
a very commonly used language feature, and thus adding
special syntax for this doesn't seem very important. My
expectation is that structural subtyping would be
primarily useful for libraries and frameworks.</div>
<div><br>
</div>
<div>Jukka</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>