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

Showing content from https://mail.python.org/pipermail/python-dev/2007-March/072231.html below:

[Python-Dev] Breaking calls to object.__init__/__new__

• Previous message: [Python-Dev] Contents of test_bool
• Next message: [Python-Dev] Breaking calls to object.__init__/__new__
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

See python.org/sf/1683368. I'd like to invite opinions on whether it's
worth breaking an unknown amount of user code in 2.6 for the sake of
stricter argument checking for object.__init__ and object.__new__. I
think it probably isn't; but the strict version could be added to 3.0
and a warning issued in 2.6 in -Wpy3k mode. Alternatively, we could
introduce the stricter code in 2.6, fix the stdlib modules that it
breaks, and hope for the best. Opinions?

-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)

• Previous message: [Python-Dev] Contents of test_bool
• Next message: [Python-Dev] Breaking calls to object.__init__/__new__
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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