RetroSearch Browse

Tue Feb 10 12:25:18 EST 2004 · https://mail.python.org/pipermail/python-dev/2004-February/042484.html

From: "Guido van Rossum" <guido at python.org>
> 
> If in 3rd party code, that code is simply wrong.
> 
> If indeed such 3rd party code exists, and we expect we can't get it
> all fixed before 2.4 is released, the tracked_item hack can be used as
> a temporary measure to hunt down all those 3rd party extensions that
> break the abstraction.  I propose to issue a warning when it is
> discovered that ob_item != tracked_item.  Then in 2.5 we can remove
> the tracked_item feature.

There is a simpler way to make sure all clients that illicitly use
ob_item are updated appropriately: Break the build by renaming.  If
ob_item is renamed to ob_items or ob_item2 or whatever, any code that
uses the old name will cease to compile.

- Anders

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2004-February/042484.html below:

[Python-Dev] Optimization of the Year