Mailman 3 June 2012 - Python-Dev

Re: [Python-Dev] cpython: Fix #14772: Return the destination from some shutil functions.
by Antoine Pitrou June 19, 2012

June 19, 2012

On Tue, 19 Jun 2012 01:41:44 +0200 brian.curtin <python-checkins(a)python.org> wrote: > http://hg.python.org/cpython/rev/8281233ec648 > changeset: 77514:8281233ec648 > user: Brian Curtin <brian(a)python.org> > date: Mon Jun 18 18:41:07 2012 -0500 > summary: > Fix #14772: Return the destination from some shutil functions. > > files: > Doc/library/shutil.rst | 14 ++++++--- > Lib/shutil.py | 13 +++++++-- > Lib/test/… [View More]

1 0

PEP 362: 4th edition
by Yury Selivanov June 19, 2012

June 19, 2012

Hello, The new revision of PEP 362 has been posted: http://www.python.org/dev/peps/pep-0362/ Summary: 1. Signature's 'is_args', 'is_kwargs', 'is_keyword_only' were all replaced with a single 'kind' attribute (Nick, I borrowed your description of 'kind' attribute and its possible values.) 2. 'signature()' checks for the '__wrapped__' attribute on all callables. 3. 'POSITIONAL_ONLY' parameters should be fully supported by 'bind()' and other Signature class methods. Open questions: 1. … [View More]Should we keep 'Parameter.implemented' or not. *Please vote* 2. Should 'Signature.format()' instead of 7 or so arguments accept just a SignatureFormatter class, that implements all the formatting logic, that is easy to override? All in all, I think that the PEP is almost ready for the acceptance. As 3.3 beta 1 is just a week away, I want to ask for BDFAP (Nick?) Please also do the patch review: http://bugs.python.org/issue15008 Thank you! PEP: 362 Title: Function Signature Object Version: $Revision$ Last-Modified: $Date$ Author: Brett Cannon <brett(a)python.org>, Jiwon Seo <seojiwon(a)gmail.com>, Yury Selivanov <yselivanov(a)sprymix.com>, Larry Hastings <larry(a)hastings.org> Status: Draft Type: Standards Track Content-Type: text/x-rst Created: 21-Aug-2006 Python-Version: 3.3 Post-History: 04-Jun-2012 Abstract ======== Python has always supported powerful introspection capabilities, including introspecting functions and methods (for the rest of this PEP, "function" refers to both functions and methods). By examining a function object you can fully reconstruct the function's signature. Unfortunately this information is stored in an inconvenient manner, and is spread across a half-dozen deeply nested attributes. This PEP proposes a new representation for function signatures. The new representation contains all necessary information about a function and its parameters, and makes introspection easy and straightforward. However, this object does not replace the existing function metadata, which is used by Python itself to execute those functions. The new metadata object is intended solely to make function introspection easier for Python programmers. Signature Object ================ A Signature object represents the call signature of a function and its return annotation. For each parameter accepted by the function it stores a `Parameter object`_ in its ``parameters`` collection. A Signature object has the following public attributes and methods: * return_annotation : object The annotation for the return type of the function if specified. If the function has no annotation for its return type, this attribute is not set. * parameters : OrderedDict An ordered mapping of parameters' names to the corresponding Parameter objects (keyword-only arguments are in the same order as listed in ``code.co_varnames``). * bind(\*args, \*\*kwargs) -> BoundArguments Creates a mapping from positional and keyword arguments to parameters. Raises a ``TypeError`` if the passed arguments do not match the signature. * bind_partial(\*args, \*\*kwargs) -> BoundArguments Works the same way as ``bind()``, but allows the omission of some required arguments (mimics ``functools.partial`` behavior.) Raises a ``TypeError`` if the passed arguments do not match the signature. * format(...) -> str Formats the Signature object to a string. Optional arguments allow for custom render functions for parameter names, annotations and default values, along with custom separators. Signature implements the ``__str__`` method, which fallbacks to the ``Signature.format()`` call. It's possible to test Signatures for equality. Two signatures are equal when they have equal parameters and return annotations. Changes to the Signature object, or to any of its data members, do not affect the function itself. Parameter Object ================ Python's expressive syntax means functions can accept many different kinds of parameters with many subtle semantic differences. We propose a rich Parameter object designed to represent any possible function parameter. The structure of the Parameter object is: * name : str The name of the parameter as a string. * default : object The default value for the parameter, if specified. If the parameter has no default value, this attribute is not set. * annotation : object The annotation for the parameter if specified. If the parameter has no annotation, this attribute is not set. * kind : str Describes how argument values are bound to the parameter. Possible values: * ``Parameter.POSITIONAL_ONLY`` - value must be supplied as a positional argument. Python has no explicit syntax for defining positional-only parameters, but many builtin and extension module functions (especially those that accept only one or two parameters) accept them. * ``Parameter.POSITIONAL_OR_KEYWORD`` - value may be supplied as either a keyword or positional argument (this is the standard binding behaviour for functions implemented in Python.) * ``Parameter.KEYWORD_ONLY`` - value must be supplied as a keyword argument. Keyword only parameters are those which appear after a "*" or "\*args" entry in a Python function definition. * ``Parameter.VAR_POSITIONAL`` - a tuple of positional arguments that aren't bound to any other parameter. This corresponds to a "\*args" parameter in a Python function definition. * ``Parameter.VAR_KEYWORD`` - a dict of keyword arguments that aren't bound to any other parameter. This corresponds to a "\*\*kwds" parameter in a Python function definition. * implemented : bool True if the parameter is implemented for use. Some platforms implement functions but can't support specific parameters (e.g. "mode" for ``os.mkdir``). Passing in an unimplemented parameter may result in the parameter being ignored, or in NotImplementedError being raised. It is intended that all conditions where ``implemented`` may be False be thoroughly documented. Two parameters are equal when all their attributes are equal. BoundArguments Object ===================== Result of a ``Signature.bind`` call. Holds the mapping of arguments to the function's parameters. Has the following public attributes: * arguments : OrderedDict An ordered, mutable mapping of parameters' names to arguments' values. Does not contain arguments' default values. * args : tuple Tuple of positional arguments values. Dynamically computed from the 'arguments' attribute. * kwargs : dict Dict of keyword arguments values. Dynamically computed from the 'arguments' attribute. The ``arguments`` attribute should be used in conjunction with ``Signature.parameters`` for any arguments processing purposes. ``args`` and ``kwargs`` properties can be used to invoke functions: :: def test(a, *, b): ... sig = signature(test) ba = sig.bind(10, b=20) test(*ba.args, **ba.kwargs) Implementation ============== The implementation adds a new function ``signature()`` to the ``inspect`` module. The function is the preferred way of getting a ``Signature`` for a callable object. The function implements the following algorithm: - If the object is not callable - raise a TypeError - If the object has a ``__signature__`` attribute and if it is not ``None`` - return a deepcopy of it - If it is ``None`` and the object is an instance of ``BuiltinFunction``, raise a ``ValueError`` - If it has a ``__wrapped__`` attribute, return ``signature(object.__wrapped__)`` - If the object is a an instance of ``FunctionType`` construct and return a new ``Signature`` for it - If the object is a method or a classmethod, construct and return a new ``Signature`` object, with its first parameter (usually ``self`` or ``cls``) removed - If the object is a staticmethod, construct and return a new ``Signature`` object - If the object is an instance of ``functools.partial``, construct a new ``Signature`` from its ``partial.func`` attribute, and account for already bound ``partial.args`` and ``partial.kwargs`` - If the object is a class or metaclass: - If the object's type has a ``__call__`` method defined in its MRO, return a Signature for it - If the object has a ``__new__`` method defined in its class, return a Signature object for it - If the object has a ``__init__`` method defined in its class, return a Signature object for it - Return ``signature(object.__call__)`` Note, that the ``Signature`` object is created in a lazy manner, and is not automatically cached. If, however, the Signature object was explicitly cached by the user, ``signature()`` returns a new deepcopy of it on each invocation. An implementation for Python 3.3 can be found at [#impl]_. The python issue tracking the patch is [#issue]_. Design Considerations ===================== No implicit caching of Signature objects ---------------------------------------- The first PEP design had a provision for implicit caching of ``Signature`` objects in the ``inspect.signature()`` function. However, this has the following downsides: * If the ``Signature`` object is cached then any changes to the function it describes will not be reflected in it. However, If the caching is needed, it can be always done manually and explicitly * It is better to reserve the ``__signature__`` attribute for the cases when there is a need to explicitly set to a ``Signature`` object that is different from the actual one Examples ======== Visualizing Callable Objects' Signature --------------------------------------- Let's define some classes and functions: :: from inspect import signature from functools import partial, wraps class FooMeta(type): def __new__(mcls, name, bases, dct, *, bar:bool=False): return super().__new__(mcls, name, bases, dct) def __init__(cls, name, bases, dct, **kwargs): return super().__init__(name, bases, dct) class Foo(metaclass=FooMeta): def __init__(self, spam:int=42): self.spam = spam def __call__(self, a, b, *, c) -> tuple: return a, b, c def shared_vars(*shared_args): """Decorator factory that defines shared variables that are passed to every invocation of the function""" def decorator(f): @wraps(f) def wrapper(*args, **kwds): full_args = shared_args + args return f(*full_args, **kwds) # Override signature sig = wrapper.__signature__ = signature(f) for __ in shared_args: sig.parameters.popitem(last=False) return wrapper return decorator @shared_vars({}) def example(_state, a, b, c): return _state, a, b, c def format_signature(obj): return str(signature(obj)) Now, in the python REPL: :: >>> format_signature(FooMeta) '(name, bases, dct, *, bar:bool=False)' >>> format_signature(Foo) '(spam:int=42)' >>> format_signature(Foo.__call__) '(self, a, b, *, c) -> tuple' >>> format_signature(Foo().__call__) '(a, b, *, c) -> tuple' >>> format_signature(partial(Foo().__call__, 1, c=3)) '(b, *, c=3) -> tuple' >>> format_signature(partial(partial(Foo().__call__, 1, c=3), 2, c=20)) '(*, c=20) -> tuple' >>> format_signature(example) '(a, b, c)' >>> format_signature(partial(example, 1, 2)) '(c)' >>> format_signature(partial(partial(example, 1, b=2), c=3)) '(b=2, c=3)' Annotation Checker ------------------ :: import inspect import functools def checktypes(func): '''Decorator to verify arguments and return types Example: >>> @checktypes ... def test(a:int, b:str) -> int: ... return int(a * b) >>> test(10, '1') 1111111111 >>> test(10, 1) Traceback (most recent call last): ... ValueError: foo: wrong type of 'b' argument, 'str' expected, got 'int' ''' sig = inspect.signature(func) types = {} for param in sig.parameters.values(): # Iterate through function's parameters and build the list of # arguments types try: type_ = param.annotation except AttributeError: continue else: if not inspect.isclass(type_): # Not a type, skip it continue types[param.name] = type_ # If the argument has a type specified, let's check that its # default value (if present) conforms with the type. try: default = param.default except AttributeError: continue else: if not isinstance(default, type_): raise ValueError("{func}: wrong type of a default value for {arg!r}". \ format(func=func.__qualname__, arg=param.name)) def check_type(sig, arg_name, arg_type, arg_value): # Internal function that encapsulates arguments type checking if not isinstance(arg_value, arg_type): raise ValueError("{func}: wrong type of {arg!r} argument, " \ "{exp!r} expected, got {got!r}". \ format(func=func.__qualname__, arg=arg_name, exp=arg_type.__name__, got=type(arg_value).__name__)) @functools.wraps(func) def wrapper(*args, **kwargs): # Let's bind the arguments ba = sig.bind(*args, **kwargs) for arg_name, arg in ba.arguments.items(): # And iterate through the bound arguments try: type_ = types[arg_name] except KeyError: continue else: # OK, we have a type for the argument, lets get the corresponding # parameter description from the signature object param = sig.parameters[arg_name] if param.kind == param.VAR_POSITIONAL: # If this parameter is a variable-argument parameter, # then we need to check each of its values for value in arg: check_type(sig, arg_name, type_, value) elif param.kind == param.VAR_KEYWORD: # If this parameter is a variable-keyword-argument parameter: for subname, value in arg.items(): check_type(sig, arg_name + ':' + subname, type_, value) else: # And, finally, if this parameter a regular one: check_type(sig, arg_name, type_, arg) result = func(*ba.args, **ba.kwargs) # The last bit - let's check that the result is correct try: return_type = sig.return_annotation except AttributeError: # Looks like we don't have any restriction on the return type pass else: if isinstance(return_type, type) and not isinstance(result, return_type): raise ValueError('{func}: wrong return type, {exp} expected, got {got}'. \ format(func=func.__qualname__, exp=return_type.__name__, got=type(result).__name__)) return result return wrapper Render Function Signature to HTML --------------------------------- :: import inspect def format_to_html(func): sig = inspect.signature(func) html = sig.format(token_params_separator=',', token_colon=':', token_eq='=', token_return_annotation='->', token_left_paren='(', token_right_paren=')', token_kwonly_separator='*', format_name=lambda name: ''+name+'') return '{}'.format(html) References ========== .. [#impl] pep362 branch (https://bitbucket.org/1st1/cpython/overview) .. [#issue] issue 15008 (http://bugs.python.org/issue15008) Copyright ========= This document has been placed in the public domain. .. Local Variables: mode: indented-text indent-tabs-mode: nil sentence-end-double-space: t fill-column: 70 coding: utf-8 End: [View Less]

