Mailman 3 August 2012 - Python-Dev

Sphinx issue in What's New in Python 3.3 doc

by Victor Stinner

Hi, In the first example of the "PEP 409: Suppressing exception context" section, I read "from None...". http://docs.python.org/dev/whatsnew/3.3.html#pep-409-suppressing-exception-… It's confusing because I don't remember what was the last choice for the PEP: None or ... :-) The reST "code" looks correct in Doc/whatsnew/3.3.rst: ... raise AttributeError(attr) from None ... Victor

7 years, 4 months

2
1
0 0

[RELEASED] Python 3.3.0 release candidate 1

by Georg Brandl

On behalf of the Python development team, I'm delighted to announce the first release candidate of Python 3.3.0. This is a preview release, and its use is not recommended in production settings. Python 3.3 includes a range of improvements of the 3.x series, as well as easier porting between 2.x and 3.x. Major new features and changes in the 3.3 release series are: * PEP 380, syntax for delegating to a subgenerator ("yield from") * PEP 393, flexible string representation (doing away with the distinction between "wide" and "narrow" Unicode builds) * A C implementation of the "decimal" module, with up to 80x speedup for decimal-heavy applications * The import system (__import__) now based on importlib by default * The new "lzma" module with LZMA/XZ support * PEP 397, a Python launcher for Windows * PEP 405, virtual environment support in core * PEP 420, namespace package support * PEP 3151, reworking the OS and IO exception hierarchy * PEP 3155, qualified name for classes and functions * PEP 409, suppressing exception context * PEP 414, explicit Unicode literals to help with porting * PEP 418, extended platform-independent clocks in the "time" module * PEP 412, a new key-sharing dictionary implementation that significantly saves memory for object-oriented code * PEP 362, the function-signature object * The new "faulthandler" module that helps diagnosing crashes * The new "unittest.mock" module * The new "ipaddress" module * The "sys.implementation" attribute * A policy framework for the email package, with a provisional (see PEP 411) policy that adds much improved unicode support for email header parsing * A "collections.ChainMap" class for linking mappings to a single unit * Wrappers for many more POSIX functions in the "os" and "signal" modules, as well as other useful functions such as "sendfile()" * Hash randomization, introduced in earlier bugfix releases, is now switched on by default In total, almost 500 API items are new or improved in Python 3.3. For a more extensive list of changes in 3.3.0, see http://docs.python.org/3.3/whatsnew/3.3.html To download Python 3.3.0 visit: http://www.python.org/download/releases/3.3.0/ Please consider trying Python 3.3.0 with your code and reporting any bugs you may notice to: http://bugs.python.org/ Enjoy! -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire python-dev team and 3.3's contributors)

7 years, 5 months

1
0
0 0

Summary of Python tracker Issues

by Python tracker

