<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.python.bugs">
    <title>gmane.comp.python.bugs</title>
    <link>http://blog.gmane.org/gmane.comp.python.bugs</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215556"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215554"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215552"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215551"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215529"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215508"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215497"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215492"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215488"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215485"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215458"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215452"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215436"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215432"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215429"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215427"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215426"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215408"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215402"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.python.bugs/215396"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215556">
    <title>[issue18250] In itertools.repeat() object shadows object()</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215556</link>
    <description>&lt;pre&gt;
New submission from py.user:

&amp;lt;class 'object'&amp;gt;

----------
assignee: docs&amp;lt; at &amp;gt;python
components: Documentation
files: issue.diff
keywords: patch
messages: 191384
nosy: docs&amp;lt; at &amp;gt;python, py.user
priority: normal
severity: normal
status: open
title: In itertools.repeat() object shadows object()
type: enhancement
versions: Python 3.4
Added file: http://bugs.python.org/file30630/issue.diff

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18250&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>py.user</dc:creator>
    <dc:date>2013-06-18T01:16:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215554">
    <title>[issue18249] Incorrect and incomplete help docs for close() method</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215554</link>
    <description>&lt;pre&gt;
New submission from Dave Angel:

Python 3.3.0 (default, Mar  7 2013, 00:24:38) 
[GCC 4.6.3] on linux

q = open('/dev/null')
help(q.close)

the entire output is:
-------------------------------
Help on built-in function close:

close(...)
(END)
-------------------------------

But close() is NOT a built-in, it's a method.

