Chris Angelico writes:
> 1) Keep deprecated APIs around for as long as you can, even if they're
> implemented messily on top of your current API.
>
> 2) Design your API with future-proofing in mind.
2.1) Have a generous deprecation schedule, and go to significant lengths
to ensure all developers
On Thu, Nov 21, 2013 at 11:02 AM, Chris Friesen
wrote:
> I'm pretty new to python, I'm trying to figure out how a python module is
> supposed to make non-backwards-compatible changes without blowing up the
> applications that use it.
First and foremost, the best way to break backward compatibilit
Chris Friesen writes:
> I'm pretty new to python, I'm trying to figure out how a python module
> is supposed to make non-backwards-compatible changes without blowing
> up the applications that use it.
The short answer is that Python doesn't have a library linker, so we do
it through co-operative
Hi,
I'm pretty new to python, I'm trying to figure out how a python module
is supposed to make non-backwards-compatible changes without blowing up
the applications that use it.
In the C world this is straightforward, an application is linked against
version X of the library, and if the libra
