[Python-Dev] Breaking undocumented API
fuzzyman at voidspace.org.uk
Mon Nov 8 19:46:39 CET 2010
> On Mon, Nov 8, 2010 at 1:39 PM, Michael Foord<fuzzyman at voidspace.org.uk> wrote:
>> So you have a bug in the module that can only be fixed in a function you
>> want to deprecate?
> No, I have a bug in a function that I want to deprecate. You said I
> don't need to fix it if I add a deprecation warning. However, as far
> as I know, deprecation warnings are not backported to maintenance
> branches while bug fixes are. So the specific question is: there is a
> bug in trace.find_strings() - should it be fixed in 3.1-maint?
My opinion would be:
* No we don't backport the deprecation warning
* No we don't need to fix the bug
Others may disagree. (Logic being that we won't fix the bug in 3.2, if
we fixed it in 2.7 then we would have to fix it in 3.2. Therefore we
shouldn't fix in 2.7.)
READ CAREFULLY. By accepting and reading this email you agree,
on behalf of your employer, to release me from all obligations
and waivers arising from any and all NON-NEGOTIATED agreements,
licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap,
confidentiality, non-disclosure, non-compete and acceptable use
policies (”BOGUS AGREEMENTS”) that I have entered into with your
employer, its partners, licensors, agents and assigns, in
perpetuity, without prejudice to my ongoing rights and privileges.
You further represent that you have the authority to release me
from any BOGUS AGREEMENTS on behalf of your employer.
More information about the Python-Dev