Mailman 3 January 2012 - Python-Dev

Hashing proposal: change only string-only dicts
by "Martin v. Löwis" 20 Jan '12

20 Jan '12

I'd like to propose a different approach to seeding the string hashes: only do so for dictionaries involving only strings, and leave the tp_hash slot of strings unchanged. Each string would get two hashes: the "public" hash, which is constant across runs and bugfix releases, and the dict-hash, which is only used by the dictionary implementation, and only if all keys to the dict are strings. In order to allow caching of the hash, all dicts should use the same hash (if caching wasn't necessary, each dict could use its own seed). There are several variants of that approach wrt. caching of the hash 1. add an additional field to all string objects, to cache the second hash value. a) variant: in 3.3, drop the extra field, and declare that hashes may change across runs 2. only cache the dict-hash, recomputing the public hash each time 3. on a per-string choice, cache either the dict-hash or the public hash, depending on which one gets computed first, and recompute the other one every time it's needed. As you can see, 1 vs. 2/3 is a classical time-space-tradeoff. What do you think? Regards, Martin

10 17

negative ref count on windows debug version
by Dr.-Ing. Ingo D. Rullhusen 20 Jan '12

20 Jan '12

Hello, using loc = PyDict_New(); Py_XDECREF(loc); or PyObject *src = Py_CompileString( code.toStdString().c_str(), "<console>", Py_single_input ); Py_XDECREF(src); results in a "object at blahblah has negative ref count -1" error on windows visual studio in debug mode. And yes, python is compiled and linked in debug mode also. The release version seems to work. This happens in version 2.6.7 and 2.7.2. Any hints? Thanks Ingo

2 1

PEP 407: New release cycle and introducing long-term support versions
by Antoine Pitrou 20 Jan '12

20 Jan '12

Hello, We would like to propose the following PEP to change (C)Python's release cycle. Discussion is welcome, especially from people involved in the release process, and maintainers from third-party distributions of Python. Regards Antoine. PEP: 407 Title: New release cycle and introducing long-term support versions Version: $Revision$ Last-Modified: $Date$ Author: Antoine Pitrou <solipsis(a)pitrou.net>, Georg Brandl <georg(a)python.org>, Barry Warsaw <barry(a)python.org> Status: Draft Type: Process Content-Type: text/x-rst Created: 2012-01-12 Post-History: Resolution: TBD Abstract ======== Finding a release cycle for an open-source project is a delicate exercise in managing mutually contradicting constraints: developer manpower, availability of release management volunteers, ease of maintenance for users and third-party packagers, quick availability of new features (and behavioural changes), availability of bug fixes without pulling in new features or behavioural changes. The current release cycle errs on the conservative side. It is adequate for people who value stability over reactivity. This PEP is an attempt to keep the stability that has become a Python trademark, while offering a more fluid release of features, by introducing the notion of long-term support versions. Scope ===== This PEP doesn't try to change the maintenance period or release scheme for the 2.7 branch. Only 3.x versions are considered. Proposal ======== Under the proposed scheme, there would be two kinds of feature versions (sometimes dubbed "minor versions", for example 3.2 or 3.3): normal feature versions and long-term support (LTS) versions. Normal feature versions would get either zero or at most one bugfix release; the latter only if needed to fix critical issues. Security fix handling for these branches needs to be decided. LTS versions would get regular bugfix releases until the next LTS version is out. They then would go into security fixes mode, up to a termination date at the release manager's discretion. Periodicity ----------- A new feature version would be released every X months. We tentatively propose X = 6 months. LTS versions would be one out of N feature versions. We tentatively propose N = 4. With these figures, a new LTS version would be out every 24 months, and remain supported until the next LTS version 24 months later. This is mildly similar to today's 18 months bugfix cycle for every feature version. Pre-release versions -------------------- More frequent feature releases imply a smaller number of disruptive changes per release. Therefore, the number of pre-release builds (alphas and betas) can be brought down considerably. Two alpha builds and a single beta build would probably be enough in the regular case. The number of release candidates depends, as usual, on the number of last-minute fixes before final release. Effects ======= Effect on development cycle --------------------------- More feature releases might mean more stress on the development and release management teams. This is quantitatively alleviated by the smaller number of pre-release versions; and qualitatively by the lesser amount of disruptive changes (meaning less potential for breakage). The shorter feature freeze period (after the first beta build until the final release) is easier to accept. The rush for adding features just before feature freeze should also be much smaller. Effect on bugfix cycle ---------------------- The effect on fixing bugs should be minimal with the proposed figures. The same number of branches would be simultaneously open for regular maintenance (two until 2.x is terminated, then one). Effect on workflow ------------------ The workflow for new features would be the same: developers would only commit them on the ``default`` branch. The workflow for bug fixes would be slightly updated: developers would commit bug fixes to the current LTS branch (for example ``3.3``) and then merge them into ``default``. If some critical fixes are needed to a non-LTS version, they can be grafted from the current LTS branch to the non-LTS branch, just like fixes are ported from 3.x to 2.7 today. Effect on the community ----------------------- People who value stability can just synchronize on the LTS releases which, with the proposed figures, would give a similar support cycle (both in duration and in stability). People who value reactivity and access to new features (without taking the risk to install alpha versions or Mercurial snapshots) would get much more value from the new release cycle than currently. People who want to contribute new features or improvements would be more motivated to do so, knowing that their contributions will be more quickly available to normal users. Also, a smaller feature freeze period makes it less cumbersome to interact with contributors of features. Discussion ========== These are open issues that should be worked out during discussion: * Decide on X (months between feature releases) and N (feature releases per LTS release) as defined above. * For given values of X and N, is the no-bugfix-releases policy for non-LTS versions feasible? * Restrict new syntax and similar changes (i.e. everything that was prohibited by PEP 3003) to LTS versions? * What is the effect on packagers such as Linux distributions? * How will release version numbers or other identifying and marketing material make it clear to users which versions are normal feature releases and which are LTS releases? How do we manage user expectations? A community poll or survey to collect opinions from the greater Python community would be valuable before making a final decision. 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:

