<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div><br>On May 4, 2016, at 2:34 PM, Burton, Ross <<a href="mailto:ross.burton@intel.com">ross.burton@intel.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 4 May 2016 at 22:29, Mark Hatle <span dir="ltr"><<a href="mailto:mark.hatle@windriver.com" target="_blank">mark.hatle@windriver.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":3bw" class="a3s aXjCH">I'd hate for someone to bring in a layer and find it doesn't work, without<br>
understanding WHY it doesn't work.<br>
<br>
Alternative would be to change the 'python' identifier to 'python3'.. Then if<br>
'python' is parsed, we error?</div></blockquote></div><br>That sounds like a lot of dull work. If a layer's class is using python2 syntax and runs under python3 then it will generally throw exceptions, right?</div><div class="gmail_extra"><br></div></div></div></blockquote>Yes, you will see a lot of TypeError, SyntaxError and other exceptions. In fact, the try:catch handling for those exceptions is a frequent crutch for py2-py3 compatibility. The other biggest PITA is str vs unicode and friends. Look at the recent commits for pystatgrab (upstream) as an example.<div><br></div><div>Ripping off the band-aid sounds ok to me too. Flag day +1<br><div><br></div><div>--Tim</div><div><br></div><div>"Just as long as we aren't switching to perl6 at the same time."</div><div><br><blockquote type="cite"><div><div dir="ltr"><div class="gmail_extra">Ross</div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Openembedded-architecture mailing list</span><br><span><a href="mailto:Openembedded-architecture@lists.openembedded.org">Openembedded-architecture@lists.openembedded.org</a></span><br><span><a href="http://lists.openembedded.org/mailman/listinfo/openembedded-architecture">http://lists.openembedded.org/mailman/listinfo/openembedded-architecture</a></span><br></div></blockquote></div></div></body></html>