[Python-Dev] Very Strange Argument Handling Behavior (original) (raw)
Michael Foord fuzzyman at voidspace.org.uk
Fri Apr 16 17:17:28 CEST 2010
- Previous message: [Python-Dev] Very Strange Argument Handling Behavior
- Next message: [Python-Dev] Very Strange Argument Handling Behavior
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 16/04/2010 17:06, Mark Dickinson wrote:
On Fri, Apr 16, 2010 at 3:57 PM, Antoine Pitrou<solipsis at pitrou.net> wrote:
Mark Dickinson<dickinsm gmail.com> writes:
Okay; I'll open an issue for deprecation in 3.2 and removal in 3.3.
Can this sneak in under the 'incorrect language semantics' exemption for PEP 3003 (the moratorium PEP)? If not, then deprecation presumably has to wait for 3.3. It seems that in spirit the moratorium applies more to language additions than to removals/limitations. The goal being that alternate implementation stop chasing a moving target in terms of features. So IMVHO it is fine for 3.2. Removing it certainly seems in keeping with the goal of making life easier for alternate implementations. (Out of curiosity, does anyone know what IronPython does here?)
Same as Jython and PyPy:
IronPython 2.6.1 (2.6.10920.0) on .NET 2.0.50727.4927 Type "help", "copyright", "credits" or "license" for more information.
dict(**{1: 'hi'}) Traceback (most recent call last): File "", line 1, in TypeError: expected string for dictionary argument got 1
Michael
I've opened http://bugs.python.org/issue8419
Mark
Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk
-- http://www.ironpythoninaction.com/
- Previous message: [Python-Dev] Very Strange Argument Handling Behavior
- Next message: [Python-Dev] Very Strange Argument Handling Behavior
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]