On 14.03.2022 19:34, Brett Cannon wrote: > Greg proposed something like "Code changes to support platforms beyond tier1 > or > tier2 may be rejected, broken, or removed from the CPython codebase without > notice if they cause a maintenance burden for tier1&2 or obstruct general > improvements." and drop the concept of tier 3. Does that work for you?
Almost :-) I don't understand the "without notice". I guess Greg meant "without deprecation process". Removal of support code should be discussed on a ticket and then listed in PEP 11 and mentioned in the NEWS file, as usual. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Experts (#1, Mar 14 2022) >>> Python Projects, Coaching and Support ... https://www.egenix.com/ >>> Python Product Development ... https://consulting.egenix.com/ ________________________________________________________________________ ::: We implement business ideas - efficiently in both time and costs ::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 https://www.egenix.com/company/contact/ https://www.malemburg.com/ _______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/STJAMJ45INJB2KDRMNDK6Y6REHZRAXTY/ Code of Conduct: https://www.python.org/psf/codeofconduct/