23 58

Summary of Python tracker Issues
by Python tracker 20 Jan '12

20 Jan '12

ACTIVITY SUMMARY (2012-01-13 - 2012-01-20) 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 3209 ( -1) closed 22405 (+53) total 25614 (+52) Open issues with patches: 1376 Issues opened (37) ================== #13411: Hashable memoryviews http://bugs.python.org/issue13411 reopened by skrah #13782: xml.etree.ElementTree: Element.append doesn't type-check its a http://bugs.python.org/issue13782 opened by sjmachin #13783: Clean up PEP 380 C API additions http://bugs.python.org/issue13783 opened by ncoghlan #13784: Documentation of xml.sax.xmlreader: Locator.getLineNumber() a http://bugs.python.org/issue13784 opened by patrick.vrijlandt #13785: Make concurrent.futures.Future state public http://bugs.python.org/issue13785 opened by jjdominguezm #13788: os.closerange optimization http://bugs.python.org/issue13788 opened by ferringb #13789: _tkinter does not build on Windows 7 http://bugs.python.org/issue13789 opened by terry.reedy #13790: In str.format an incorrect error message for list, tuple, dict http://bugs.python.org/issue13790 opened by py.user #13792: The "os.execl" call doesn't give programs exit code http://bugs.python.org/issue13792 opened by kayhayen #13793: hasattr, delattr, getattr fail with unnormalized names http://bugs.python.org/issue13793 opened by Jim.Jewett #13796: use 'text=...' to define the text attribute of and xml.etree.E http://bugs.python.org/issue13796 opened by paaguti #13797: Allow objects implemented in pure Python to export PEP 3118 bu http://bugs.python.org/issue13797 opened by ncoghlan #13798: Pasting and then running code doesn't work in the IDLE Shell http://bugs.python.org/issue13798 opened by ramchandra.apte #13799: Base 16 should be hexadecimal in Unicode HOWTO http://bugs.python.org/issue13799 opened by ramchandra.apte #13801: The Python 3 Docs don't highlight nonlocal http://bugs.python.org/issue13801 opened by ramchandra.apte #13802: IDLE Prefernces/Fonts: use multiple alphabets in examples http://bugs.python.org/issue13802 opened by terry.reedy #13804: Python library structure creates hard to read code when using http://bugs.python.org/issue13804 opened by dwt #13806: Audioop decompression frames size check fix http://bugs.python.org/issue13806 opened by Oleg.Plakhotnyuk #13812: multiprocessing package doesn't flush stderr on child exceptio http://bugs.python.org/issue13812 opened by brandj #13814: Generators as context managers. http://bugs.python.org/issue13814 opened by yak #13815: tarfile.ExFileObject can't be wrapped using io.TextIOWrapper http://bugs.python.org/issue13815 opened by cjwatson #13816: Two typos in the docs http://bugs.python.org/issue13816 opened by Retro #13817: deadlock in subprocess while running several threads using Pop http://bugs.python.org/issue13817 opened by glaubich #13818: argparse: -h listening required options under optional argumen http://bugs.python.org/issue13818 opened by mgodinho #13819: _warnings settings are process-wide http://bugs.python.org/issue13819 opened by pitrou #13820: 2.6 is no longer in the future http://bugs.python.org/issue13820 opened by Jim.Jewett #13821: misleading return from isidentifier http://bugs.python.org/issue13821 opened by Jim.Jewett #13822: is(upper/lower/title) are not exactly correct http://bugs.python.org/issue13822 opened by benjamin.peterson #13823: xml.etree.ElementTree.ElementTree.write - argument checking http://bugs.python.org/issue13823 opened by patrick.vrijlandt #13824: argparse.FileType opens a file without excepting resposibility http://bugs.python.org/issue13824 opened by David.Layton #13825: Datetime failing while reading active directory time attribute http://bugs.python.org/issue13825 opened by scape #13826: Having a shlex example in the subprocess.Popen docs is confusi http://bugs.python.org/issue13826 opened by Julian #13828: Further improve casefold documentation http://bugs.python.org/issue13828 opened by Jim.Jewett #13829: exception error http://bugs.python.org/issue13829 opened by Dan.kamp #13830: codecs error handler is called with a UnicodeDecodeError with http://bugs.python.org/issue13830 opened by amaury.forgeotdarc #13831: get method of multiprocessing.pool.Async should return full t http://bugs.python.org/issue13831 opened by fmitha #13833: No documentation for PyStructSequence http://bugs.python.org/issue13833 opened by torsten Most recent 15 issues with no replies (15) ========================================== #13833: No documentation for PyStructSequence http://bugs.python.org/issue13833 #13831: get method of multiprocessing.pool.Async should return full t http://bugs.python.org/issue13831 #13830: codecs error handler is called with a UnicodeDecodeError with http://bugs.python.org/issue13830 #13829: exception error http://bugs.python.org/issue13829 #13824: argparse.FileType opens a file without excepting resposibility http://bugs.python.org/issue13824 #13823: xml.etree.ElementTree.ElementTree.write - argument checking http://bugs.python.org/issue13823 #13822: is(upper/lower/title) are not exactly correct http://bugs.python.org/issue13822 #13820: 2.6 is no longer in the future http://bugs.python.org/issue13820 #13819: _warnings settings are process-wide http://bugs.python.org/issue13819 #13818: argparse: -h listening required options under optional argumen http://bugs.python.org/issue13818 #13815: tarfile.ExFileObject can't be wrapped using io.TextIOWrapper http://bugs.python.org/issue13815 #13802: IDLE Prefernces/Fonts: use multiple alphabets in examples http://bugs.python.org/issue13802 #13784: Documentation of xml.sax.xmlreader: Locator.getLineNumber() a http://bugs.python.org/issue13784 #13777: socket: communicating with Mac OS X KEXT controls http://bugs.python.org/issue13777 #13771: HTTPSConnection __init__ super implementation causes recursion http://bugs.python.org/issue13771 Most recent 15 issues waiting for review (15) ============================================= #13833: No documentation for PyStructSequence http://bugs.python.org/issue13833 #13817: deadlock in subprocess while running several threads using Pop http://bugs.python.org/issue13817 #13816: Two typos in the docs http://bugs.python.org/issue13816 #13815: tarfile.ExFileObject can't be wrapped using io.TextIOWrapper http://bugs.python.org/issue13815 #13806: Audioop decompression frames size check fix http://bugs.python.org/issue13806 #13788: os.closerange optimization http://bugs.python.org/issue13788 #13785: Make concurrent.futures.Future state public http://bugs.python.org/issue13785 #13777: socket: communicating with Mac OS X KEXT controls http://bugs.python.org/issue13777 #13775: Access Denied message on symlink creation misleading for an ex http://bugs.python.org/issue13775 #13773: Support sqlite3 uri filenames http://bugs.python.org/issue13773 #13742: Add a key parameter (like sorted) to heapq.merge http://bugs.python.org/issue13742 #13736: urllib.request.urlopen leaks exceptions from socket and httpli http://bugs.python.org/issue13736 #13734: Add a generic directory walker method to avoid symlink attacks http://bugs.python.org/issue13734 #13733: Change required to sysconfig.py for Python 2.7.2 on OS/2 http://bugs.python.org/issue13733 #13719: bdist_msi upload fails http://bugs.python.org/issue13719 Top 10 most discussed issues (10) ================================= #13703: Hash collision security issue http://bugs.python.org/issue13703 48 msgs #12600: Add example of using load_tests to parameterise Test Cases http://bugs.python.org/issue12600 12 msgs #13790: In str.format an incorrect error message for list, tuple, dict http://bugs.python.org/issue13790 10 msgs #6727: ImportError when package is symlinked on Windows http://bugs.python.org/issue6727 8 msgs #13405: Add DTrace probes http://bugs.python.org/issue13405 8 msgs #6531: atexit_callfuncs() crashing within Py_Finalize() when using mu http://bugs.python.org/issue6531 7 msgs #13804: Python library structure creates hard to read code when using http://bugs.python.org/issue13804 7 msgs #8052: subprocess close_fds behavior should only close open fds http://bugs.python.org/issue8052 6 msgs #11805: package_data only allows one glob per-package http://bugs.python.org/issue11805 6 msgs #10181: Problems with Py_buffer management in memoryobject.c (and else http://bugs.python.org/issue10181 5 msgs Issues closed (51) ================== #2124: xml.sax and xml.dom fetch DTDs by default http://bugs.python.org/issue2124 closed by loewis #2134: Add new attribute to TokenInfo to report specific token IDs http://bugs.python.org/issue2134 closed by meador.inge #6528: builtins colored as keyword at beginning of line http://bugs.python.org/issue6528 closed by terry.reedy #8285: IDLE not smart indenting correctly in nested statements http://bugs.python.org/issue8285 closed by terry.reedy #11906: test_argparse failure in interactive mode http://bugs.python.org/issue11906 closed by terry.reedy #11948: Tutorial/Modules - small fix to better clarify the modules sea http://bugs.python.org/issue11948 closed by sandro.tosi #12705: Make compile('1\n2\n', '', 'single') raise an exception instea http://bugs.python.org/issue12705 closed by meador.inge #12949: Documentation of PyCode_New() lacks kwonlyargcount argument http://bugs.python.org/issue12949 closed by meador.inge #13039: IDLE editor: shell-like behaviour on line starting with ">>>" http://bugs.python.org/issue13039 closed by terry.reedy #13516: Gzip old log files in rotating handlers http://bugs.python.org/issue13516 closed by vinay.sajip #13589: Aifc low level serialization primitives fix http://bugs.python.org/issue13589 closed by pitrou #13605: document argparse's nargs=REMAINDER http://bugs.python.org/issue13605 closed by sandro.tosi #13629: _PyParser_TokenNames does not match up with the token.h number http://bugs.python.org/issue13629 closed by meador.inge #13642: urllib incorrectly quotes username and password in https basic http://bugs.python.org/issue13642 closed by orsenthil #13645: import machinery vulnerable to timestamp collisions http://bugs.python.org/issue13645 closed by pitrou #13665: TypeError: string or integer address expected instead of str i http://bugs.python.org/issue13665 closed by ezio.melotti #13695: "type specific" to "type-specific" http://bugs.python.org/issue13695 closed by ezio.melotti #13715: typo in unicodedata documentation http://bugs.python.org/issue13715 closed by ezio.melotti #13722: "distributions can disable the encodings package" http://bugs.python.org/issue13722 closed by pitrou #13723: Regular expressions: (?:X|\s+)*$ takes a long time http://bugs.python.org/issue13723 closed by terry.reedy #13725: regrtest does not recognize -d flag http://bugs.python.org/issue13725 closed by meador.inge #13726: regrtest ambiguous -S flag http://bugs.python.org/issue13726 closed by orsenthil #13727: Accessor macros for PyDateTime_Delta members http://bugs.python.org/issue13727 closed by amaury.forgeotdarc #13728: Description of -m and -c cli options wrong? http://bugs.python.org/issue13728 closed by sandro.tosi #13730: Grammar mistake in Decimal documentation http://bugs.python.org/issue13730 closed by python-dev #13746: ast.Tuple's have an inconsistent "col_offset" value http://bugs.python.org/issue13746 closed by georg.brandl #13752: add a str.casefold() method http://bugs.python.org/issue13752 closed by python-dev #13760: ConfigParser exceptions are not pickleable http://bugs.python.org/issue13760 closed by lukasz.langa #13761: Add flush keyword to print() http://bugs.python.org/issue13761 closed by python-dev #13763: Potentially hard to understand wording in devguide http://bugs.python.org/issue13763 closed by terry.reedy #13764: Misc/build.sh is outdated... talks about svn http://bugs.python.org/issue13764 closed by pitrou #13766: explain the relationship between Lib/lib2to3/Grammar.txt and G http://bugs.python.org/issue13766 closed by python-dev #13768: Doc/tools/dailybuild.py available only on 2.7 branch http://bugs.python.org/issue13768 closed by georg.brandl #13774: json.loads raises a SystemError for invalid encoding on 2.7.2 http://bugs.python.org/issue13774 closed by amaury.forgeotdarc #13780: make YieldFrom its own node http://bugs.python.org/issue13780 closed by python-dev #13781: gzip module does the wrong thing with an os.fdopen()'ed fileob http://bugs.python.org/issue13781 closed by nadeem.vawda #13786: regrtest.py does not handle --trace http://bugs.python.org/issue13786 closed by meador.inge #13787: PyCode_New not round-trippable (TypeError) http://bugs.python.org/issue13787 closed by amaury.forgeotdarc #13791: Reword “Old versions” in the doc sidebar http://bugs.python.org/issue13791 closed by eric.araujo #13794: Copyright Year - Change it to 2012 please http://bugs.python.org/issue13794 closed by eric.araujo #13795: CDATA Element missing http://bugs.python.org/issue13795 closed by amaury.forgeotdarc #13803: Under Solaris, distutils doesn't include bitness in the direct http://bugs.python.org/issue13803 closed by python-dev #13805: [].sort() should return self http://bugs.python.org/issue13805 closed by ezio.melotti #13807: logging.Handler.handlerError() may raise AttributeError in tra http://bugs.python.org/issue13807 closed by python-dev #13808: url for Tutor mailing list is broken http://bugs.python.org/issue13808 closed by ezio.melotti #13809: bz2 does not work when threads are disabled http://bugs.python.org/issue13809 closed by nadeem.vawda #13810: refer people to Doc/Makefile when not using 'make' to build ma http://bugs.python.org/issue13810 closed by sandro.tosi #13811: In str.format, if invalid fill and alignment are specified, th http://bugs.python.org/issue13811 closed by python-dev #13813: "sysconfig.py" and "distutils/util.py" redundancy http://bugs.python.org/issue13813 closed by eric.araujo #13827: Unexecuted import changes namespace http://bugs.python.org/issue13827 closed by benjamin.peterson #13832: tokenization assuming ASCII whitespace; missing multiline case http://bugs.python.org/issue13832 closed by benjamin.peterson

