Python port best-practice?

[Joshua Root]

On 2018-4-27 02:07 , Renee Otten wrote:
> 
>> On Apr 26, 2018, at 11:41 AM, Joshua Root <jmr at macports.org> wrote:
>>
>> On 2018-4-27 01:34 , Ryan Schmidt wrote:
>>>
>>> At this time, I probably wouldn't use older versions than 2.7 or 3.5. We have been phasing 3.3 and 3.4 modules out.
>>
>> Both 3.4 and 3.5 are in security fixes only mode. 3.3 is EOL. 2.6 is right out, of course.
> 
> Wouldn’t it make sense to have a policy so that Python ports (if working correctly) have the same subports - that would avoid breaking one port when (subjectively?) removing a subport from another. Just quickly looking at the current subports in the tree shows the following number of packages for the different py-?? subports: 11 (py25-), 387 (py-26), 1274 (py-27), 16 (py-31), 23 (py-32), 198 (py-33), 715 (py-34), 800 (py-35), 832 (py-36). 

Not all modules support the same python versions. Any time you remove
any port, you need to check for dependents. Python module ports are
depended on by more than just other python module ports.

- Josh