<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Mojca,<div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On May 5, 2017, at 3:35 PM, Mojca Miklavec <<a href="mailto:mojca@macports.org" class="">mojca@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Often a question of what to do with Python 3.4 modules gets raised now<br class="">that Python 3.6 has been out for a while (but its support is not<br class="">nearly complete).<br class=""><br class="">That is:<br class="">- Should new ports include 34 subports or not?</div></div></blockquote><div><br class=""></div><div>I think we should not. I don’t want to get into the same situation as perl where we had so many different versions which made supporting the latest version even harder. Testing old versions ultimately slows down modules from getting updated. </div><br class=""><blockquote type="cite" class=""><div class=""><div class="">- Should we actively remove 34 subports?<br class=""></div></div></blockquote><div><br class=""></div><div>When py35 and py36 have more sub-ports, then yes. </div><div><br class=""></div><div><font face="Monaco" class="">$ port list py34-* | wc -l<br class=""> 654<br class="">$ port list py35-* | wc -l<br class=""> 520<br class="">$ port list py36-* | wc -l<br class=""> 323<br class=""></font><br class=""></div><div>I think we should strive to support the latest versions of python 2 and 3 only. </div><div><br class=""></div><div><br class=""></div><div>Cheers!</div><div>Frank</div><div><br class=""></div></div></div></body></html>