<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=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span class="Apple-tab-span" style="white-space:pre"> </span>ciao,<div class=""><br class=""></div><div class="">is there any overall strategy regarding the update of perl and python version as dependencies?</div><div class=""><br class=""></div><div class="">exampli gratia, i refer to the following ticket: </div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://trac.macports.org/ticket/61092" class="">https://trac.macports.org/ticket/61092</a> </div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://trac.macports.org/ticket/61097" class="">https://trac.macports.org/ticket/61097</a> </div><div class=""><br class=""></div><div class="">locally i have update perl version to perl30 (just like i have done with littleutils, wget, intltool, help2man) to avoid having two different perl versions in the system.</div><div class=""><br class=""></div><div class="">beyond search for open tickets, each time i check against the upstream developers if there is some incompatibility and/or bug ticket for the landing version. is that enough before submitting the pr?</div><div class=""><br class=""></div><div class="">if that’s the case and it is where we are supposed to move forward, i can volunteer to look for ports depending on perl28 and update them to perl30 (i know it’s a repetitive and boring task, but it could be really useful for me to learn quicker about macports dynamics).</div><div class=""><br class=""></div><div class="">same situation for pyrhon. i have already with thefuck, LyX and global updating to 3.9. </div><div class="">also, in this case, i have been told not creating a new variant for python3.9 leaving the python27 variant, but to replace 27 with 39. </div><div class=""><br class=""></div><div class="">cheers,</div><div class="">—</div><div class="">ferdy</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></div></div></body></html>