1 0

Re: [Python-Dev] [Python-checkins] cpython (3.1): Closes #13807: Now checks for sys.stderr being there before writing to it.
by Meador Inge 20 Jan '12

20 Jan '12

On Fri, Jan 20, 2012 at 5:32 AM, vinay.sajip <python-checkins(a)python.org> wrote: > http://hg.python.org/cpython/rev/73dad4940b88 > changeset: 74538:73dad4940b88 > branch: 3.1 I thought that the 3.1 branch is in security mode? Is this a security related fix? >From my brief scan of the changeset, it doesn't seem to be. > parent: 74253:fb5707168351 > user: Vinay Sajip <vinay_sajip(a)yahoo.co.uk> > date: Fri Jan 20 11:23:02 2012 +0000 > summary: > Closes #13807: Now checks for sys.stderr being there before writing to it. > > files: > Lib/logging/__init__.py | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > > diff --git a/Lib/logging/__init__.py b/Lib/logging/__init__.py > --- a/Lib/logging/__init__.py > +++ b/Lib/logging/__init__.py > @@ -721,7 +721,7 @@ > You could, however, replace this with a custom handler if you wish. > The record which was being processed is passed in to this method. > """ > - if raiseExceptions: > + if raiseExceptions and sys.stderr: # see issue 13807 > ei = sys.exc_info() > try: > traceback.print_exception(ei[0], ei[1], ei[2], None, sys.stderr) > > -- > Repository URL: http://hg.python.org/cpython > > _______________________________________________ > Python-checkins mailing list > Python-checkins(a)python.org > http://mail.python.org/mailman/listinfo/python-checkins > -- # Meador

