`<div dir="ltr">No Python 3.x ?</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 10, 2017 at 6:04 PM, Dale Ghent <span dir="ltr"><<a href="mailto:daleg@omniti.com" target="_blank">daleg@omniti.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On Jan 10, 2017, at 5:04 PM, Dominik Hassler <<a href="mailto:hasslerd@gmx.li">hasslerd@gmx.li</a>> wrote:<br>
><br>
</span><span class="">> @Dan: LX zones are considered BETA in r20 and r22 seems to be "late", is there a chance to get LX bleeding edge in r20 w/o the risk of breaking something else?<br>
<br>
</span>Zones in 020 is still largely in sync with the LX code currently in bloody (021). Since zones (beta) was released with 020, we’ve been primarily focussed on other items required for 022, the most laborious of which is the Python 2.6 -> 2.7 upgrade. This is needed for a number of reasons. First, the benefits of getting off of 2.6 and on to 2.7 is self-explanatory, but 2.7 is also needed for being able to stay in sync with the pkg code, as well as the next big project for 022 - a loader-enabled installer (text installer and kayak) to replace the current one.<br>
<br>
In the mean-time, we’re always looking for ideas (and even contributions!) from the community on how best to handle the management and administrivia involved with LX zones. For now, we’d like this to stay within the realm of zoneadm/zonecfg and family.<br>
<span class="HOEnZb"><font color="#888888"><br>
/dale<br>
</font></span><br>______________________________<wbr>_________________<br>
OmniOS-discuss mailing list<br>
<a href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.<wbr>com</a><br>
<a href="http://lists.omniti.com/mailman/listinfo/omnios-discuss" rel="noreferrer" target="_blank">http://lists.omniti.com/<wbr>mailman/listinfo/omnios-<wbr>discuss</a><br>
<br></blockquote></div><br></div>
`