[Python-Dev] Proposal to revert r54204 (splitext change)
bjourne at gmail.com
Thu Mar 15 00:01:21 CET 2007
On 3/14/07, Phillip J. Eby <pje at telecommunity.com> wrote:
> At 06:47 PM 3/14/2007 +0100, Martin v. Löwis wrote:
> >Phillip J. Eby schrieb:
> > > This backwards-incompatible change is therefore contrary to policy and
> > > should be reverted, pending a proper transition plan for the change
> > > (such as introduction of an alternative API and deprecation of the
> > > existing one.)
> >I'm clearly opposed to this proposal, or else I wouldn't have committed
> >the change in the first place.
> That much is obvious. But I haven't seen any explanation as to why
> explicitly-documented and explicitly-tested behavior should be treated as a
> bug in policy terms, just because people don't like the documented and
> tested behavior.
> So far, the only policy justification I've seen you give was along the
> lines of, "I volunteered to do it, so I get to decide".
I guess it maybe also had something to do with that the bug had been
left open on the bug tracker for almost two years and the persons
favoring the change had a 2:1 advantage (3:1 if you count the patch
contributor). There was plenty of time to voice your dissent. I also
think that which ever behavior splitext has, it does not matter much
in the grand scheme of things. There are bigger fishes to fry.
More information about the Python-Dev