16 43

CFFI released
by Armin Rigo June 19, 2012

June 19, 2012

Hi all, We (=fijal and myself) finally released the beta-0.1 version of CFFI. http://cffi.readthedocs.org/ It is a(nother) simple Foreign Function Interface for Python calling C code. I talked about it with a few python core people during the PyCon sprint; now it's done, with a pure Python part and a compact (but still 3000 lines) piece of C code. The goal is for it to be simple yet as complete as possible; it can be used in places where ctypes (say) is not applicable or only with platform-… [View More]

6 9

Re: [Python-Dev] dictnotes.txt out of date?
by Raymond Hettinger June 18, 2012

June 18, 2012

On Jun 13, 2012, at 10:35 AM, Eli Bendersky wrote: > Did you mean to send this to the list, Raymond? Yes. I wanted to find-out whether someone approved changing all the dict tunable parameters. I thought those weren't supposed to have changed. PEP 412 notes that the existing parameters were finely tuned and it did not make recommendations for changing them. At one point, I spent a full month testing all of the tunable parameters using dozens of popular Python applications. The … [View More]

8 15

Re: [Python-Dev] What's the best way to debug python3 source code? (for this bug: http://bugs.python.org/issue15068)
by gmspro June 18, 2012

June 18, 2012

@martin, I'm working on this bug, http://bugs.python.org/issue15068 I tried this with gdb (gdb)run >>>from sys import stdin >>>str=sys.stdin.read() blabla blabla blabla CTRL+D CTRL+D >>>CTRL+C (gdb)backtrace 0xb7f08348 in ___newselect_nocancel () at ../sysdeps/unix/syscall-template.S:82 82 ../sysdeps/unix/syscall-template.S: No such file or directory. in ../sysdeps/unix/syscall-template.S Current language: auto The current … [View More]source language is "auto; currently asm". (gdb) backtrace #0 0xb7f08348 in ___newselect_nocancel () at ../sysdeps/unix/syscall-template.S:82 #1 0xb7b43f9f in readline_until_enter_or_signal (prompt=0xb7b578d0 ">>> ", signal=0xbfffed54) at /home/user1/python/Python-3.2.3/Modules/readline.c:987 #2 0xb7b440ed in call_readline (sys_stdin=0xb7f84420, sys_stdout=0xb7f844c0, prompt=0xb7b578d0 ">>> ") at /home/user1/python/Python-3.2.3/Modules/readline.c:1082 #3 0x0811a15b in PyOS_Readline (sys_stdin=0xb7f84420, sys_stdout=0xb7f844c0, prompt=0xb7b578d0 ">>> ") at ../Parser/myreadline.c:200 #4 0x0811b92d in tok_nextc (tok=0x82e1d08) at ../Parser/tokenizer.c:897 #5 0x0811c39b in tok_get (tok=0x82e1d08, p_start=0xbfffef20, p_end=0xbfffef1c) at ../Parser/tokenizer.c:1306 #6 0x0811cda2 in PyTokenizer_Get (tok=0x82e1d08, p_start=0xbfffef20, p_end=0xbfffef1c) at ../Parser/tokenizer.c:1687 #7 0x08119866 in parsetok (tok=0x82e1d08, g=0x81df0c0, start=256, err_ret=0xbfffefd8, flags=0xbfffefd4) at ../Parser/parsetok.c:150 #8 0x081197a6 in PyParser_ParseFileFlagsEx (fp=0xb7f84420, filename=0x818ac7a "<stdin>", enc=0xb7c57750 "UTF-8", g= 0x81df0c0, start=256, ps1=0xb7b578d0 ">>> ", ps2=0xb7b578e8 "... ", err_ret=0xbfffefd8, flags=0xbfffefd4) at ../Parser/parsetok.c:100 #9 0x080cb96d in PyParser_ASTFromFile (fp=0xb7f84420, filename=0x818ac7a "<stdin>", enc=0xb7c57750 "UTF-8", start=256, ps1= 0xb7b578d0 ">>> ", ps2=0xb7b578e8 "... ", flags=0xbffff194, errcode=0xbffff044, arena=0x8285a50) at ../Python/pythonrun.c:1941 #10 0x080c9c9c in PyRun_InteractiveOneFlags (fp=0xb7f84420, filename=0x818ac7a "<stdin>", flags=0xbffff194) at ../Python/pythonrun.c:1175 #11 0x080c99ed in PyRun_InteractiveLoopFlags (fp=0xb7f84420, filename=0x818ac7a "<stdin>", flags=0xbffff194) at ../Python/pythonrun.c:1086 #12 0x080c98b5 in PyRun_AnyFileExFlags (fp=0xb7f84420, filename=0x818ac7a "<stdin>", closeit=0, flags=0xbffff194) at ../Python/pythonrun.c:1055 #13 0x080deb5c in run_file (fp=0xb7f84420, filename=0x0, p_cf=0xbffff194) at ../Modules/main.c:307 #14 0x080df5c0 in Py_Main (argc=1, argv=0x81f7008) at ../Modules/main.c:733 #15 0x0805c3d9 in main (argc=1, argv=0xbffff2f4) at ../Modules/python.c:63 But i can't get any clue which file to look at. Thanks [View Less]

