Issues representing Python version 3.10 in portfiles

[Blair Zajac]

Maybe we should have a policy in putting periods in our version numbers? This seems to occur with some frequency, e.g. clang and llvm ports also.

> On Oct 19, 2020, at 12:10 PM, Christopher Chavez <chrischavez at gmx.us> wrote:
> 
> So far the versions for Python have been able to compact into two-digit strings: e.g. 36 37 38 39. Is the compacted version number for next year's Python 3.10 going to be "310"?
> 
> If so, there is code in portfiles which requires adjustment. Common example:
> 
> set pbranch [string range ${pver} 0 end-1].[string index ${pver} end]
> 
> assumes ${pver} is two-digit; setting ${pver} to "310" causes ${pbranch} to be set to "31.0" rather than "3.10". (I'd much prefer the inverse approach of setting ${pbranch} first, then doing `set pver [join [split ${pbranch} "."] ""]`.)
> 
> Maybe this convention followed Van Rossum's expectation long ago that Python would go directly from 3.9 to 4.0.
> 
> 
> Christopher A. Chavez
>