Mailman 3 June 2012 - Python-Dev

Built-in sub modules
by Albert Zeyer 12 Jun '12

12 Jun '12

Hi, I just created some code to support built-in sub modules. The naive way I tried first was just to add {"Mod.Sub1.Sub2", init_modsub1sub2} to _PyImport_Inittab. This didn't worked. Maybe it would be a nice addition so that this works. Mod itself, in my case, was a package directory with pure Python code. Mod.Sub1 also. Only Mod.Sub1.Sub2 was some native code. Now, to make it work, I added {"Mod", init_modwrapper} to _PyImport_Inittab. init_modwrapper then first loads the package just in the way it would have been loaded before (I copied some code from Python/import.c). Then, in addition, it preloads Mod.Sub1 and call the native Mod.Sub1.Sub2 initialization (this also needs some _Py_PackageContext handling) and setups everything as needed. An example implementation is here: https://github.com/albertz/python-embedded/blob/master/pycryptoutils/crypto… https://github.com/albertz/python-embedded/blob/master/pyimportconfig.c Maybe this is useful for someone. I also searched a bit around and I didn't directly found any easier way to do this. Only a post from 2009 (http://mail.python.org/pipermail/cplusplus-sig/2009-January/014178.html) which seems like a much more ugly hack. Btw., my example implementation is part of another Python embedded project (https://github.com/albertz/python-embedded/). It builds a single static library with Python and PyCrypto - no external dependencies. So far, some basic test with RSA/AES works fine. Maybe that is also interesting to someone. Regards, Albert

3 2

Updated PEP 362 (Function Signature Object)
by Brett Cannon 11 Jun '12

11 Jun '12

On behalf of Yury, Larry, Jiwon (wherever he ended up), and myself, here is an updated version of PEP 362 to address Guido's earlier comments. Credit for most of the update should go to Yury with Larry also helping out. At this point I need a BDFAP and someone to do a code review: http://bugs.python.org/issue15008 . ----------------------------------------------- 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 overall signature of a function. It stores a `Parameter object`_ for each parameter accepted by the function, as well as information specific to the function itself. A Signature object has the following public attributes and methods: * name : str Name of the function. * qualname : str Fully qualified name of the function. * 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. Once a Signature object is created for a particular function, it's cached in the ``__signature__`` attribute of that function. 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. * is_keyword_only : bool True if the parameter is keyword-only, else False. * is_args : bool True if the parameter accepts variable number of arguments (``\*args``-like), else False. * is_kwargs : bool True if the parameter accepts variable number of keyword arguments (``\*\*kwargs``-like), else False. * is_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 ``is_implemented`` may be False be thoroughly documented. 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 should be used to invoke functions: :: def test(a, *, b): ... sig = signature(test) ba = sig.bind(10, b=20) test(*ba.args, **ba.kwargs) Implementation ============== An implementation for Python 3.3 can be found here: [#impl]_. A python issue was also created: [#issue]_. The implementation adds a new function ``signature()`` to the ``inspect`` module. ``signature()`` returns the value stored on the ``__signature__`` attribute if it exists, otherwise it creates the Signature object for the function and caches it in the function's ``__signature__``. (For methods this is stored directly in the ``__func__`` function object, since that is what decorators work with.) Examples ======== Function Signature Renderer --------------------------- :: def render_signature(signature): '''Renders function definition by its signature. Example: >>> def test(a:'foo', *, b:'bar', c=True, **kwargs:None) -> 'spam': ... pass >>> render_signature(inspect.signature(test)) test(a:'foo', *, b:'bar', c=True, **kwargs:None) -> 'spam' ''' result = [] render_kw_only_separator = True for param in signature.parameters.values(): formatted = param.name # Add annotation and default value if hasattr(param, 'annotation'): formatted = '{}:{!r}'.format(formatted, param.annotation) if hasattr(param, 'default'): formatted = '{}={!r}'.format(formatted, param.default) # Handle *args and **kwargs -like parameters if param.is_args: formatted = '*' + formatted elif param.is_kwargs: formatted = '**' + formatted if param.is_args: # OK, we have an '*args'-like parameter, so we won't need # a '*' to separate keyword-only arguments render_kw_only_separator = False elif param.is_keyword_only and render_kw_only_separator: # We have a keyword-only parameter to render and we haven't # rendered an '*args'-like parameter before, so add a '*' # separator to the parameters list ("foo(arg1, *, arg2)" case) result.append('*') # This condition should be only triggered once, so # reset the flag render_kw_only_separator = False result.append(formatted) rendered = '{}({})'.format(signature.name, ', '.join(result)) if hasattr(signature, 'return_annotation'): rendered += ' -> {!r}'.format(signature.return_annotation) return rendered 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=sig.qualname, arg= param.name)) def check_type(sig, arg_name, arg_type, arg_value): # Internal function that incapsulates 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=sig.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.is_args: # 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.is_kwargs: # 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=sig.qualname, exp=return_type.__name__, got=type(result).__name__)) return result return wrapper Open Issues =========== When to construct the Signature object? --------------------------------------- The Signature object can either be created in an eager or lazy fashion. In the eager situation, the object can be created during creation of the function object. In the lazy situation, one would pass a function object to a function and that would generate the Signature object and store it to ``__signature__`` if needed, and then return the value of ``__signature__``. In the current implementation, signatures are created only on demand ("lazy"). Deprecate ``inspect.getfullargspec()`` and ``inspect.getcallargs()``? --------------------------------------------------------------------- Since the Signature object replicates the use of ``getfullargspec()`` and ``getcallargs()`` from the ``inspect`` module it might make sense to begin deprecating them in 3.3. 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:

15 67

Re: [Python-Dev] [Python-checkins] cpython: Note that the _asdict() method is outdated
by Nick Coghlan 10 Jun '12

10 Jun '12

On Sun, Jun 10, 2012 at 12:15 PM, raymond.hettinger <python-checkins(a)python.org> wrote: > http://hg.python.org/cpython/rev/fecbcd5c3978 > changeset: 77397:fecbcd5c3978 > user: Raymond Hettinger <python(a)rcn.com> > date: Sat Jun 09 19:15:26 2012 -0700 > summary: > Note that the _asdict() method is outdated This checkin changed a lot of the indentation in the collections docs. Did you mean to do that? Cheers, Nick. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

1 0

PEP 362 Second Revision
by Yury Selivanov 09 Jun '12

09 Jun '12

Hello, The new revision of PEP 362 has been posted: http://www.python.org/dev/peps/pep-0362/ Thanks to Brett, Larry, Nick, and everybody else on python-dev for your corrections/suggestions. Summary of changes: 1. We don't cache signatures in __signature__ attribute implicitly 2. signature() function is now more complex, but supports methods, partial objects, classes, callables, and decorated functions 3. Signatures are always constructed on demand 4. Dropped the deprecation section The implementation is not aligned with the latest PEP yet, I'll try to update it tonight. Thanks, - Yury

4 7

VS 2012 Express will support desktop apps
by Christian Heimes 09 Jun '12

09 Jun '12

Good news everybody! Microsoft has announced that the free VS 2012 Express Edition (aka VS11) will support desktop and console apps, too. Formerly only Metro apps were supported by the free edition. http://blogs.msdn.com/b/visualstudio/archive/2012/06/08/visual-studio-expre… Christian

1 0

Re: [Python-Dev] Import semantics?
by Ethan Furman 08 Jun '12

08 Jun '12

Dan Stromberg wrote: > On Fri, Jun 8, 2012 at 3:16 PM, Ethan Furman wrote: > Dan Stromberg wrote: >> Did the import semantics change in cpython 3.3a4? >> >> I used to be able to import treap.py even though I had a treap >> directory in my cwd. With 3.3a4, I have to rename the treap >> directory to see treap.py. > > Check out PEP 420 -- Implicit Namespace Packages > [http://www.python.org/dev/peps/pep-0420/] > > > Am I misinterpreting this? It seems like according to the PEP, I should > have still been able to import treap.py despite having a treap/. But I > couldn't; I had to rename treap/ to treap-dir/ first. > > During import processing, the import machinery will continue to iterate > over each directory in the parent path as it does in Python 3.2. While > looking for a module or package named "foo", for each directory in the > parent path: > > * If <directory>/foo/__init__.py is found, a regular package is > imported and returned. > * If not, but <directory>/foo.{py,pyc,so,pyd} is found, a module > is imported and returned. The exact list of extension varies > by platform and whether the -O flag is specified. The list > here is representative. > * If not, but <directory>/foo is found and is a directory, it is > recorded and the scan continues with the next directory in the > parent path. > * Otherwise the scan continues with the next directory in the > parent path. I do not understand PEP 420 well enough to say if this is intentional or a bug -- thoughts? ~Ethan~

2 1

Re: [Python-Dev] [Python-checkins] cpython (3.2): #14957: clarify splitlines docs.
by Nick Coghlan 08 Jun '12

08 Jun '12

On Jun 2, 2012 6:21 AM, "r.david.murray" <python-checkins(a)python.org> wrote: > > http://hg.python.org/cpython/rev/24572015e24f > changeset: 77288:24572015e24f > branch: 3.2 > parent: 77285:bf6305bce3af > user: R David Murray <rdmurray(a)bitdance.com> > date: Fri Jun 01 16:19:36 2012 -0400 > summary: > #14957: clarify splitlines docs. > > Initial patch by Michael Driscoll, I added the example. > > files: > Doc/library/stdtypes.rst | 8 +++++++- > 1 files changed, 7 insertions(+), 1 deletions(-) > > > diff --git a/Doc/library/stdtypes.rst b/Doc/library/stdtypes.rst > --- a/Doc/library/stdtypes.rst > +++ b/Doc/library/stdtypes.rst > @@ -1329,7 +1329,13 @@ > > Return a list of the lines in the string, breaking at line boundaries. Line > breaks are not included in the resulting list unless *keepends* is given and > - true. > + true. This method uses the universal newlines approach to splitting lines. > + Unlike :meth:`~str.split`, if the string ends with line boundary characters > + the returned list does ``not`` have an empty last element. > + > + For example, ``'ab c\n\nde fg\rkl\r\n'.splitlines()`` returns > + ``['ab c', '', 'de fg', 'kl']``, while the same call with ``splinelines(True)`` > + returns ``['ab c\n', '\n, 'de fg\r', 'kl\r\n']``. s/splinelines/splitlines/ Maybe also show what split() would do for that string? > > > .. method:: str.startswith(prefix[, start[, end]]) > > -- > Repository URL: http://hg.python.org/cpython > > _______________________________________________ > Python-checkins mailing list > Python-checkins(a)python.org > http://mail.python.org/mailman/listinfo/python-checkins >

5 7

Summary of Python tracker Issues
by Python tracker 08 Jun '12

08 Jun '12

ACTIVITY SUMMARY (2012-06-01 - 2012-06-08) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 3460 (+10) closed 23354 (+46) total 26814 (+56) Open issues with patches: 1460 Issues opened (44) ================== #12988: Tkinter File Dialog crashes on Win7 when saving to Documents L http://bugs.python.org/issue12988 reopened by serwy #14502: Document better what happens on releasing an unacquired lock http://bugs.python.org/issue14502 reopened by petri.lehtinen #14982: pkgutil.walk_packages seems to not work properly on Python 3.3 http://bugs.python.org/issue14982 opened by Marc.Abramowitz #14983: email.generator should always add newlines after closing bound http://bugs.python.org/issue14983 opened by mitya57 #14984: netrc module allows read of non-secured .netrc file http://bugs.python.org/issue14984 opened by bruno.Piguet #14988: _elementtree: Raise ImportError when importing of pyexpat fail http://bugs.python.org/issue14988 opened by Arfrever #14990: detect_encoding should fail with SyntaxError on invalid encodi http://bugs.python.org/issue14990 opened by flox #14991: Option for regex groupdict() to show only matching names http://bugs.python.org/issue14991 opened by rhettinger #14995: PyLong_FromString documentation should state that the string m http://bugs.python.org/issue14995 opened by rfk #14997: IDLE tries to run shell window if line is completed with F5 ra http://bugs.python.org/issue14997 opened by cuulblu #14998: pprint._safe_key is not always safe enough http://bugs.python.org/issue14998 opened by Shawn.Brown #14999: ctypes ArgumentError lists arguments from 1, not 0 http://bugs.python.org/issue14999 opened by perey #15001: segmentation fault with del sys.module['__main__'] http://bugs.python.org/issue15001 opened by amaury.forgeotdarc #15002: urllib2 does not download 4 MB file completely using ftp http://bugs.python.org/issue15002 opened by sspapilin #15003: make PyNamespace_New() public http://bugs.python.org/issue15003 opened by eric.snow #15004: add weakref support to types.SimpleNamespace http://bugs.python.org/issue15004 opened by eric.snow #15005: trace corrupts return result on chained execution http://bugs.python.org/issue15005 opened by techtonik #15006: Allow equality comparison between naive and aware datetime obj http://bugs.python.org/issue15006 opened by belopolsky #15007: Unittest CLI does not support test packages very well http://bugs.python.org/issue15007 opened by r.david.murray #15008: PEP 362 "Signature Objects" reference implementation http://bugs.python.org/issue15008 opened by Yury.Selivanov #15009: urlsplit can't round-trip relative-host urls. http://bugs.python.org/issue15009 opened by Buck.Golemon #15010: unittest: _top_level_dir is incorrectly persisted between call http://bugs.python.org/issue15010 opened by r.david.murray #15011: Change Scripts to bin on Windows http://bugs.python.org/issue15011 opened by brian.curtin #15013: smtplib: add low-level APIs to doc? http://bugs.python.org/issue15013 opened by sandro.tosi #15014: smtplib: add support for arbitrary auth methods http://bugs.python.org/issue15014 opened by sandro.tosi #15015: Access to non-existing "future" attribute in error path of fut http://bugs.python.org/issue15015 opened by pieleric #15016: Add special case for latin messages in email.mime.text http://bugs.python.org/issue15016 opened by mitya57 #15018: Incomplete Python LDFLAGS and CPPFLAGS used for extension modu http://bugs.python.org/issue15018 opened by marcusva #15019: Sting termination on Linux http://bugs.python.org/issue15019 opened by jjanis #15020: Poor default value for progname http://bugs.python.org/issue15020 opened by Joshua.Cogliati #15021: xmlrpc server hangs http://bugs.python.org/issue15021 opened by Abhishek.Singh #15022: types.SimpleNamespace needs to be picklable http://bugs.python.org/issue15022 opened by eric.snow #15025: httplib and http.client are missing response messages for defi http://bugs.python.org/issue15025 opened by craigloftus #15026: Faster UTF-16 encoding http://bugs.python.org/issue15026 opened by storchaka #15027: Faster UTF-32 encoding http://bugs.python.org/issue15027 opened by storchaka #15028: PySys_SetArgv escapes quotes in argv[] http://bugs.python.org/issue15028 opened by RMBianchi #15029: Update Defining New Types chapter according to PEP 253 http://bugs.python.org/issue15029 opened by mloskot #15030: PyPycLoader can't read cached .pyc files http://bugs.python.org/issue15030 opened by Ronan.Lamy #15031: Split .pyc parsing from module loading http://bugs.python.org/issue15031 opened by Ronan.Lamy #15032: Provide a select.select implemented using select.poll http://bugs.python.org/issue15032 opened by gregory.p.smith #15033: Different exit status when using -m http://bugs.python.org/issue15033 opened by kisielk #15034: tutorial should use best practices in user defined execeptions http://bugs.python.org/issue15034 opened by r.david.murray #15035: array.array of UCS2 values http://bugs.python.org/issue15035 opened by ronaldoussoren #15036: mailbox.mbox fails to pop two items in a row, flushing in betw http://bugs.python.org/issue15036 opened by petri.lehtinen Most recent 15 issues with no replies (15) ========================================== #15034: tutorial should use best practices in user defined execeptions http://bugs.python.org/issue15034 #15033: Different exit status when using -m http://bugs.python.org/issue15033 #15032: Provide a select.select implemented using select.poll http://bugs.python.org/issue15032 #15027: Faster UTF-32 encoding http://bugs.python.org/issue15027 #15026: Faster UTF-16 encoding http://bugs.python.org/issue15026 #15025: httplib and http.client are missing response messages for defi http://bugs.python.org/issue15025 #15018: Incomplete Python LDFLAGS and CPPFLAGS used for extension modu http://bugs.python.org/issue15018 #15015: Access to non-existing "future" attribute in error path of fut http://bugs.python.org/issue15015 #15010: unittest: _top_level_dir is incorrectly persisted between call http://bugs.python.org/issue15010 #14999: ctypes ArgumentError lists arguments from 1, not 0 http://bugs.python.org/issue14999 #14995: PyLong_FromString documentation should state that the string m http://bugs.python.org/issue14995 #14991: Option for regex groupdict() to show only matching names http://bugs.python.org/issue14991 #14988: _elementtree: Raise ImportError when importing of pyexpat fail http://bugs.python.org/issue14988 #14978: distutils Extension fails to be created with unicode package n http://bugs.python.org/issue14978 #14966: Fully document subprocess.CalledProcessError http://bugs.python.org/issue14966 Most recent 15 issues waiting for review (15) ============================================= #15031: Split .pyc parsing from module loading http://bugs.python.org/issue15031 #15030: PyPycLoader can't read cached .pyc files http://bugs.python.org/issue15030 #15027: Faster UTF-32 encoding http://bugs.python.org/issue15027 #15026: Faster UTF-16 encoding http://bugs.python.org/issue15026 #15022: types.SimpleNamespace needs to be picklable http://bugs.python.org/issue15022 #15016: Add special case for latin messages in email.mime.text http://bugs.python.org/issue15016 #15015: Access to non-existing "future" attribute in error path of fut http://bugs.python.org/issue15015 #15011: Change Scripts to bin on Windows http://bugs.python.org/issue15011 #15008: PEP 362 "Signature Objects" reference implementation http://bugs.python.org/issue15008 #15006: Allow equality comparison between naive and aware datetime obj http://bugs.python.org/issue15006 #15004: add weakref support to types.SimpleNamespace http://bugs.python.org/issue15004 #15003: make PyNamespace_New() public http://bugs.python.org/issue15003 #15001: segmentation fault with del sys.module['__main__'] http://bugs.python.org/issue15001 #14998: pprint._safe_key is not always safe enough http://bugs.python.org/issue14998 #14997: IDLE tries to run shell window if line is completed with F5 ra http://bugs.python.org/issue14997 Top 10 most discussed issues (10) ================================= #14814: Implement PEP 3144 (the ipaddress module) http://bugs.python.org/issue14814 14 msgs #14908: datetime.datetime should have a timestamp() method http://bugs.python.org/issue14908 13 msgs #12510: IDLE: calltips mishandle raw strings and other examples http://bugs.python.org/issue12510 12 msgs #14982: pkgutil.walk_packages seems to not work properly on Python 3.3 http://bugs.python.org/issue14982 11 msgs #7559: TestLoader.loadTestsFromName swallows import errors http://bugs.python.org/issue7559 9 msgs #15005: trace corrupts return result on chained execution http://bugs.python.org/issue15005 8 msgs #6721: Locks in python standard library should be sanitized on fork http://bugs.python.org/issue6721 7 msgs #14983: email.generator should always add newlines after closing bound http://bugs.python.org/issue14983 7 msgs #15003: make PyNamespace_New() public http://bugs.python.org/issue15003 7 msgs #14997: IDLE tries to run shell window if line is completed with F5 ra http://bugs.python.org/issue14997 6 msgs Issues closed (41) ================== #1079: decode_header does not follow RFC 2047 http://bugs.python.org/issue1079 closed by r.david.murray #2658: decode_header() fails on multiline headers http://bugs.python.org/issue2658 closed by r.david.murray #6203: locale documentation doesn't mention that LC_CTYPE is changed http://bugs.python.org/issue6203 closed by python-dev #6745: (curses) addstr() takes str in Python 3 http://bugs.python.org/issue6745 closed by haypo #8652: Minor improvements to the "Handling Exceptions" part of the tu http://bugs.python.org/issue8652 closed by r.david.murray #8902: add datetime.time.now() for consistency http://bugs.python.org/issue8902 closed by belopolsky #9967: encoded_word regular expression in email.header.decode_header( http://bugs.python.org/issue9967 closed by r.david.murray #10365: IDLE Crashes on File Open Dialog when code window closed befor http://bugs.python.org/issue10365 closed by terry.reedy #10574: email.header.decode_header fails if the string contains multip http://bugs.python.org/issue10574 closed by r.david.murray #11022: locale.getpreferredencoding() must not set temporary LC_CTYPE http://bugs.python.org/issue11022 closed by python-dev #11823: disassembly needs argument counts on calls with keyword args http://bugs.python.org/issue11823 closed by belopolsky #12157: join method of multiprocessing Pool object hangs if iterable a http://bugs.python.org/issue12157 closed by sbt #13854: multiprocessing: SystemExit from child with non-int, non-str a http://bugs.python.org/issue13854 closed by sbt #14006: Improve the documentation of xml.etree.ElementTree http://bugs.python.org/issue14006 closed by eli.bendersky #14078: Add 'sourceline' property to xml.etree Elements http://bugs.python.org/issue14078 closed by eli.bendersky #14424: document PyType_GenericAlloc http://bugs.python.org/issue14424 closed by eli.bendersky #14627: Fatal Python Error when Python startup is interrupted by CTRL+ http://bugs.python.org/issue14627 closed by haypo #14673: add sys.implementation http://bugs.python.org/issue14673 closed by loewis #14711: Remove os.stat_float_times http://bugs.python.org/issue14711 closed by haypo #14712: Integrate PEP 405 http://bugs.python.org/issue14712 closed by vinay.sajip #14852: json and ElementTree parsers misbehave on streams containing m http://bugs.python.org/issue14852 closed by eli.bendersky #14907: SSL module cannot handle unicode filenames http://bugs.python.org/issue14907 closed by loewis #14918: Incorrect TypeError message for wrong function arguments http://bugs.python.org/issue14918 closed by r.david.murray #14926: random.seed docstring needs edit of "*a *is" http://bugs.python.org/issue14926 closed by sandro.tosi #14937: IDLE's deficiency in the completion of file names (Python 32, http://bugs.python.org/issue14937 closed by loewis #14957: Improve docs for str.splitlines http://bugs.python.org/issue14957 closed by r.david.murray #14981: 3.3.0a4 compilation fails von MacOS Lion /10.7.4 http://bugs.python.org/issue14981 closed by hynek #14985: os.path.isfile and os.path.isdir inconsistent on OSX Lion http://bugs.python.org/issue14985 closed by hynek #14986: print() fails on latin1 characters on OSX http://bugs.python.org/issue14986 closed by hynek #14987: inspect missing warnings import http://bugs.python.org/issue14987 closed by brett.cannon #14989: http.server option to run CGIHTTPRequestHandler http://bugs.python.org/issue14989 closed by r.david.murray #14992: os.makedirs expect_ok=True test_os failure when directory has http://bugs.python.org/issue14992 closed by gregory.p.smith #14993: GCC error when using unicodeobject.h http://bugs.python.org/issue14993 closed by haypo #14994: GCC error when using pyerrors.h http://bugs.python.org/issue14994 closed by python-dev #14996: IDLE 3.2.3 crashes saving a .py file to certain folders on Win http://bugs.python.org/issue14996 closed by terry.reedy #15000: _posixsubprocess module broken on x32 http://bugs.python.org/issue15000 closed by gregory.p.smith #15012: test issue http://bugs.python.org/issue15012 closed by brian.curtin #15017: threading.Lock documentation conflict http://bugs.python.org/issue15017 closed by r.david.murray #15023: listextend (and therefore list.extend and list.__init__) peek http://bugs.python.org/issue15023 closed by r.david.murray #15024: Split enhanced assertion support out as a unittest.TestCase ba http://bugs.python.org/issue15024 closed by ncoghlan #1467619: Header.decode_header eats up spaces http://bugs.python.org/issue1467619 closed by r.david.murray

1 0

PyPy 1.9 - Yard Wolf
by Maciej Fijalkowski 08 Jun '12

08 Jun '12

==================== PyPy 1.9 - Yard Wolf ==================== We're pleased to announce the 1.9 release of PyPy. This release brings mostly bugfixes, performance improvements, other small improvements and overall progress on the `numpypy`_ effort. It also brings an improved situation on Windows and OS X. You can download the PyPy 1.9 release here: http://pypy.org/download.html .. _`numpypy`: http://pypy.org/numpydonate.html What is PyPy? ============= PyPy is a very compliant Python interpreter, almost a drop-in replacement for CPython 2.7. It's fast (`pypy 1.9 and cpython 2.7.2`_ performance comparison) due to its integrated tracing JIT compiler. This release supports x86 machines running Linux 32/64, Mac OS X 64 or Windows 32. Windows 64 work is still stalling, we would welcome a volunteer to handle that. .. _`pypy 1.9 and cpython 2.7.2`: http://speed.pypy.org Thanks to our donors ==================== But first of all, we would like to say thank you to all people who donated some money to one of our four calls: * `NumPy in PyPy`_ (got so far $44502 out of $60000, 74%) * `Py3k (Python 3)`_ (got so far $43563 out of $105000, 41%) * `Software Transactional Memory`_ (got so far $21791 of $50400, 43%) * as well as our general PyPy pot. Thank you all for proving that it is indeed possible for a small team of programmers to get funded like that, at least for some time. We want to include this thank you in the present release announcement even though most of the work is not finished yet. More precisely, neither Py3k nor STM are ready to make it in an official release yet: people interested in them need to grab and (attempt to) translate PyPy from the corresponding branches (respectively ``py3k`` and ``stm-thread``). .. _`NumPy in PyPy`: http://pypy.org/numpydonate.html .. _`Py3k (Python 3)`: http://pypy.org/py3donate.html .. _`Software Transactional Memory`: http://pypy.org/tmdonate.html Highlights ========== * This release still implements Python 2.7.2. * Many bugs were corrected for Windows 32 bit. This includes new functionality to test the validity of file descriptors; and correct handling of the calling convensions for ctypes. (Still not much progress on Win64.) A lot of work on this has been done by Matti Picus and Amaury Forgeot d'Arc. * Improvements in ``cpyext``, our emulator for CPython C extension modules. For example PyOpenSSL should now work. We thank various people for help. * Sets now have strategies just like dictionaries. This means for example that a set containing only ints will be more compact (and faster). * A lot of progress on various aspects of ``numpypy``. See the `numpy-status`_ page for the automatic report. * It is now possible to create and manipulate C-like structures using the PyPy-only ``_ffi`` module. The advantage over using e.g. ``ctypes`` is that ``_ffi`` is very JIT-friendly, and getting/setting of fields is translated to few assembler instructions by the JIT. However, this is mostly intended as a low-level backend to be used by more user-friendly FFI packages, and the API might change in the future. Use it at your own risk. * The non-x86 backends for the JIT are progressing but are still not merged (ARMv7 and PPC64). * JIT hooks for inspecting the created assembler code have been improved. See `JIT hooks documentation`_ for details. * ``select.kqueue`` has been added (BSD). * Handling of keyword arguments has been drastically improved in the best-case scenario: proxy functions which simply forwards ``*args`` and ``**kwargs`` to another function now performs much better with the JIT. * List comprehension has been improved. .. _`numpy-status`: http://buildbot.pypy.org/numpy-status/latest.html .. _`JIT hooks documentation`: http://doc.pypy.org/en/latest/jit-hooks.html JitViewer ========= There will be a corresponding 1.9 release of JitViewer which is guaranteed to work with PyPy 1.9. See the `JitViewer docs`_ for details. .. _`JitViewer docs`: http://bitbucket.org/pypy/jitviewer Cheers, The PyPy Team

1 0

Re: [Python-Dev] [Python-checkins] cpython (3.2): Nudge readers towards a more accurate mental model for loop else clauses
by Terry Reedy 08 Jun '12

08 Jun '12

On 6/7/2012 8:42 AM, nick.coghlan wrote: > http://hg.python.org/cpython/rev/6e4ec47fba6a > changeset: 77369:6e4ec47fba6a > branch: 3.2 > parent: 77363:aa9cfeea07ad > user: Nick Coghlan<ncoghlan(a)gmail.com> > date: Thu Jun 07 22:41:34 2012 +1000 > summary: > Nudge readers towards a more accurate mental model for loop else clauses > > files: > Doc/tutorial/controlflow.rst | 7 +++++++ > 1 files changed, 7 insertions(+), 0 deletions(-) > > > diff --git a/Doc/tutorial/controlflow.rst b/Doc/tutorial/controlflow.rst > --- a/Doc/tutorial/controlflow.rst > +++ b/Doc/tutorial/controlflow.rst > @@ -187,6 +187,13 @@ > (Yes, this is the correct code. Look closely: the ``else`` clause belongs to > the :keyword:`for` loop, **not** the :keyword:`if` statement.) > > +When used with a loop, the ``else`` clause has more in common with the > +``else`` clause of a :keyword:`try` statement than it does that of > +:keyword:`if` statements: a :keyword:`try` statement's ``else`` clause runs > +when no exception occurs, (And there no return. But that is true of of every statement.) I think the above is wrong. I claim that try-statement else: is essentially identical to if-statement else:. The try-statement else: clause is subordinate to the except: clauses, not the try: part itself. It must follow at least one except condition just as an if-statement must follow at least one if condition. So it is really an except else, not a try else. Furthermore, 'except SomeError' is an abbreviation for 'if/elif SomeError was raised since the corresponding try' and more particularly 'if/elif isinstance(__exception__, SomeError). I use __exception__ here as the equivalent of C's errno, except that it is hidden. (If it were not hidden, we would not need 'as e', and indeed, we would not really need 'except' either.) The else clause runs when all the implied conditionals of the excepts are false. Just as an if-statement else clause runs when all the explicit conditionals of the if/elifs are false. The real contrast is between if/except else and loop else. The latter is subordinate to exactly one condition instead of possibly many, but that one condition may be evaluated multiple times instead of just once. It is the latter fact that seems to confuse people. > and a loop's ``else`` clause runs when no ``break`` occurs. As I explained on Python-ideas, the else clause runs when the loop condition is false. Period. This sentence is an incomplete equivalent to 'the loop condition is false'. The else clause runs when no 'break', no 'return', no 'raise' (explicit or implicit), AND no infinite loop occurs. I think your addition should be reverted. Here is a possible alternative if you think something more is needed. "An else clause used with a loop has two differences from an else clause used with an if statement. It is subordinate to just one condition instead of possibly many. (In for statements, the condition is implicit but still there.) That one condition is tested repeatedly instead of just once. A loop else is the same in that it triggers when that one condition is false." --- Terry Jan Reedy

3 2