3 2

3.3 beta in one week
by Georg Brandl June 18, 2012

June 18, 2012

Hi all, this is just a quick reminder that the feature freeze for 3.3 will start next weekend with the release of beta1. Since I won't be able to shift that date for short periods (the next possible date for me would be around July 16), I hope that everybody has planned ahead accordingly. Let me also say that it's great to see how 3.3 is shaping up; the team is doing very well and I want to thank everybody for pushing, but not rushing, awesome features :) cheers, Georg

4 3

What's the best way to debug python3 source code?
by gmspro June 18, 2012

June 18, 2012

Hi, What's the best way to debug python3 source code? To fix a bug i need to debug source code(C files). I use gdb to debug. But how can i get the exact file/point to fix the bug? How can i know quickly where the bug is? How can i run python>>> from gdb and giving input there how can i test and debug to fix a bug? Someone please explain/elaborate the process you use/do as usual with examples. Thanks.

3 2

Re: [Python-Dev] [Python-checkins] cpython: Improve an internal ipaddress test, add a comment explaining why treating
by Nadeem Vawda June 17, 2012

June 17, 2012

On Sun, Jun 17, 2012 at 8:33 AM, nick.coghlan <python-checkins(a)python.org> wrote: > + @property > + def version(self): > + msg = '%200s has no version specified' % (type(self),) > + raise NotImplementedError(msg) > + Shouldn't that be "%.200s", rather than "%200s"?

