Shortening the Python release schedule
Shortening the Python release schedule
Posted May 23, 2018 22:30 UTC (Wed) by Cyberax (✭ supporter ✭, #52523)In reply to: Shortening the Python release schedule by jhoblitt
Parent article: Shortening the Python release schedule
Doesn't matter. As long as it's out there and easily enabled, people are going to depend on it.
It's far better to have two distinct states: "feature present" and "feature not present" rather than a plethora of "present", "present, but broken", "present, but incompatible with the next version".
Posted May 24, 2018 23:04 UTC (Thu)
by smurf (subscriber, #17840)
[Link]
Shortening the Python release schedule
You forget "feature present, but saddled with random pain points which require arcane workarounds, yet are set in stone for the next three releases".