[Python-ideas] Making Python more enterprise technology

[Nick Coghlan]

Mark Summerfield wrote:
> One possible way would be to standardize one particular version, but not
> the next two minor releases. For example, standardize 3.2, but not 3.3
> or 3.4, then standardize 3.5, but not 3.6 or 3.7, and so on. This would
> mean that the standardization effort would take place about every four
> years (and which would only affect those involved in the standardization
> process). There would however, be a cost to the development community:
> maintaining the standardized version (e.g., bug & security fixes) until
> it is superceded.

Someone could always decide to standardise Python 2.7 ;)

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
---------------------------------------------------------------