ACTIVITY SUMMARY (2012-08-17 - 2012-08-24) 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 3640 ( +0) closed 23914 (+58) total 27554 (+58) Open issues with patches: 1603 Issues opened (36) ================== #15316: runpy swallows ImportError information with relative imports http://bugs.python.org/issue15316 reopened by cjerdonek #15720: move __import__() out of the default lookup chain http://bugs.python.org/issue15720 opened by eric.snow #15721: PEP 3121, 384 Refactoring applied to tkinter module http://bugs.python.org/issue15721 opened by Robin.Schreiber #15722: PEP 3121, 384 Refactoring applied to decimal module http://bugs.python.org/issue15722 opened by Robin.Schreiber #15723: Python breaks OS' append guarantee on file writes http://bugs.python.org/issue15723 opened by bsdphk #15724: Add "versionchanged" to memoryview docs http://bugs.python.org/issue15724 opened by skrah #15725: PyType_FromSpecWithBases bugfix http://bugs.python.org/issue15725 opened by Robin.Schreiber #15727: PyType_FromSpecWithBases tp_new bugfix http://bugs.python.org/issue15727 opened by Robin.Schreiber #15729: PyStructSequence_NewType enhancement http://bugs.python.org/issue15729 opened by Robin.Schreiber #15730: Silence unused value warnings under Mac OS X 10.8/clang http://bugs.python.org/issue15730 opened by Benno.Rice #15731: Mechanism for inheriting docstrings and signatures http://bugs.python.org/issue15731 opened by ncoghlan #15733: PEP 3121, 384 Refactoring applied to winapi module http://bugs.python.org/issue15733 opened by Robin.Schreiber #15734: PEP 3121, 384 Refactoring applied to spwd module http://bugs.python.org/issue15734 opened by Robin.Schreiber #15735: PEP 3121, 384 Refactoring applied to ossaudio module http://bugs.python.org/issue15735 opened by Robin.Schreiber #15743: test_urllib2/test_urllib use deprecated urllib.Request methods http://bugs.python.org/issue15743 opened by Jeff.Knupp #15744: missing tests for {RawIO,BufferedIO,TextIO}.writelines http://bugs.python.org/issue15744 opened by pitrou #15745: Numerous utime ns tests fail on FreeBSD w/ ZFS http://bugs.python.org/issue15745 opened by trent #15746: test_winsound bombing out on 2003 buildslave http://bugs.python.org/issue15746 opened by trent #15748: Various symlink test failures in test_shutil on FreeBSD http://bugs.python.org/issue15748 opened by trent #15749: cgitb prints html for text when display disabled. http://bugs.python.org/issue15749 opened by aliles #15750: test_localtime_daylight_false_dst_true raises OverflowError: m http://bugs.python.org/issue15750 opened by trent #15751: Support subinterpreters in the GIL state API http://bugs.python.org/issue15751 opened by ncoghlan #15753: No-argument super in method with variable arguments raises Sys http://bugs.python.org/issue15753 opened by james.sanders #15756: subprocess.poll() does not handle errno.ECHILD "No child proce http://bugs.python.org/issue15756 opened by twhitema #15757: ./configure --with-pydebug on FreeBSD results in -O2 -pipe eve http://bugs.python.org/issue15757 opened by trent #15758: FileIO.readall() has worst case O(n^2) complexity http://bugs.python.org/issue15758 opened by sbt #15759: "make suspicious" doesn't display instructions in case of fail http://bugs.python.org/issue15759 opened by ezio.melotti #15761: Setting PYTHONEXECUTABLE can cause segfaults on OS X http://bugs.python.org/issue15761 opened by ned.deily #15765: test_getcwd_long_pathnames (in test_posix) kills NetBSD http://bugs.python.org/issue15765 opened by trent #15766: _imp.load_dynamic() does crash with non-ASCII path and uses th http://bugs.python.org/issue15766 opened by haypo #15767: add ModuleNotFoundError http://bugs.python.org/issue15767 opened by eric.snow #15769: urllib.request.urlopen with cafile or capath set overrides any http://bugs.python.org/issue15769 opened by caligatio #15772: Unresolved symbols in Windows 64-bit python http://bugs.python.org/issue15772 opened by spatz123 #15775: Add StopParser() to expat http://bugs.python.org/issue15775 opened by nemeskeyd #15776: Allow pyvenv to work in existing directory http://bugs.python.org/issue15776 opened by stefanholek #15777: test_capi refleak http://bugs.python.org/issue15777 opened by rosslagerwall Most recent 15 issues with no replies (15) ========================================== #15775: Add StopParser() to expat http://bugs.python.org/issue15775 #15772: Unresolved symbols in Windows 64-bit python http://bugs.python.org/issue15772 #15767: add ModuleNotFoundError http://bugs.python.org/issue15767 #15759: "make suspicious" doesn't display instructions in case of fail http://bugs.python.org/issue15759 #15749: cgitb prints html for text when display disabled. http://bugs.python.org/issue15749 #15744: missing tests for {RawIO,BufferedIO,TextIO}.writelines http://bugs.python.org/issue15744 #15735: PEP 3121, 384 Refactoring applied to ossaudio module http://bugs.python.org/issue15735 #15734: PEP 3121, 384 Refactoring applied to spwd module http://bugs.python.org/issue15734 #15729: PyStructSequence_NewType enhancement http://bugs.python.org/issue15729 #15727: PyType_FromSpecWithBases tp_new bugfix http://bugs.python.org/issue15727 #15725: PyType_FromSpecWithBases bugfix http://bugs.python.org/issue15725 #15714: PEP 3121, 384 Refactoring applied to grp module http://bugs.python.org/issue15714 #15713: PEP 3121, 384 Refactoring applied to zipimport module http://bugs.python.org/issue15713 #15712: PEP 3121, 384 Refactoring applied to unicodedata module http://bugs.python.org/issue15712 #15711: PEP 3121, 384 Refactoring applied to time module http://bugs.python.org/issue15711 Most recent 15 issues waiting for review (15) ============================================= #15776: Allow pyvenv to work in existing directory http://bugs.python.org/issue15776 #15769: urllib.request.urlopen with cafile or capath set overrides any http://bugs.python.org/issue15769 #15766: _imp.load_dynamic() does crash with non-ASCII path and uses th http://bugs.python.org/issue15766 #15765: test_getcwd_long_pathnames (in test_posix) kills NetBSD http://bugs.python.org/issue15765 #15759: "make suspicious" doesn't display instructions in case of fail http://bugs.python.org/issue15759 #15758: FileIO.readall() has worst case O(n^2) complexity http://bugs.python.org/issue15758 #15756: subprocess.poll() does not handle errno.ECHILD "No child proce http://bugs.python.org/issue15756 #15753: No-argument super in method with variable arguments raises Sys http://bugs.python.org/issue15753 #15749: cgitb prints html for text when display disabled. http://bugs.python.org/issue15749 #15743: test_urllib2/test_urllib use deprecated urllib.Request methods http://bugs.python.org/issue15743 #15735: PEP 3121, 384 Refactoring applied to ossaudio module http://bugs.python.org/issue15735 #15734: PEP 3121, 384 Refactoring applied to spwd module http://bugs.python.org/issue15734 #15733: PEP 3121, 384 Refactoring applied to winapi module http://bugs.python.org/issue15733 #15731: Mechanism for inheriting docstrings and signatures http://bugs.python.org/issue15731 #15730: Silence unused value warnings under Mac OS X 10.8/clang http://bugs.python.org/issue15730 Top 10 most discussed issues (10) ================================= #15751: Support subinterpreters in the GIL state API http://bugs.python.org/issue15751 23 msgs #15758: FileIO.readall() has worst case O(n^2) complexity http://bugs.python.org/issue15758 16 msgs #15316: runpy swallows ImportError information with relative imports http://bugs.python.org/issue15316 9 msgs #15723: Python breaks OS' append guarantee on file writes http://bugs.python.org/issue15723 9 msgs #15748: Various symlink test failures in test_shutil on FreeBSD http://bugs.python.org/issue15748 9 msgs #15776: Allow pyvenv to work in existing directory http://bugs.python.org/issue15776 9 msgs #13370: test_ctypes fails when building python with clang http://bugs.python.org/issue13370 8 msgs #15642: Integrate pickle protocol version 4 GSoC work by Stefan Mihail http://bugs.python.org/issue15642 8 msgs #15745: Numerous utime ns tests fail on FreeBSD w/ ZFS http://bugs.python.org/issue15745 8 msgs #14468: Update cloning guidelines in devguide http://bugs.python.org/issue14468 7 msgs Issues closed (55) ================== #1574: Touchpad 2 Finger scroll does not work in IDLE on Mac (But scr http://bugs.python.org/issue1574 closed by ned.deily #4966: Improving Lib Doc Sequence Types Section http://bugs.python.org/issue4966 closed by python-dev #6749: Support for encrypted zipfiles when interpreting zipfile as sc http://bugs.python.org/issue6749 closed by ncoghlan #12415: Missing: How to checkout the Doc sources http://bugs.python.org/issue12415 closed by sandro.tosi #13579: string.Formatter doesn't understand the a conversion specifier http://bugs.python.org/issue13579 closed by r.david.murray #13799: Base 16 should be hexadecimal in Unicode HOWTO http://bugs.python.org/issue13799 closed by terry.reedy #14292: OS X installer build script doesn't set $CXX, so it ends up as http://bugs.python.org/issue14292 closed by ned.deily #14563: Segmentation fault on ctypes.Structure subclass with byte stri http://bugs.python.org/issue14563 closed by aliles #14814: Implement PEP 3144 (the ipaddress module) http://bugs.python.org/issue14814 closed by python-dev #14846: Change in error when sys.path contains a nonexistent folder (i http://bugs.python.org/issue14846 closed by python-dev #14954: weakref doc clarification http://bugs.python.org/issue14954 closed by pitrou #15131: Document py/pyw launchers http://bugs.python.org/issue15131 closed by brian.curtin #15199: Default mimetype for javascript should be application/javascri http://bugs.python.org/issue15199 closed by petri.lehtinen #15249: email.generator.BytesGenerator doesn't mangle "From " lines wh http://bugs.python.org/issue15249 closed by r.david.murray #15355: generator docs should mention already-executing exception http://bugs.python.org/issue15355 closed by r.david.murray #15477: test_cmath failures on OS X 10.8 http://bugs.python.org/issue15477 closed by mark.dickinson #15511: _decimal does not build in PGUpdate mode http://bugs.python.org/issue15511 closed by loewis #15570: email.header.decode_header parses differently http://bugs.python.org/issue15570 closed by r.david.murray #15595: subprocess.Popen(universal_newlines=True) does not work for ce http://bugs.python.org/issue15595 closed by asvetlov #15615: More tests for JSON decoder to test Exceptions http://bugs.python.org/issue15615 closed by pitrou #15632: regrtest.py: spurious leaks with -R option http://bugs.python.org/issue15632 closed by python-dev #15636: base64.decodebytes is only available in Python3.1+ http://bugs.python.org/issue15636 closed by eric.araujo #15637: Segfault reading null VMA (works fine in python 2.x) http://bugs.python.org/issue15637 closed by r.david.murray #15640: Document importlib.abc.Finder as deprecated http://bugs.python.org/issue15640 closed by brett.cannon #15645: 2to3 Grammar pickles not created when upgrading to 3.3.0b2 http://bugs.python.org/issue15645 closed by ned.deily #15660: Clarify 0 prefix for width specifier in str.format doc, http://bugs.python.org/issue15660 closed by terry.reedy #15678: IDLE menu customization is broken from OS X command lines http://bugs.python.org/issue15678 closed by ned.deily #15694: link to "file object" glossary entry in open() and io docs http://bugs.python.org/issue15694 closed by r.david.murray #15715: __import__ now raises with non-existing items in fromlist in 3 http://bugs.python.org/issue15715 closed by brett.cannon #15717: Mail System Error - Returned Mail http://bugs.python.org/issue15717 closed by eric.araujo #15719: Sort dict items in urlencode() http://bugs.python.org/issue15719 closed by gvanrossum #15726: PyState_FindModule false length-comparison fix http://bugs.python.org/issue15726 closed by pitrou #15728: Leak in PyUnicode_AsWideCharString() http://bugs.python.org/issue15728 closed by skrah #15732: Crash (constructed) in _PySequence_BytesToCharpArray() http://bugs.python.org/issue15732 closed by skrah #15736: Crash #2 (constructed overflow) in _PySequence_BytesToCharpAr http://bugs.python.org/issue15736 closed by skrah #15737: NULL dereference in zipimport.c http://bugs.python.org/issue15737 closed by python-dev #15738: Crash (constructed) in subprocess_fork_exec() http://bugs.python.org/issue15738 closed by skrah #15739: Python crashes with "Bus error: 10" http://bugs.python.org/issue15739 closed by ned.deily #15740: test_ssl failure when cacert.org CA cert in system keychain on http://bugs.python.org/issue15740 closed by ronaldoussoren #15741: NULL dereference in builtin_compile() http://bugs.python.org/issue15741 closed by skrah #15742: SQLite3 documentation changes http://bugs.python.org/issue15742 closed by r.david.murray #15747: Various chflags tests failing on FreeBSD/ZFS http://bugs.python.org/issue15747 closed by trent #15752: change test_json's use of deprecated unittest function http://bugs.python.org/issue15752 closed by ezio.melotti #15754: Traceback message not returning SQLite check constraint detail http://bugs.python.org/issue15754 closed by jftuga #15760: make install should generate grammar file http://bugs.python.org/issue15760 closed by lregebro #15762: Windows 8 certification http://bugs.python.org/issue15762 closed by loewis #15763: email non-ASCII characters in TO or FROM field doesn't work http://bugs.python.org/issue15763 closed by r.david.murray #15764: Sqlite3 performance http://bugs.python.org/issue15764 closed by loewis #15768: re.sub() with re.MULTILINE not replacing all occurrences http://bugs.python.org/issue15768 closed by eacousineau #15770: _testbuffer.get_contiguous() doesn't check input arguments http://bugs.python.org/issue15770 closed by skrah #15771: Tunple Bug? http://bugs.python.org/issue15771 closed by ezio.melotti #15773: `is' operator returns False on classmethods http://bugs.python.org/issue15773 closed by ncoghlan #15774: String method title() produces incorrect resutls http://bugs.python.org/issue15774 closed by r.david.murray #1578643: various datetime methods fail in restricted mode http://bugs.python.org/issue1578643 closed by belopolsky #1228112: code.py use sys.excepthook to display exceptions http://bugs.python.org/issue1228112 closed by tebeka