1 0

VS 11 Express is Metro only.
by Terry Reedy June 17, 2012

June 17, 2012

The free Visual Studio 11 Express for Windows 8 (still in beta) will produce both 32 and 64 bit binaries and allow multiple languages but will only produce Metro apps. For desktop apps, either the paid Visual Studio versions or the free 2010 Express releases are required. https://www.microsoft.com/visualstudio/11/en-us/products/express bottom of page. Will this inhibit someday moving to Visual Studio 11 Professional or would VS2010 Express or VC++2010 Express still work for hacking on … [View More]

11 14

Re: [Python-Dev] [Python-checkins] cpython: Elaborate that sizeof only accounts for the object itself.
by Eli Bendersky June 17, 2012

June 17, 2012

On Sun, Jun 17, 2012 at 11:42 AM, martin.v.loewis < python-checkins(a)python.org> wrote: > http://hg.python.org/cpython/rev/cddaf96c8149 > changeset: 77484:cddaf96c8149 > parent: 77482:1f6c23ed8218 > user: Martin v. Löwis <martin(a)v.loewis.de> > date: Sun Jun 17 10:40:16 2012 +0200 > summary: > Elaborate that sizeof only accounts for the object itself. > > files: > Doc/library/sys.rst | 3 +++ > 1 files changed, 3 insertions(… [View More]

1 0