<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="">
It seems like it would be a good idea to include a section for periodic review and updating of the language standards support. That is, do we review and reissue with each major version release (e.g., 7 -> 8)? Each sub-major release (7.8 -> 7.9). Or do we review
and potentially update with any major/sub-major update of the language and its distribution (e.g., Python 2 -> 3 or 3.7 -> 3.8)? Or are there other ways to decide when to do review and update this standard?
<div class=""><br class="">
</div>
<div class="">Michael<br class="">
<div class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="orphans: 2; text-align: -webkit-auto; text-indent: 0px; widows: 2; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<span class="Apple-style-span" style="border-collapse: separate; orphans: 2; text-indent: 0px; widows: 2; border-spacing: 0px;">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<span class="Apple-style-span" style="border-collapse: separate; orphans: 2; text-indent: 0px; widows: 2; border-spacing: 0px;">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<span class="Apple-style-span" style="border-collapse: separate; orphans: 2; text-indent: 0px; widows: 2; border-spacing: 0px;">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<span class="Apple-style-span" style="border-collapse: separate; orphans: 2; text-indent: 0px; widows: 2; border-spacing: 0px;">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<span class="Apple-style-span" style="border-collapse: separate; orphans: 2; text-indent: 0px; widows: 2; border-spacing: 0px;">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<span class="Apple-style-span" style="border-collapse: separate; orphans: 2; text-indent: 0px; widows: 2; border-spacing: 0px;">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<span class="Apple-style-span" style="border-collapse: separate; orphans: 2; text-indent: 0px; widows: 2; border-spacing: 0px;">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<span class="Apple-style-span" style="border-collapse: separate; orphans: 2; text-indent: 0px; widows: 2; border-spacing: 0px;">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<font color="#5e5e5e" class="">
<div style="color: rgb(0, 0, 0); font-style: normal; caret-color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; text-decoration: none; -webkit-text-stroke-width: 0px; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-east-asian: normal; font-variant-position: normal; line-height: normal; -webkit-text-decorations-in-effect: none;" class="">
_____________________________</div>
<div style="font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; line-height: normal;" class="">
<span style="font-style: normal; font-size: 12px;" class="">C. Michael Barton <br class="">
Director, Center for Social Dynamics & Complexity<br class="">
Director, Network for Computational Modeling in Social & Ecological Sciences<br class="">
Associate Director, School of Complex Adaptive Systems<br class="">
Professor, School of Human Evolution & Social Change<br class="">
Arizona State University<br class="">
Tempe, AZ 85287-2402<br class="">
USA<br class="">
<br class="">
voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)<br class="">
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)<br class="">
www: <a href="http://shesc.asu.edu" class="">http://shesc.asu.edu</a>, <a href="https://complexity.asu.edu" class="">https://complexity.asu.edu</a>, <a href="http://www.public.asu.edu/~cmbarton" class="">http://www.public.asu.edu/~cmbarton</a></span></div>
</font></div>
</span></div>
</span></div>
</span></div>
</span></div>
</span></div>
</span></div>
</span></div>
</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Mar 16, 2021, at 12:30 PM, Veronica Andreo <<a href="mailto:veroandreo@gmail.com" class="">veroandreo@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div class="">Hi everyone</div>
<div class=""><br class="">
</div>
<div class="">Thanks for all the feedback. <br class="">
</div>
<div class=""><br class="">
</div>
<div class="">In practical terms then, shall we:</div>
<div class="">- remove all python references from the Language Standards draft RFC [0] and vote only for C/C++, while creating a separate RFC for the minimum python version?
<br class="">
</div>
<div class="">- add a formula that sets on which pace the minimum supported python version will change to the Language Standards draft RFC [0] and vote for everything altogether?
<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Vero<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">[0] <a href="https://urldefense.com/v3/__https://trac.osgeo.org/grass/wiki/RFC/7_LanguageStandardsSupport__;!!IKRxdwAv5BmarQ!IGGdA3JGHwIvM70uQAxKgP-SoAnSPcupVWcVBGmLKhV4ocBAMqqxF8S2vhiwWU_ODXbcMWU$" class="">
https://trac.osgeo.org/grass/wiki/RFC/7_LanguageStandardsSupport</a></div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">El mar, 2 mar 2021 a las 22:54, Markus Neteler (<<a href="mailto:neteler@osgeo.org" class="">neteler@osgeo.org</a>>) escribió:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi all,<br class="">
<br class="">
On Tue, Mar 2, 2021 at 8:15 AM Nicklas Larsson via grass-dev<br class="">
<<a href="mailto:grass-dev@lists.osgeo.org" target="_blank" class="">grass-dev@lists.osgeo.org</a>> wrote:<br class="">
><br class="">
> Good, Anna, you brought up this question on regular update of Python version support. I deliberately left that part out of the draft for setting/updating language standards, as I would argue it deserves a RFC on its own.<br class="">
<br class="">
I agree to both:<br class="">
<br class="">
- we need to find a formula with our release rhythm and the oldest<br class="">
still supported Python version,<br class="">
- and yes, please let's separate this out into a different discussion<br class="">
(RFC if needed).<br class="">
<br class="">
I.e., one C/C++ RFC and one Python RFC.<br class="">
<br class="">
> A RFC should't be updatable, but may be overridden, partly or completely, with a new RFC. Adopting adherence to a new C or C++ standard will most likely be a quite rare business and should be dealt with a new RFC.<br class="">
<br class="">
I agree to that, as it would become a moving target otherwise.<br class="">
<br class="">
> The discussed approach, following the Python versions life-cycle, could possibly look a little different, however the forms and modes for this should be established likewise with a RFC.<br class="">
><br class="">
> If we agree now, to set Python 3.6 as a minimum, we have roughly six months to work out such a procedure. I’m glad to assist to this in, say around, October, in time for the 3.6 retirement.<br class="">
<br class="">
Let me suggest to separate Python out into another discussion.<br class="">
The pace of C/++ standards and that of Python versions are quite<br class="">
different and not easy to handle in a single RFC.<br class="">
<br class="">
Just my 0.02 cents,<br class="">
<br class="">
Markus<br class="">
</blockquote>
</div>
_______________________________________________<br class="">
grass-psc mailing list<br class="">
<a href="mailto:grass-psc@lists.osgeo.org" class="">grass-psc@lists.osgeo.org</a><br class="">
https://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!IGGdA3JGHwIvM70uQAxKgP-SoAnSPcupVWcVBGmLKhV4ocBAMqqxF8S2vhiwWU_OZbE7gBY$
<br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>