This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

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 <>
> 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.
Date User Action Args
2012-04-17 10:51:56pitrousetrecipients: + pitrou, brett.cannon, r.david.murray, eric.snow
2012-04-17 10:51:55pitroulinkissue14551 messages
2012-04-17 10:51:55pitroucreate