7 years, 5 months

5
6
0 0

Snakebite build slaves and developer SSH/GPG public keys

by Trent Nelson

Hi folks, I've set up a bunch of Snakebite build slaves over the past week. One of the original goals was to provide Python committers with full access to the slaves, which I'm still keen on providing. What's a nice simple way to achieve that in the interim? Here's what I was thinking: - Create a new hg repo: hg.python.org/keys. - Committers can push to it just like any other repo (i.e. same ssh/authz configuration as cpython). - Repo is laid out as follows: keys/ <python username>/ ssh (ssh public key) gpg (gpg public key) - Prime the repo with the current .ssh/authorized_keys (presuming you still use the --tunnel-user facility?). That'll provide me with everything I need to set up the relevant .ssh/authorized_keys stuff on the Snakebite side. GPG keys will be handy if I ever need to send passwords over e-mail (which I'll probably have to do initially for those that want to RDP into the Windows slaves). Thoughts? As for the slaves, here's what's up and running now: - AMD64 Mountain Lion [SB] - AMD64 FreeBSD 8.2 [SB] - AMD64 FreeBSD 9.1 [SB] - AMD64 NetBSD 5.1.2 [SB] - AMD64 OpenBSD 5.1 [SB] - AMD64 DragonFlyBSD 3.0.2 [SB] - AMD64 Windows Server 2008 R2 SP1 [SB] - x86 NetBSD 5.1.2 [SB] - x86 OpenBSD 5.1 [SB] - x86 DragonFlyBSD 3.0.2 [SB] - x86 Windows Server 2003 R2 SP2 [SB] - x86 Windows Server 2008 R2 SP1 [SB] All the FreeBSD ones use ZFS, all the DragonFly ones use HAMMER. DragonFly, NetBSD and OpenBSD are currently reporting all sorts of weird and wonderful errors, which is partly why I want to set up ssh access sooner rather than later. Other slaves on the horizon (i.e. hardware is up, OS is installed): - Windows 8 x64 (w/ VS2010 and VS2012) - HP-UX 11iv2 PA-RISC - HP-UX 11iv3 Itanium (64GB RAM) - AIX 5.3 RS/6000 - AIX 6.1 RS/6000 - AIX 7.1 RS/6000 - Solaris 9 SPARC - Solaris 10 SPARC Nostalgia slaves that probably won't ever see green: - IRIX 6.5.33 MIPS - Tru64 5.1B Alpha If anyone wants ssh access now to the UNIX platforms in order to debug/test, feel free to e-mail me directly with your ssh public keys. For committers on other Python projects like Buildbot, Django and Twisted that may be reading this -- yes, the plan is to give you guys Snakebite access/slaves down the track too. I'll start looking into that after I've finished setting up the remaining slaves for Python. (Setting up a keys repo will definitely help (doesn't have to be hg -- feel free to use svn/git/whatever, just try and follow the same layout).) Regards, Trent "that-took-a-bit-longer-than-expected" Nelson.

