<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I don't think it does undermine 2.0's philosophy of "style changes
only" as this doesn't affect the code in anyway as we don't add in
any new features in 2.0, therefore MPL-2.0 will still work fine with
python-2.6, we just won't officially support python-2.6 with version
2.0, and should we have minor releases (2.0.1) then we don't have to
worry about py-2.6. 2.0 feels like a more appropriate place to drop
it.<br>
<br>
Best,<br>
OceanWolf<br>
<br>
<div class="moz-cite-prefix">On 14/09/15 22:17, Nathaniel Smith
wrote:<br>
</div>
<blockquote
cite="mid:CAPJVwB=72wCfeL0Lc+a_osMhiegxKAheWx+tWkDpzx45fY-e0w@mail.gmail.com"
type="cite">
<p dir="ltr">It seems like a good idea in general to me, but
doesn't it kinda undermine the "2.0 is style changes only"
idea/messaging? I assume the maintenance burden of supporting
the old versions in 2.0 won't be large compared to 1.5 given
this... Maybe 2.1 (or 1.5!) would be a better place to draw the
line?</p>
<div class="gmail_quote">On Sep 14, 2015 12:49 PM, "Thomas
Caswell" <<a moz-do-not-send="true"
href="mailto:tcaswell@gmail.com">tcaswell@gmail.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>Hey all,</div>
<div><br>
</div>
<div>I would like to propose the following for which version
of python mpl officially supports:</div>
<div><br>
</div>
<div> - for v1.5 we continue to support 2.6, 2.7, 3.3-3.5</div>
<div> - for v2.0 forward we support (2.7, 3.4, 3.5)</div>
<div><br>
</div>
<div>and allow for new, python3 only, features to be
developed for mpl2.1 onward, so long as they do not break
any existing functionality in py2.7.</div>
<div><br>
</div>
<div>We already support all of those versions on master,
there is no good reason to drop 2.6 support right before
the RC. For 2.0 we should drop 2.6 so that we do not have
to maintain a mpl2.0.x py2.6 compatible bug-fix branch.</div>
<div><br>
</div>
<div>Regarding dropping 2.6 as a supported version I suggest
you read/watch the following from Nick Coghlan:</div>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="http://www.curiousefficiency.org/posts/2015/04/stop-supporting-python26.html"
target="_blank">http://www.curiousefficiency.org/posts/2015/04/stop-supporting-python26.html</a></div>
<div><a moz-do-not-send="true"
href="http://www.pyvideo.org/video/3764/contributors-colleagues-clients-customers-su"
target="_blank">http://www.pyvideo.org/video/3764/contributors-colleagues-clients-customers-su</a></div>
<div><br>
</div>
<div>We are resource limited and those resources would be
better spent improving the library and supporting modern
version of python. At some point it is unreasonable for
people running very old installations of python to expect
the the newest versions of down-stream tools to work. If
this is important to someone, please step up to mange
maintaining a 1.5.x bug-fix branch which will maintain 2.6
compatibility.</div>
<div><br>
</div>
<div>Dropping 2.6 will also free us to being using
OrderedDict and several other language features added in
2.7.</div>
<div><br>
</div>
<div>Regarding dropping 3.3, every survey has shown that
among the users who have adopted py3, a vast majority are
using the newest version so supporting and testing against
the older versions of 3 is not worth the effort.</div>
<div><br>
</div>
<div>
<div>In all cases, versions of mpl that currently work on
legacy versions of python will continue to work.</div>
<div><br>
</div>
<div>Thanks to Eric, Mike, and Phil who have this a read
over.</div>
<div><br>
</div>
<div>Tom</div>
</div>
</div>
<br>
_______________________________________________<br>
Matplotlib-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:Matplotlib-devel@python.org">Matplotlib-devel@python.org</a><br>
<a moz-do-not-send="true"
href="https://mail.python.org/mailman/listinfo/matplotlib-devel"
rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/matplotlib-devel</a><br>
<br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Matplotlib-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Matplotlib-devel@python.org">Matplotlib-devel@python.org</a>
<a class="moz-txt-link-freetext" href="https://mail.python.org/mailman/listinfo/matplotlib-devel">https://mail.python.org/mailman/listinfo/matplotlib-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>