Message158541
| Author |
pitrou |
| Recipients |
brett.cannon, eric.snow, pitrou, r.david.murray |
| Date |
2012年04月17日.10:51:55 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1334659856.3338.12.camel@localhost.localdomain> |
| In-reply-to |
<1334610825.15.0.928567560303.issue14551@psf.upfronthosting.co.za> |
| Content |
> Well, I want backwards-compatibility *now*, not forever.
I don't think changing a function signature in an incompatible way is
generally acceptable. You might make one of the arguments optional,
though (but keeping the current semantics when the argument *is*
passed). If it's not possible, you can add another function with the
intended behaviour.
The importlib bootstrapping has already had some (unavoidable)
disruptive consequences. Let's keep them to a minimum. People *rely* on
our APIs, even the less popular ones. |
|