7 years, 5 months

10
16
0 0

[compatibility-sig] do all VMs implement the ast module? (was: Re: AST optimizer implemented in Python)

by Brett Cannon

On Mon, Aug 13, 2012 at 3:00 PM, Terry Reedy <tjreedy(a)udel.edu> wrote: > On 8/13/2012 10:45 AM, Guido van Rossum wrote: > >> Not so fast. If you make this a language feature you force all Python >> implementations to support an identical AST API. That's a big step. >> > > I have been wondering about this. One could think from the manuals that we > are there already. From the beginning of the ast chapter: > > "The ast module helps Python applications to process trees of *the* Python > abstract syntax grammar. ... An abstract syntax tree can be generated by > passing ast.PyCF_ONLY_AST as a flag to the compile() built-in function" > (emphasis on *the* added). > > and the entry for compile(): "Compile the source into a code or AST > object." > > I see nothing about ast possibly being CPython only. Should there be? Time to ask the other VMs what they are currently doing (the ast module came into existence in Python 2.6 so all the VMs should be answer the question since Jython is in alpha for 2.7 compatibility).

7 years, 5 months

7
12
0 0

bug in tarfile module?

by Chris Withers

Hi All, This feels like a bug, but just wanted to check here before filing a report if I've missed something: buzzkill$ python2.7 Enthought Python Distribution -- www.enthought.com Version: 7.2-2 (32-bit) Python 2.7.2 |EPD 7.2-2 (32-bit)| (default, Sep 7 2011, 09:16:50) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type "packages", "demo" or "enthought" for more information. >>> import tarfile >>> source = open('/src/Python-2.6.7.tgz', 'rb') >>> tar = tarfile.open(fileobj=source, mode='r|*') >>> member = tar.extractfile('Python-2.6.7/Lib/genericpath.py') >>> data = member.read() Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/Library/Frameworks/Python.framework/Versions/7.2/lib/python2.7/tarfile.py", line 815, in read buf += self.fileobj.read() File "/Library/Frameworks/Python.framework/Versions/7.2/lib/python2.7/tarfile.py", line 735, in read return self.readnormal(size) File "/Library/Frameworks/Python.framework/Versions/7.2/lib/python2.7/tarfile.py", line 742, in readnormal self.fileobj.seek(self.offset + self.position) File "/Library/Frameworks/Python.framework/Versions/7.2/lib/python2.7/tarfile.py", line 554, in seek raise StreamError("seeking backwards is not allowed") tarfile.StreamError: seeking backwards is not allowed The key is the "mode='r*|" which I understood to be specifically for reading blocks from a stream without seeking that would cause problems. I've reproduced on Py26 and Py27 on Mac OS X, and Py26 on SUSE. Thoughts? Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

