A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2010-November/105577.html below:

[Python-Dev] Removal of Win32 ANSI API

[Python-Dev] Removal of Win32 ANSI API [Python-Dev] Removal of Win32 ANSI APIAntoine Pitrou solipsis at pitrou.net
Sun Nov 14 01:19:28 CET 2010
On Sun, 14 Nov 2010 01:06:55 +0100
Victor Stinner <victor.stinner at haypocalc.com> wrote:
> 
> The code is currently working. The question is if we have to drop the ANSI API 
> now, later or never.

If the code is currently working and isn't a security hole, then we
obviously don't "have to".
Apparently several developers "want to", which is different.

> It looks like the decision moves to "later" (deprecate in 
> 3.2, remove in 3.3). I still think that drop now doesn't really hurt.

If you drop code without first deprecating it, chances are it will
hurt someone.  That's why having a deprecation period is the rule we
usually follow (most of the time :-)).

Regards

Antoine.


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4