(In Python 2.7.*  the output is:

-------------------------------
Help on built-in function close:

close(...)
    close() -&amp;gt; None or (perhaps) an integer.  Close the file.
    
    Sets data attribute .closed to True.  A closed file cannot be used for
    further I/O operations.  close() may be called more than once without
    error.  Some kinds of file objects (for example, opened by popen())
    may return an exit status upon closing.
(END)
-------------------------------
which is only partially wrong.

----------
assignee: docs&amp;lt; at &amp;gt;python
components: Documentation
messages: 191382
nosy: DaveA, docs&amp;lt; at &amp;gt;python
priority: normal
severity: normal
status: open
title: Incorrect and incomplete help docs for close() method

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18249&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>Dave Angel</dc:creator>
    <dc:date>2013-06-18T00:55:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215552">
    <title>[issue18248] fficonfig.py.in wrong for AIX</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215552</link>
    <description>&lt;pre&gt;
New submission from David Edelsohn:

fficonfig.py.in incorrectly mixes source files intended for Linux with source files intended for AIX, causing a build failure.

AIX uses ffi_darwin.c not ffi.c

diff -r f6f70f1ab124 Modules/_ctypes/libffi.diff
--- a/Modules/_ctypes/libffi.diff       Mon Jun 17 22:02:14 2013 +0200
+++ b/Modules/_ctypes/libffi.diff       Mon Jun 17 22:18:44 2013 -0700
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -135,7 +135,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 +    'M32R': ['src/m32r/sysv.S', 'src/m32r/ffi.c'],
 +    'M68K': ['src/m68k/ffi.c', 'src/m68k/sysv.S'],
 +    'POWERPC': ['src/powerpc/ffi.c', 'src/powerpc/sysv.S', 'src/powerpc/ppc_closure.S', 'src/powerpc/linux64.S', 'src/powerpc/linux64_closure.S'],
-+    'POWERPC_AIX': ['src/powerpc/ffi.c', 'src/powerpc/aix.S', 'src/powerpc/aix_closure.S'],
++    'POWERPC_AIX': ['src/powerpc/ffi_darwin.c', 'src/powerpc/aix.S', 'src/powerpc/aix_closure.S'],
 +    'POWERPC_FREEBSD': ['src/powerpc/ffi.c', 'src/powerpc/sysv.S', 'src/powerpc/ppc_closure.S'],
 +    'ARM': ['src/arm/sysv.S', 'src/arm/ffi.c'],
 +    'LIBFFI_CRIS': ['src/cris/sysv.S', 'src/cris/ffi.c'],
diff -r f6f70f1ab124 Modules/_ctypes/libffi/fficonfig.py.in
--- a/Modules/_ctypes/libffi/fficonfig.py.in    Mon Jun 17 22:02:14 2013 +0200
+++ b/Modules/_ctypes/libffi/fficonfig.py.in    Mon Jun 17 22:18:44 2013 -0700
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -16,7 +16,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
     'M32R': ['src/m32r/sysv.S', 'src/m32r/ffi.c'],
     'M68K': ['src/m68k/ffi.c', 'src/m68k/sysv.S'],
     'POWERPC': ['src/powerpc/ffi.c', 'src/powerpc/sysv.S', 'src/powerpc/ppc_closure.S', 'src/powerpc/linux64.S', 'src/powerpc/linux64_closure.S'],
-    'POWERPC_AIX': ['src/powerpc/ffi.c', 'src/powerpc/aix.S', 'src/powerpc/aix_closure.S'],
+    'POWERPC_AIX': ['src/powerpc/ffi_darwin.c', 'src/powerpc/aix.S', 'src/powerpc/aix_closure.S'],
     'POWERPC_FREEBSD': ['src/powerpc/ffi.c', 'src/powerpc/sysv.S', 'src/powerpc/ppc_closure.S'],
     'ARM': ['src/arm/sysv.S', 'src/arm/ffi.c'],
     'LIBFFI_CRIS': ['src/cris/sysv.S', 'src/cris/ffi.c'],

----------
components: Extension Modules
messages: 191381
nosy: David.Edelsohn
priority: normal
severity: normal
status: open
title: fficonfig.py.in wrong for AIX
type: behavior
versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18248&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>David Edelsohn</dc:creator>
    <dc:date>2013-06-18T00:20:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215551">
    <title>[issue18247] Add Lib/test/data/ to .gitignore</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215551</link>
    <description>&lt;pre&gt;
New submission from py.user:

have a git repository:
http://docs.python.org/devguide/faq.html#i-already-know-how-to-use-git-can-i-use-that-instead
git clone git://github.com/akheron/cpython

after running tests by "make test" they created some files in "Lib/test/data/"


[guest&amp;lt; at &amp;gt;localhost cpython]$ git st
# On branch master
# Changes to be committed:
#   (use "git reset HEAD &amp;lt;file&amp;gt;..." to unstage)
#
#       modified:   Doc/library/itertools.rst
#
# Changes not staged for commit:
#   (use "git add &amp;lt;file&amp;gt;..." to update what will be committed)
#   (use "git checkout -- &amp;lt;file&amp;gt;..." to discard changes in working directory)
#
#       modified:   Modules/itertoolsmodule.c
#
# Untracked files:
#   (use "git add &amp;lt;file&amp;gt;..." to include in what will be committed)
#
#       Lib/test/data/BIG5.TXT
#       Lib/test/data/BIG5HKSCS-2004.TXT
#       Lib/test/data/CP932.TXT
#       Lib/test/data/CP936.TXT
#       Lib/test/data/CP949.TXT
#       Lib/test/data/CP950.TXT
#       Lib/test/data/EUC-CN.TXT
#       Lib/test/data/EUC-JISX0213.TXT
#       Lib/test/data/EUC-JP.TXT
#       Lib/test/data/EUC-KR.TXT
#       Lib/test/data/JOHAB.TXT
#       Lib/test/data/NamedSequences.txt
#       Lib/test/data/NormalizationTest.txt
#       Lib/test/data/SHIFTJIS.TXT
#       Lib/test/data/SHIFT_JISX0213.TXT
#       Lib/test/data/gb-18030-2000.xml
[guest&amp;lt; at &amp;gt;localhost cpython]$

----------
components: Build, Devguide
messages: 191380
nosy: ezio.melotti, py.user
priority: normal
severity: normal
status: open
title: Add Lib/test/data/ to .gitignore
type: enhancement
versions: Python 3.4

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18247&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>py.user</dc:creator>
    <dc:date>2013-06-17T23:41:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215529">
    <title>[issue18246] tkinter.Text() add a newline to the content - bug?</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215529</link>
    <description>&lt;pre&gt;
New submission from Friedrich Spee von Langenfeld:

Python 3.3.2 (v3.3.2:d047928ae3f6, May 16 2013, 00:06:53) [MSC v.1600 64 bit (AMD64)] on win32
Type "copyright", "credits" or "license()" for more information.
'Hello\n'

The tkinter.Text() widget add a newline (\n) to its content. Is this behavior a bug?

----------
components: Tkinter
messages: 191370
nosy: Friedrich.Spee.von.Langenfeld
priority: normal
severity: normal
status: open
title: tkinter.Text() add a newline to the content - bug?
versions: Python 3.3

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18246&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>Friedrich Spee von Langenfeld</dc:creator>
    <dc:date>2013-06-17T20:04:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215508">
    <title>[issue18245] In itertools.groupby() make data plural</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215508</link>
    <description>&lt;pre&gt;
New submission from py.user:

http://en.wiktionary.org/wiki/data
"data (uncountable) or plural noun"

----------
assignee: docs&amp;lt; at &amp;gt;python
components: Documentation
files: issue.diff
keywords: patch
messages: 191354
nosy: docs&amp;lt; at &amp;gt;python, py.user
priority: normal
severity: normal
status: open
title: In itertools.groupby() make data plural
versions: Python 3.3, Python 3.4
Added file: http://bugs.python.org/file30624/issue.diff

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18245&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>py.user</dc:creator>
    <dc:date>2013-06-17T18:33:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215497">
    <title>[issue18244] singledispatch: When virtual-inheriting ABCs at distinctpoints in MRO, composed MRO is dependent on haystack ordering</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215497</link>
    <description>&lt;pre&gt;
New submission from Edward Catmur:

Suppose we have a class C with MRO (C, B, A, object).  C virtual-inherits an ABC V, while B virtual-inherits an unrelated ABC W:

       object
      /   |  \
      A   W  |
      | .`  /
      B`  V
      | .`
      C`

Recalling that per PEP 443 singledispatch prefers concrete bases to virtual bases, we would expect the following composed MRO:

    C, B, V, A, W, object

However what actually happens is the composed MRO depends on the order of the haystack; if W is processed first the result is correct, but if V is processed first then (because V does not subclass W) W is inserted in the MRO *before* V:

    C, B, A, object
    C, B, V, A, object
    C, B, W, V, A, object

This results in ambiguity between V and W.

Suggested fix is a slight change to the MRO composition algorithm, considering whether the items already placed in the MRO are concrete base classes.

----------
components: Extension Modules
hgrepos: 200
messages: 191350
nosy: ecatmur
priority: normal
severity: normal
status: open
title: singledispatch: When virtual-inheriting ABCs at distinct points in MRO, composed MRO is dependent on haystack ordering
versions: Python 3.4

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18244&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>Edward Catmur</dc:creator>
    <dc:date>2013-06-17T17:34:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215492">
    <title>[issue18243] mktime_tz documentation out-of-date</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215492</link>
    <description>&lt;pre&gt;
New submission from Jakub Wilk:

email.utils.mktime_tz documentations says:
"Minor deficiency: mktime_tz() interprets the first 8 elements of tuple as a local time and then compensates for the timezone difference. This may yield a slight error around changes in daylight savings time, though not worth worrying about for common use."

But now that issue #14653 is fixed, this is no longer true.

----------
assignee: docs&amp;lt; at &amp;gt;python
components: Documentation
messages: 191346
nosy: docs&amp;lt; at &amp;gt;python, jwilk
priority: normal
severity: normal
status: open
title: mktime_tz documentation out-of-date

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18243&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>Jakub Wilk</dc:creator>
    <dc:date>2013-06-17T15:24:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215488">
    <title>[issue18242] IDLE should not be replacing warnings.formatwarning</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215488</link>
    <description>&lt;pre&gt;
New submission from Brett Cannon:

Both idlelib.run and idlelib.PyShell replace warning.formatwarning which is a no-no. Only warning.showwarning is design to be replaced in any way. The proper solution is to replace warnings.showwarning with code that calls whatever formatting function you provide.

----------
components: IDLE
messages: 191344
nosy: brett.cannon
priority: normal
severity: normal
stage: needs patch
status: open
title: IDLE should not be replacing warnings.formatwarning
type: behavior
versions: Python 3.4

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18242&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>Brett Cannon</dc:creator>
    <dc:date>2013-06-17T14:59:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215485">
    <title>[issue18241] Add unique option to heapq functions</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215485</link>
    <description>&lt;pre&gt;
New submission from Antoine Pitrou:

In one application, I would like to use a heap as an allocation pool. I also want to check that a given value isn't released twice, therefore that the heap contains unique values. My use case would be solved nicely if heappush() took an optional "unique=False" parameter.

Note that I haven't checked if doing so is possible while maintaining the O(log n) complexity :-)

----------
messages: 191341
nosy: pitrou, rhettinger
priority: low
severity: normal
status: open
title: Add unique option to heapq functions
type: enhancement
versions: Python 3.4

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18241&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>Antoine Pitrou</dc:creator>
    <dc:date>2013-06-17T14:44:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215458">
    <title>[issue18240] hmac unnecessarily restricts input to "bytes"</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215458</link>
    <description>&lt;pre&gt;
New submission from Jonas Borgström:

Problem:
In hmac.py there's a type check that verifies that the msg parameter is of type bytes().

if not isinstance(msg, bytes):
    raise TypeError("expected bytes, but got %r" % type(msg).__name__)

That is incorrect. The hmac module should also work with other data types as long as they are supported by the underlying hashlib module, for example bytearray() and memoryview().

Suggestion:
Remove that type check. hashlib will make sure str() and other invalid data types raises a TypeError.

----------
components: Library (Lib)
messages: 191321
nosy: jborg
priority: normal
severity: normal
status: open
title: hmac unnecessarily restricts input to "bytes"
type: behavior
versions: Python 3.3

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18240&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org

&lt;/pre&gt;</description>
    <dc:creator>Jonas Borgström</dc:creator>
    <dc:date>2013-06-17T10:38:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215452">
    <title>[issue18239] In itertools docstring update arguments in count()example</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215452</link>
    <description>&lt;pre&gt;
New submission from py.user:

Functional tools for creating and using iterators.

Infinite iterators:
count([n]) --&amp;gt; n, n+1, n+2, ...

...

----------
assignee: docs&amp;lt; at &amp;gt;python
components: Documentation, Library (Lib)
files: issue.patch
keywords: patch
messages: 191317
nosy: docs&amp;lt; at &amp;gt;python, py.user
priority: normal
severity: normal
status: open
title: In itertools docstring update arguments in count() example
type: enhancement
versions: Python 3.3, Python 3.4
Added file: http://bugs.python.org/file30617/issue.patch

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18239&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>py.user</dc:creator>
    <dc:date>2013-06-17T07:04:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215436">
    <title>[issue18238] test_signal.py wait_helper hangs on AIX</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215436</link>
    <description>&lt;pre&gt;
New submission from David Edelsohn:

test_signal.py wait_helper hangs on AIX.  Please skip the test on AIX for now to allow all other tests to run to completion.

diff -r bdd60bedf933 Lib/test/test_signal.py
--- a/Lib/test/test_signal.py   Sun Jun 16 18:37:53 2013 -0400
+++ b/Lib/test/test_signal.py   Mon Jun 17 00:10:01 2013 -0700
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -593,6 +593,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
         """
         assert_python_ok('-c', code)
 
+    &amp;lt; at &amp;gt;unittest.skipIf(sys.platform == "aix7", "Test hangs on AIX")
     &amp;lt; at &amp;gt;unittest.skipUnless(hasattr(signal, 'pthread_sigmask'),
                          'need signal.pthread_sigmask()')
     def wait_helper(self, blocked, test):

----------
components: Tests
messages: 191310
nosy: David.Edelsohn
priority: normal
severity: normal
status: open
title: test_signal.py wait_helper hangs on AIX
type: behavior
versions: Python 3.5

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18238&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>David Edelsohn</dc:creator>
    <dc:date>2013-06-17T02:12:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215432">
    <title>[issue18237] unittest.assertRaisesRegex(p) example is wrong in docs</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215432</link>
    <description>&lt;pre&gt;
New submission from Jeff Tratner:

One of the examples for assertRaisesRegex(p) is wrong by one character.

Current is:

self.assertRaisesRegexp(ValueError, 'invalid literal for.*XYZ$',
                        int, 'XYZ')

The $ at the end is wrong because the actual error message is "ValueError: invalid literal for int() with base 10: 'XYZ'" (with a ``'`` at the end).  Two options for fixing.

Option 1 - remove $
self.assertRaisesRegexp(ValueError, 'invalid literal for.*XYZ',
                        int, 'XYZ')
Option 2 - add '

self.assertRaisesRegexp(ValueError, 'invalid literal for.*XYZ\'$',
                        int, 'XYZ')

Same example is shown for assertRaisesRegex, so applies to both.

And for completeness...here's something you can run to see the error [couldn't figure out how to attach two files]:

import unittest
class MyTest(unittest.TestCase):
    def test_example(self):
        # this fails
        self.assertRaisesRegexp(ValueError, 'invalid literal for.*XYZ$',
                        int, 'XYZ')
    def test_option1(self):
        self.assertRaisesRegexp(ValueError, 'invalid literal for.*XYZ',
                                int, 'XYZ')
    def test_option2(self):
        self.assertRaisesRegexp(ValueError, 'invalid literal for.*XYZ\'$',
                                int, 'XYZ')

unittest.main()

----------
assignee: docs&amp;lt; at &amp;gt;python
components: Documentation
files: unittest.patch
keywords: patch
messages: 191306
nosy: docs&amp;lt; at &amp;gt;python, jtratner
priority: normal
severity: normal
status: open
title: unittest.assertRaisesRegex(p) example is wrong in docs
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5
Added file: http://bugs.python.org/file30615/unittest.patch

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18237&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>Jeff Tratner</dc:creator>
    <dc:date>2013-06-17T01:34:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215429">
    <title>[issue18236] int() and float() do not accept strings with trailingseparators</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215429</link>
    <description>&lt;pre&gt;
New submission from Alexander Belopolsky:

ASCII information separators, hex codes 1C through 1F are classified as space:

True

but int()/float() do not accept strings with leading or trailing separators:

Traceback (most recent call last):
  File "&amp;lt;stdin&amp;gt;", line 1, in &amp;lt;module&amp;gt;
ValueError: invalid literal for int() with base 10: '123\x1e'

This is probably because corresponding bytes values are not classified as whitespace:

False

----------
messages: 191303
nosy: belopolsky
priority: normal
severity: normal
status: open
title: int() and float() do not accept strings with trailing separators
type: behavior

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18236&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>Alexander Belopolsky</dc:creator>
    <dc:date>2013-06-17T01:06:30</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215427">
    <title>[issue18235] _sysconfigdata.py wrong on AIX installations</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215427</link>
    <description>&lt;pre&gt;
New submission from David Edelsohn:

_sysconfigdata.py includes information about how to build extension modules. On AIX this requires a wrapper script to build shared libraries.  The file includes definitions like:

 'BLDSHARED': './Modules/ld_so_aix gcc -pthread -bI:./Modules/python.exp',
 'LDSHARED': './Modules/ld_so_aix gcc -pthread -bI:./Modules/python.exp',
 'LINKCC': './Modules/makexp_aix Modules/python.exp . libpython3.4dm.a;  gcc '
           '-pthread',
 'MAKESETUP': './Modules/makesetup',

which is correct in the build directory, but is not correct for the install directory.  The paths do not correspond to the installed location of ld_so_aix and makexp_aix in lib/pythonX.Y/config .

----------
components: Extension Modules
messages: 191301
nosy: David.Edelsohn
priority: normal
severity: normal
status: open
title: _sysconfigdata.py wrong on AIX installations
type: behavior
versions: Python 3.5

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18235&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>David Edelsohn</dc:creator>
    <dc:date>2013-06-17T00:33:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215426">
    <title>[issue18234] Unicodedata module should provide access to codepointaliases</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215426</link>
    <description>&lt;pre&gt;
New submission from Alexander Belopolsky:

Python is aware of unicode codepoint aliases, but unicodedata does not provide a way to find aliases of a given codepoint:

True
True

but

Traceback (most recent call last):
  File "&amp;lt;stdin&amp;gt;", line 1, in &amp;lt;module&amp;gt;
ValueError: no such name


Traceback (most recent call last):
  File "&amp;lt;stdin&amp;gt;", line 1, in &amp;lt;module&amp;gt;
ValueError: no such name

----------
messages: 191300
nosy: belopolsky
priority: normal
severity: normal
status: open
title: Unicodedata module should provide access to codepoint aliases
type: enhancement
versions: Python 3.4

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18234&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>Alexander Belopolsky</dc:creator>
    <dc:date>2013-06-17T00:24:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215408">
    <title>[issue18233] SSLSocket.getpeercertchain()</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215408</link>
    <description>&lt;pre&gt;
New submission from Christian Heimes:

The patch implements a method getpeercertchain() on a SSLSocket. It returns the peer's certificate chain from the leaf cert to the root cert if available. It wraps SSL_get_peer_cert_chain().

SSL_get_peer_cert_chain() doesn't have to pull any additional data from the peer. The information is already exchanged for cert validation.

----------
files: ssl_peerchertchain.patch
keywords: patch
messages: 191287
nosy: christian.heimes
priority: normal
severity: normal
stage: patch review
status: open
title: SSLSocket.getpeercertchain()
type: enhancement
versions: Python 3.4
Added file: http://bugs.python.org/file30611/ssl_peerchertchain.patch

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18233&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>Christian Heimes</dc:creator>
    <dc:date>2013-06-16T20:39:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215402">
    <title>[issue18232] running a suite with no tests is not an error</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215402</link>
    <description>&lt;pre&gt;
New submission from Robert Collins:

In bug https://bugs.launchpad.net/subunit/+bug/586176 I recorded a user request - that if no tests are found, tools consuming subunit streams should be able to consider that an error.

There is an analogous situation though, which is that if discover returns without error, running the resulting suite is worthless, as it has no tests. This is a bit of a sliding slope - what if discover finds one test when there should be 1000's ? 

Anyhow, filing this because there's been a few times when things have gone completely wrong that it would have helped CI systems detect that. (For instance, the tests package missing entirely, but tests were being scanned in the whole source tree, so no discover level error occurred).

I'm thinking I'll add a '--min-tests=X' parameter to unittest.main, with the semantic that if there are less than X tests executed, the test run will be considered a failure, and folk can set this to 1 for the special case, or any arbitrary figure that they want for larger suites.

----------
messages: 191282
nosy: michael.foord, rbcollins
priority: normal
severity: normal
status: open
title: running a suite with no tests is not an error

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18232&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>Robert Collins</dc:creator>
    <dc:date>2013-06-16T19:32:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215396">
    <title>[issue18231] What's new in Python should explain what's new in UCD</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215396</link>
    <description>&lt;pre&gt;
New submission from Alexander Belopolsky:

At the minimum, we should refer to unicode.org:

http://www.unicode.org/versions/Unicode6.1.0/#Database_Changes (for Python 3.3),
http://www.unicode.org/versions/Unicode6.2.0/#Database_Changes (for Python 3.4).

We may also want to highlight changes that directly affect python programs.  For example addition of new characters accepted as decimal digits in UCD 6.1.0.

----------
assignee: docs&amp;lt; at &amp;gt;python
messages: 191278
nosy: belopolsky, docs&amp;lt; at &amp;gt;python
priority: normal
severity: normal
status: open
title: What's new in Python should explain what's new in UCD
versions: Python 3.3, Python 3.4

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18231&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>Alexander Belopolsky</dc:creator>
    <dc:date>2013-06-16T18:10:53</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.python.bugs/215384">
    <title>[issue18230] test_builtin fails/hangs when run after test_getopt</title>
    <link>http://comments.gmane.org/gmane.comp.python.bugs/215384</link>
    <description>&lt;pre&gt;
New submission from Brett Cannon:

If you run test_builtin after test_getopt it will hang. If you run test_getopt test_socket test_builtin it will fail in all tty-related tests for input().

Not sure if this is related to issue #17734 or #13886.

----------
components: Library (Lib)
messages: 191270
nosy: brett.cannon
priority: normal
severity: normal
stage: needs patch
status: open
title: test_builtin fails/hangs when run after test_getopt
type: behavior
versions: Python 3.3, Python 3.4

_______________________________________
Python tracker &amp;lt;report&amp;lt; at &amp;gt;bugs.python.org&amp;gt;
&amp;lt;http://bugs.python.org/issue18230&amp;gt;
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/python-python-bugs-list%40m.gmane.org


&lt;/pre&gt;</description>
    <dc:creator>Brett Cannon</dc:creator>
    <dc:date>2013-06-16T15:17:40</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.python.bugs">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.python.bugs</link>
  </textinput>
</rdf:RDF>