7 years, 5 months

3
2
0 0

root@python doc cron job failure messages

by Terry Reedy

root@python is indirectly trying to send doc cron job failure messages to the python-checkings list. headers below. They are caught and held for moderation since "Blind carbon copies or other implicit destinations are not allowed." I think it is a mistake to send these messages to checkins, which has enough checkins traffic already, but I do not know who is responsible to fix the situation. The last two examples: "home/docs/devguide/documenting.rst:773: WARNING: term not in glossary: bytecode" "abort: error: Connection timed out" Headers: Return-Path: <docs(a)python.org> X-Original-To: python-checkins(a)python.org Delivered-To: python-checkins(a)mail.python.org Received: from albatross.python.org (localhost [127.0.0.1]) by mail.python.org (Postfix) with ESMTP id 3X2G3z3xCNzQjK; Wed, 22 Aug 2012 19:30:23 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901; t=1345656623; bh=conhuN6h+7FXE7LPMr0jHBM5W+Bs5Ld9a8QDgyfQyA4=; h=Date:Message-Id:From:To:Subject:Content-Type; b=lVY4n5KqDW1Qzzy4ngaHTMcO7wCbBlDQzSPWDqaNsUGwrBrcjtY1X8+hiDNsDxUA/ A/wYxK1w887LE2mbzqzONtg2zoUau0cvTvG52sg0aXHqWLidRNbvJZ3WxYeYSC1ph/ pK5u6M9JBd5a1HOiyiTOA5uTu6DWXATy04FTkjdM= X-Spam-Status: OK 0.009 X-Spam-Evidence: '*H*': 0.98; '*S*': 0.00; 'received:dinsdale.python.org': 0.03; 'error:': 0.05; 'subject:build': 0.07; 'subject: <': 0.09; 'message- id:@dinsdale.python.org': 0.16; 'subject:home': 0.16; 'timed': 0.16; 'from:addr:python.org': 0.17; 'subject:/': 0.28; 'connection': 0.30; 'received:python.org': 0.31; 'received:org': 0.36; 'subject:-': 0.40; 'header:Message-Id:1': 0.62; 'to:addr:docs': 0.68; 'subject:@': 0.81 Received: from localhost (HELO mail.python.org) (127.0.0.1) by albatross.python.org with SMTP; 22 Aug 2012 19:30:23 +0200 Received: from dinsdale.python.org (svn.python.org [IPv6:2001:888:2000:d::a4]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.python.org (Postfix) with ESMTPS; Wed, 22 Aug 2012 19:30:23 +0200 (CEST) Received: from docs by dinsdale.python.org with local (Exim 4.72) (envelope-from <docs(a)dinsdale.python.org>) id 1T4El5-0007tw-4K for docs(a)dinsdale.python.org; Wed, 22 Aug 2012 19:30:23 +0200 Date: Wed, 22 Aug 2012 19:30:23 +0200 Message-Id: <E1T4El5-0007tw-4K(a)dinsdale.python.org> From: root(a)python.org (Cron Daemon) To: docs(a)dinsdale.python.org Subject: Cron <docs@dinsdale> /home/docs/build-devguide Content-Type: text/plain; charset=UTF-8 X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/home/docs> X-Cron-Env: <PATH=/usr/bin:/bin> X-Cron-Env: <LOGNAME=docs> -- Terry Jan Reedy

7 years, 5 months

1
0
0 0

3.3 str timings

by Terry Reedy

The issue came up in python-list about string operations being slower in 3.3. (The categorical claim is false as some things are actually faster.) Some things I understand, this one I do not. Win7-64, 3.3.0b2 versus 3.2.3 print(timeit("c in a", "c = '…'; a = 'a'*1000+c")) # ord(c) = 8230 # .6 in 3.2, 1.2 in 3.3 Why is searching for a two-byte char in a two-bytes per char string so much faster in 3.2? Is this worth a tracker issue (I searched and could not find one) or is there a known and un-fixable cause? print(timeit("a.encode()", "a = 'a'*1000")) # 1.5 in 3.2, .26 in 3.3 print(timeit("a.encode(encoding='utf-8')", "a = 'a'*1000")) # 1.7 in 3.2, .51 in 3.3 This is one of the 3.3 improvements. But since the results are equal: ('a'*1000).encode() == ('a'*1000).encode(encoding='utf-8') and 3.3 should know that for an all-ascii string, I do not see why adding the parameter should double the the time. Another issue or known and un-fixable? -- Terry Jan Reedy

7 years, 5 months

12
17
0 0

Jython roadmap

by "Juancarlo Añez (Apalala)"

It seems that Jython is under the Python Foundation, but I can't find a roadmap, a plan, or instructions about how to contribute to it reaching 2.7 and 3.3. Are there any pages that describe the process? Thanks in advance, -- Juanca

7 years, 5 months

3
2
0 0

Re: [Python-Dev] [Python-checkins] cpython: Close #4966: revamp the sequence docs in order to better explain the state of

by Nick Coghlan

On Tue, Aug 21, 2012 at 11:55 AM, Ezio Melotti <ezio.melotti(a)gmail.com> wrote: >> +Sequence Types --- :class:`list`, :class:`tuple`, :class:`range` >> +================================================================ >> + > > > These 3 links in the section title redirect to the functions.html page. I > think it would be better if they linked to the appropriate subsection > instead, and in the case of the subsections (e.g. "Text Sequence Type --- > str") they shouldn't be links. The same comment can be applied to other > titles as well. I made a start on moving the info out of functions.html and adding appropriate noindex entries. str, bytes and bytearray haven't been consolidated at all yet. >> ++--------------------------+--------------------------------+----------+ >> +| ``s * n, n * s`` | *n* shallow copies of *s* | (2)(7) | > > > I would use '``s * n`` or ``n * s``' here. Done. >> +| ``s.index(x, [i[, j]])`` | index of the first occurence | \(8) | > > > This should be ``s.index(x[, i[, j]])`` Done. >> + >> + * if concatenating :class:`tuple` objects, extend a :class:`list` >> instead. >> + >> + * for other types, investigate the relevant class documentation >> + > > > The trailing punctuation of the elements in this list is inconsistent. Just removed all trailing punctuation from these bullet points for now. > > You missed clear() from this list. The problem was actually index() and count() were missing from the index for the "common sequence operations" table. Added them there, and moved that index above the table. copy() was missing from the index list for the mutable sequence methods, so I added that. > Also in the "Result" column the descriptions in prose are OK, but I find > some of the "same as ..." ones not very readable (or even fairly obscure). > (I think I saw something similar in the doc of list.append() too.) These are all rather old - much of this patch was just moving things around rather than fixing the prose, although there was plenty of the latter, too :) I tried to improve them a bit. > Is it worth mentioning a function call as an example of syntactic ambiguity? > Someone might wonder if foo(a, b, c) is actually passing a 3-elements tuple > or 3 distinct values. Done. > This claim is maybe a bit too strong. I think the main reason to use > namedtuples is being able to access the elements via t.name, rather than > t[pos], and while this can be useful for basically every heterogeneous > tuple, I think that plain tuples are still preferred. Reworded. > On a separate note, should tuple unpacking be mentioned here? (a link to a > separate section of the doc is enough.) Not really - despite the name, tuple unpacking isn't especially closely related to tuples these days. > I would mention explicitly "in :keyword:`for` loops" -- ranges don't loop on > their own (I think people familiar with Ruby and/or JQuery might get > confused here). Done. > I thought that these two paragraphs were talking about positive and negative > start/stop/step until I reached the middle of the second paragraph (the word > "indices" wasn't enough to realize that these paragraphs are about > indexing/slicing, probably because they are rarely used and I wasn't > expecting to find them at this point of the doc). Maybe it's better to move > the paragraphs at the bottom of the section. For the moment, I've just dumped the old range builtin docs into this section. They need a pass to remove the duplication and ensure everything makes sense in context. >> +String literals that are part of a single expression and have only >> whitespace >> +between them will be implicitly converted to a single string literal. >> + > > > Is it a string /literal/ they are converted to? Yup: >>> ast.dump(compile('"hello world"', '', 'eval', flags=ast.PyCF_ONLY_AST)) "Expression(body=Str(s='hello world'))" >>> ast.dump(compile('"hello" " world"', '', 'eval', flags=ast.PyCF_ONLY_AST)) "Expression(body=Str(s='hello world'))" > Anyway a simple ('foo' 'bar') == 'foobar' example might make this sentence > more understandable. Added. >> +There is also no mutable string type, but :meth:`str.join` or >> +:class:`io.StringIO` can be used to efficiently construct strings from >> +multiple fragments. >> + > > str.format() deserves to be mentioned here too. For the kinds of strings where quadratic growth is a problem, str.format is unlikely to be appropriate. > I noticed that here there's this fairly long section about the "old" string > formatting and nothing about the "new" formatting. Maybe this should be > moved together with the new formatting doc, so that all the detailed > formatting docs are in the same place. (This would also help making this > less noticeable) Probably. There are a lot of structural problems in the current docs, because the layout hasn't previously changed to suit the language design changes. >> +While bytes literals and representations are based on ASCII text, bytes >> +objects actually behave like immutable sequences of integers, with each >> +value in the sequence restricted such that ``0 <= x < 256`` (attempts to > > Earlier you used 0 <= x <= 255. The current docs are the result of many merges, much of which I didn't write. This is only the start of improving them by breaking away from the old 1.x structure with a few autocratic decisions on my part to establish a new layout that makes more sense given the evolution of the language, especially the big changes in 2.2 and 3.0 :) > Using ``'abc'.replace('a', 'f')`` and ``b'abc'.replace(b'a', b'f')`` inline > would be better IMHO, given that the current note takes lot of space to > explain a trivial concept. Stylistics edits are always fair game, they don't have to be made by me. While I skipped a lot of your specific suggestions that weren't correcting actual errors, that doesn't mean I'm especially opposed to them, just that I didn't like them enough to implement myself :) Cheers, Nick. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

7 years, 5 months

2
2
0 0

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

Python-Dev August 2012