<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi,<div class=""><br class=""><div><blockquote type="cite" class=""><div class=""><div class=""><blockquote type="cite" class="">However, the person who reported the error to me claimed he only used `port select` and didn't create the symlink himself. I didn't push him to know how nor did I try myself, but if indeed `port select` allows this calling it a "user error" is a bit unjust. You cannot expect every user to know that plain `python` should resolve to a v2 interpreter (I also didn't), and `port select` shouldn't be able to break that rule.<br class=""></blockquote><br class="">From my point of view, yes, MacPorts allows the user to commit this error, and we should fix MacPorts to prevent such an error, or at least warn the user about it, hence the ticket whose URL I mentioned earlier.<br class=""></div></div></blockquote></div><br class=""></div><div class="">Please note, the comment in that ticket referring to the PEP is 3 years old, and the PEP itself was last modified in 2015.</div><div class=""><br class=""></div><div class="">The PEP itself notes that </div><div class=""><br class=""></div><div class="">"<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Arial, Verdana, Geneva, "Bitstream Vera Sans", Helvetica, sans-serif; font-size: 14.640419960021973px; background-color: rgb(255, 255, 255);" class="">It is anticipated that there will eventually come a time where the third party ecosystem surrounding Python 3 is sufficiently mature for this recommendation to be updated to suggest that the </span><tt class="literal docutils" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">python</tt><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Arial, Verdana, Geneva, "Bitstream Vera Sans", Helvetica, sans-serif; font-size: 14.640419960021973px; background-color: rgb(255, 255, 255);" class=""> symlink refer to </span><tt class="literal docutils" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">python3</tt><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Arial, Verdana, Geneva, "Bitstream Vera Sans", Helvetica, sans-serif; font-size: 14.640419960021973px; background-color: rgb(255, 255, 255);" class=""> rather than </span><tt class="literal docutils" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">python2</tt><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Arial, Verdana, Geneva, "Bitstream Vera Sans", Helvetica, sans-serif; font-size: 14.640419960021973px; background-color: rgb(255, 255, 255);" class="">.</span><font color="#000000" face="Arial, Verdana, Geneva, Bitstream Vera Sans, Helvetica, sans-serif" class=""><span style="caret-color: rgb(0, 0, 0); font-size: 14.640419960021973px;" class="">”</span></font></div><div class=""><br class=""></div><div class="">I am not saying day that is now, but given python 2.7 is EOL next year (last time I checked) I think it is at this point less of an error for a user to have ‘python’ point to ‘python3’ than it was when that ticket was opened.</div><div class=""><br class=""></div><div class="">For me, we should allow ‘port select python’ to select a 3.x version, but at the moment issue a warning to the user if they do this they might have problems.</div><div class=""><br class=""></div><div class="">Also none of what a user might or might not do with port select should have any bearing on how any given port works. If it does, it is a bug in that port. ports should be written to, if they are sensitive to the python version used, explicitly configure their builds to use a specific macports python version, and not rely on whatever the environment provides.</div><div class=""><br class=""></div><div class="">Chris</div></body></html>