1 0

Writable __doc__
by Ethan Furman 19 Jan '12

19 Jan '12

Is there a reason why normal classes can't have their __doc__ strings rewritten? Creating a do-nothing metaclass seems like overkill for such a simple operation. Python 3.2 ... on win32 --> class Test(): ... __doc__ = 'am I permanent?' ... --> Test.__doc__ 'am I permanent?' --> Test.__doc__ = 'yes' Traceback (most recent call last): File "<stdin>", line 1, in <module> AttributeError: attribute '__doc__' of 'type' objects is not writable --> type(Test) <class 'type'> --> class Meta(type): ... "only for exists to allow writable __doc__" ... --> class Test(metaclass=Meta): ... __doc__ = 'am I permanent?' ... --> Test.__doc__ 'am I permanent?' --> Test.__doc__ = 'No!' --> Test.__doc__ 'No!' --> type(Test) <class '__main__.Meta'> Should I create a bug report? ~Ethan~

11 16

Re: [Python-Dev] [Python-checkins] cpython (2.7): Issue #13605: add documentation for nargs=argparse.REMAINDER
by Sandro Tosi 19 Jan '12

19 Jan '12

On Thu, Jan 19, 2012 at 22:07, Terry Reedy <tjreedy(a)udel.edu> wrote: > typo ... > lits .> list yep, i've already fixed it committing a more useful example too -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi

1 0

Re: [Python-Dev] [Python-checkins] cpython (2.7): Issue #13605: add documentation for nargs=argparse.REMAINDER
by Nadeem Vawda 19 Jan '12

19 Jan '12

On Thu, Jan 19, 2012 at 11:03 PM, sandro.tosi <python-checkins(a)python.org> wrote: > + are gathered into a lits. This is commonly useful for command line s/lits/list ?

2 1

Re: [Python-Dev] [Python-checkins] cpython: add str.casefold() (closes #13752)
by Éric Araujo 19 Jan '12

19 Jan '12

Hi, > changeset: d4669f43d05f > user: Benjamin Peterson <benjamin(a)python.org> > date: Sat Jan 14 13:23:30 2012 -0500 > summary: > add str.casefold() (closes #13752) > diff --git a/Doc/library/stdtypes.rst b/Doc/library/stdtypes.rst > --- a/Doc/library/stdtypes.rst > +++ b/Doc/library/stdtypes.rst > @@ -1002,6 +1002,14 @@ > rest lowercased. > > > +.. method:: str.casefold() > + > + Return a casefolded copy of the string. Casefolded strings may be > used for > + caseless matching. For example, ``"MASSE".casefold() == > "maße".casefold()``. > + > + .. versionadded:: 3.3 I think this method requires at least a link to relevant definitions (Unicode website or Wikipedia), and at best a bit more explanation (for example, it is not locale-dependent, even though the example above is only meaningful for German). Cheers

1 1

Re: [Python-Dev] [Python-checkins] Daily reference leaks (12de1ad1cee8): sum=6024
by Nick Coghlan 19 Jan '12

19 Jan '12

On Wed, Jan 18, 2012 at 2:31 PM, <solipsis(a)pitrou.net> wrote: > results for 12de1ad1cee8 on branch "default" > -------------------------------------------- > > test_capi leaked [2008, 2008, 2008] references, sum=6024 Yikes, you weren't kidding about that new subinterpreter code execution test upsetting the refleak detection... Cheers, Nick. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

4 7