From report at bugs.python.org  Tue Dec  1 00:31:34 2015
From: report at bugs.python.org (Martin Panter)
Date: Tue, 01 Dec 2015 05:31:34 +0000
Subject: [New-bugs-announce] [issue25771] importlib: '.submodule' is not a
 relative name (no leading dot)
Message-ID: <1448947894.1.0.971575571341.issue25771@psf.upfronthosting.co.za>


New submission from Martin Panter:

>>> import importlib.util
>>> importlib.util.resolve_name(".submodule", None)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/proj/python/cpython/Lib/importlib/util.py", line 26, in resolve_name
    '(no leading dot)'.format(name))
ValueError: '.submodule' is not a relative name (no leading dot)

This message sounds like nonsense. Perhaps the it should say something like:

    '.submodule' should be an absolute name (no leading dot)

or:

    relative import of '.submodule' not allowed outside of a package

----------
keywords: easy
messages: 255642
nosy: martin.panter
priority: normal
severity: normal
status: open
title: importlib: '.submodule' is not a relative name (no leading dot)
type: behavior
versions: Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25771>
_______________________________________

From report at bugs.python.org  Tue Dec  1 03:02:50 2015
From: report at bugs.python.org (Juchen Zeng)
Date: Tue, 01 Dec 2015 08:02:50 +0000
Subject: [New-bugs-announce] [issue25772] Misleading descriptions about
 built-in type `super.`
Message-ID: <1448956970.84.0.677978683679.issue25772@psf.upfronthosting.co.za>


New submission from Juchen Zeng:

A few days ago, I was learning built-in type `super` through [python official doc](https://docs.python.org/2/library/functions.html#super).  
And I was mislead by its documentation, in the part of how `__mro__` resolution works. Below is the part which confuse me:

"""
super(type[, object-or-type])

# ISSUE IRRELEVANT DOC OMITTED

The __mro__ attribute of the type lists the method resolution search order used by both getattr() and super(). The attribute is dynamic and can change whenever the inheritance hierarchy is updated.
"""

>From the description of the doc we can see that `super()` takes two arguments, the first is `type` and the second is an optional `object-or-type`. So, when I saw the doc statement: `The __mro__ attribute of the type lists the method resolution search order used by both getattr() and super(). `, I naturally thought here the `type` refers to the compulsory first `type` argument. But after doing a series of [experiments][EXP_REF]. It turns out in `super()` was using the second `type`'s `__mro__` attribute! And if the second argument is an object, it will use `object.__class__.__mro__` as its resolution order. Unless a learner experimented it throughly like me, he will have lots of difficulty to figured out that `type` mentioned in the doc refers to the second optional argument. I think here the doc should be clearly specified that the second argument's `__mro__` is what super relies on. I suggest to add distinctions on arguments name or add more clarification informations in the doc here.

By the way, the python3 document has the same issue.  
If you decided to fix this, maybe you want to fix its python3 version, too.

 

[EXP_REF]: http://stackoverflow.com/questions/33890918/how-does-super-interacts-with-a-classs-mro-attribute-in-multiple-inheri/33891281#33891281

----------
assignee: docs at python
components: Documentation
messages: 255643
nosy: Juchen Zeng, docs at python, eric.araujo, ezio.melotti, georg.brandl
priority: normal
severity: normal
status: open
title: Misleading descriptions about built-in type `super.`
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25772>
_______________________________________

From report at bugs.python.org  Tue Dec  1 10:44:28 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 01 Dec 2015 15:44:28 +0000
Subject: [New-bugs-announce] [issue25773] Deprecate deleting with
 PyObject_SetAttr, PyObject_SetAttrString and PySequence_SetItem
Message-ID: <1448984668.36.0.0444302662987.issue25773@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

If the third argument of PyObject_SetAttr(), PyObject_SetAttrString() or PySequence_SetItem() is NULL, these functions delete an attribute or an item. This is rather undocumented implementation detail. There are special counterparts for deleting:  PyObject_DelAttr(), PyObject_DelAttrString() and PySequence_DelItem(). May be worth to depre

Proposed patch deprecates using these Set* functions for deleting and replaces them with appropriate Del* functions if needed.

Discussion on Python-Dev: http://comments.gmane.org/gmane.comp.python.devel/155474

Issue that documents deleting with Set* APIs: issue25701.

----------
components: Interpreter Core
files: PyObject_SetAttr_deleting.patch
keywords: patch
messages: 255655
nosy: gvanrossum, martin.panter, ncoghlan, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Deprecate deleting with PyObject_SetAttr, PyObject_SetAttrString and PySequence_SetItem
type: enhancement
versions: Python 3.6
Added file: http://bugs.python.org/file41200/PyObject_SetAttr_deleting.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25773>
_______________________________________

From report at bugs.python.org  Tue Dec  1 13:31:55 2015
From: report at bugs.python.org (Zachary Ware)
Date: Tue, 01 Dec 2015 18:31:55 +0000
Subject: [New-bugs-announce] [issue25774] [benchmarks] Adjust to allow
 uploading benchmark data to codespeed
Message-ID: <1448994715.99.0.967922145164.issue25774@psf.upfronthosting.co.za>


New submission from Zachary Ware:

Here's a patch to the benchmarks repo that allows running a benchmark on a single interpreter and returning raw data, and provides a script to upload the raw data to a codespeed instance.  It's a bit of a quick hack, but is effective.

This is a prerequisite to getting speed.python.org running.

----------
components: Benchmarks
files: benchmarks.diff
hgrepos: 323
keywords: patch
messages: 255669
nosy: brett.cannon, pitrou, zach.ware
priority: normal
severity: normal
stage: patch review
status: open
title: [benchmarks] Adjust to allow uploading benchmark data to codespeed
type: enhancement
Added file: http://bugs.python.org/file41202/benchmarks.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25774>
_______________________________________

From report at bugs.python.org  Tue Dec  1 14:38:33 2015
From: report at bugs.python.org (Nicholas Chammas)
Date: Tue, 01 Dec 2015 19:38:33 +0000
Subject: [New-bugs-announce] [issue25775] Bug tracker emails go to spam
Message-ID: <1448998713.15.0.646298994549.issue25775@psf.upfronthosting.co.za>


New submission from Nicholas Chammas:

Not sure where to report this. Is there a component for the bug tracker itself?

Anyway, Gmail sends emails from this bug tracker to spam and flags each one with the following message:

> Why is this message in Spam? It is in violation of Google's recommended email sender guidelines.  Learn more
> https://support.google.com/mail/answer/81126?hl=en#authentication

Is this actionable? Is this a known issue?

----------
messages: 255676
nosy: Nicholas Chammas
priority: normal
severity: normal
status: open
title: Bug tracker emails go to spam
type: behavior

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25775>
_______________________________________

From report at bugs.python.org  Wed Dec  2 05:29:15 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 02 Dec 2015 10:29:15 +0000
Subject: [New-bugs-announce] [issue25776] More compact pickle of iterators
 etc
Message-ID: <1449052155.68.0.447852149746.issue25776@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Proposed patch makes a number of classes produce more compact pickle data in common case. This includes iterators of list, tuple, str, bytes, bytearray, enumerate, array, deque, iterator object for classes with __getitem__, some itertools iterators, and non-iterator objects: slice, bytearray, deque. This is achieved by omitting default constructor arguments or state.

Exhausted iterators are pickled as iter(()). This is not new, exhausted bytes, and bytearray iterators, and reversed list iterator are already pickled as iter('') or iter([]) correspondingly. iter(()) is just the simplest way to create an empty iterator and it has the most compact pickle representation.

An example.

Unpatched:
>>> import pickle, pickletools, itertools
>>> len(pickle.dumps(itertools.islice('abcdefgh', 4), 3))
80
>>> len(pickletools.optimize(pickle.dumps(itertools.islice('abcdefgh', 4), 3)))
66
>>> pickletools.dis(pickletools.optimize(pickle.dumps(itertools.islice('abcdefgh', 4), 3)))
    0: \x80 PROTO      3
    2: c    GLOBAL     'itertools islice'
   20: (    MARK
   21: c        GLOBAL     'builtins iter'
   36: X        BINUNICODE 'abcdefgh'
   49: \x85     TUPLE1
   50: R        REDUCE
   51: K        BININT1    0
   53: b        BUILD
   54: K        BININT1    0
   56: K        BININT1    4
   58: K        BININT1    1
   60: t        TUPLE      (MARK at 20)
   61: R    REDUCE
   62: K    BININT1    0
   64: b    BUILD
   65: .    STOP
highest protocol among opcodes = 2

Patched:
>>> len(pickle.dumps(itertools.islice('abcdefgh', 4), 3))
69
>>> len(pickletools.optimize(pickle.dumps(itertools.islice('abcdefgh', 4), 3)))
55
>>> pickletools.dis(pickletools.optimize(pickle.dumps(itertools.islice('abcdefgh', 4), 3)))
    0: \x80 PROTO      3
    2: c    GLOBAL     'itertools islice'
   20: c    GLOBAL     'builtins iter'
   35: X    BINUNICODE 'abcdefgh'
   48: \x85 TUPLE1
   49: R    REDUCE
   50: K    BININT1    4
   52: \x86 TUPLE2
   53: R    REDUCE
   54: .    STOP
highest protocol among opcodes = 2

----------
components: Extension Modules, Interpreter Core
files: iterators_pickle.diff
keywords: patch
messages: 255699
nosy: alexandre.vassalotti, pitrou, rhettinger, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: More compact pickle of iterators etc
type: enhancement
versions: Python 3.6
Added file: http://bugs.python.org/file41207/iterators_pickle.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25776>
_______________________________________

From report at bugs.python.org  Wed Dec  2 07:22:21 2015
From: report at bugs.python.org (Juchen Zeng)
Date: Wed, 02 Dec 2015 12:22:21 +0000
Subject: [New-bugs-announce] [issue25777] Misleading descriptions in docs
 about invoking descriptors.
Message-ID: <1449058941.53.0.26351823319.issue25777@psf.upfronthosting.co.za>


New submission from Juchen Zeng:

[Doc Link](https://docs.python.org/2/howto/descriptor.html#invoking-descriptors)

In descriptions about how to invoke descriptors with super(), it says:

    The call super(B, obj).m() searches obj.__class__.__mro__ for the base class A immediately following B and then returns A.__dict__['m'].__get__(obj, B). If not a descriptor, m is returned unchanged. If not in the dictionary, m reverts to a search using object.__getattribute__().

But the call ` super(B, obj).m()` will not return `A.__dict__['m'].__get__(obj, B)`, it will trigger the `__call__` method of ` A.__dict__['m'].__get__(obj, B)` if it has that attr, and return what this `__call__` method returns.  It could be anything.
It's actually `super(B, obj).m` returns `A.__dict__['m'].__get__(obj, B)` if m is a descriptor.

In short, the original description in the doc can be abbreviated to:
`The call super(B, obj).m() [did something] and returns A.__dict__['m'].__get__(obj, B).`
Which is obviously misleading.

As the method/function call isn't the core part in this sentence. I suggest the doc to be fixed like this:

    The action super(B, obj).m searches obj.__class__.__mro__ for the base class A immediately following B and then returns A.__dict__['m'].__get__(obj, B).

----------
assignee: docs at python
components: Documentation
messages: 255712
nosy: Juchen Zeng, docs at python, martin.panter
priority: normal
severity: normal
status: open
title: Misleading descriptions in docs about invoking descriptors.
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25777>
_______________________________________

From report at bugs.python.org  Wed Dec  2 08:55:25 2015
From: report at bugs.python.org (Anshul Agrawal)
Date: Wed, 02 Dec 2015 13:55:25 +0000
Subject: [New-bugs-announce] [issue25778] Error on import matplotlib.pyplot
 and seaborn (Python3 - Windows 10 64-bit issue)
Message-ID: <1449064525.57.0.047427517368.issue25778@psf.upfronthosting.co.za>


New submission from Anshul Agrawal:

I have described the error message I got when I recently installed Python 3.5.0 (via Anaconda3) and then subsequently tried to import mathplotlib.pyplot and seaborn packages at this StackOverflow post (http://stackoverflow.com/questions/34004063/error-on-import-matplotlib-pyplot-on-anaconda3-for-windows-10-home-64-bit-pc)

Another person responded to the above post with a simple 1-line patch to the file "fontList.py3k.cache" (please see the above post for details).

This does appear to be a purely Python 3 issue on some Windows platforms. It would be nice if Python 3 developers could check the patch out for any possible side-effects, and incorporate a permanent fix in future versions.  Thanks.

----------
components: Extension Modules
messages: 255715
nosy: anshul6
priority: normal
severity: normal
status: open
title: Error on import matplotlib.pyplot and seaborn (Python3 - Windows 10 64-bit issue)
type: behavior
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25778>
_______________________________________

From report at bugs.python.org  Wed Dec  2 10:37:25 2015
From: report at bugs.python.org (Jack O'Connor)
Date: Wed, 02 Dec 2015 15:37:25 +0000
Subject: [New-bugs-announce] [issue25779] deadlock with
 asyncio+contextmanager+ExitStack
Message-ID: <1449070645.76.0.674051861514.issue25779@psf.upfronthosting.co.za>


New submission from Jack O'Connor:

The following hangs at 100% CPU on Python 3.5, though not on Python 3.4:

1) Start an asyncio coroutine with run_until_complete().
2) Inside the coroutine, enter an ExitStack using a with-statement.
3) Inside the with-statement, call ExitStack.enter_context() with a generator context manager. It doesn't matter what the generator yields.
4) After the enter_context() call, raise an exception.

Here's an example script that does all of this and repros the hang: https://gist.github.com/oconnor663/483db2820bb5f877c9ed

----------
components: asyncio
messages: 255719
nosy: gvanrossum, haypo, oconnor663, yselivanov
priority: normal
severity: normal
status: open
title: deadlock with asyncio+contextmanager+ExitStack
type: behavior
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25779>
_______________________________________

From report at bugs.python.org  Wed Dec  2 11:40:47 2015
From: report at bugs.python.org (Stefan Tatschner)
Date: Wed, 02 Dec 2015 16:40:47 +0000
Subject: [New-bugs-announce] [issue25780] Add support for
 CAN_RAW_JOIN_FILTERS
Message-ID: <1449074447.29.0.213464499345.issue25780@psf.upfronthosting.co.za>


New submission from Stefan Tatschner:

Here is a patch, which adds support for CAN_RAW_JOIN_FILTERS which is available since linux 4.1 [1]. My patch fixes trailing whitespace issues as well. Since I have a newer version of autotools, running "autoreconf" generates a lot of changes, so I left that out for the time being.

[1]: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a5581ef4c2eac6449188862e903eb46c7233582a

----------
components: Library (Lib)
files: can_raw_join_filters.diff
keywords: patch
messages: 255723
nosy: rumpelsepp
priority: normal
severity: normal
status: open
title: Add support for CAN_RAW_JOIN_FILTERS
versions: Python 3.6
Added file: http://bugs.python.org/file41210/can_raw_join_filters.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25780>
_______________________________________

From report at bugs.python.org  Wed Dec  2 12:01:44 2015
From: report at bugs.python.org (Yury Selivanov)
Date: Wed, 02 Dec 2015 17:01:44 +0000
Subject: [New-bugs-announce] [issue25781] infinite loop in reprlib
Message-ID: <1449075704.09.0.711720305555.issue25781@psf.upfronthosting.co.za>


New submission from Yury Selivanov:

The below code blocks Python eval loop and makes it unresponsive to signals (like ^C).

    import reprlib

    try:
        raise RuntimeError
    except RuntimeError as ex:
        ex.__context__ = ex
        reprlib.repr(ex)

----------
components: Library (Lib)
messages: 255727
nosy: yselivanov
priority: normal
severity: normal
status: open
title: infinite loop in reprlib
versions: Python 3.3, Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25781>
_______________________________________

From report at bugs.python.org  Wed Dec  2 12:14:01 2015
From: report at bugs.python.org (Yury Selivanov)
Date: Wed, 02 Dec 2015 17:14:01 +0000
Subject: [New-bugs-announce] [issue25782] CPython hangs on error __context__
 set to the error itself
Message-ID: <1449076441.38.0.963505882098.issue25782@psf.upfronthosting.co.za>


New submission from Yury Selivanov:

try:
    raise Exception
except Exception as ex:
    ex.__context__ = ex
    hasattr(1, 'aa')

----------
components: Interpreter Core
messages: 255731
nosy: gvanrossum, haypo, ncoghlan, yselivanov
priority: normal
severity: normal
status: open
title: CPython hangs on error __context__ set to the error itself
versions: Python 3.3, Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25782>
_______________________________________

From report at bugs.python.org  Wed Dec  2 12:44:33 2015
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Dec 2015 17:44:33 +0000
Subject: [New-bugs-announce] [issue25783] test_traceback.test_walk_stack()
 fails when run directly (without regrtest)
Message-ID: <1449078273.26.0.535537969115.issue25783@psf.upfronthosting.co.za>


New submission from STINNER Victor:

Tested on Python 3.6 (default branch):

haypo at smithers$ ./python -m test test_traceback
[1/1] test_traceback
1 test OK.

haypo at smithers$ ./python Lib/test/test_traceback.py 
..........................................F...............
======================================================================
FAIL: test_walk_stack (__main__.TestStack)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "Lib/test/test_traceback.py", line 684, in test_walk_stack
    self.assertGreater(len(s), 10)
AssertionError: 10 not greater than 10

----------------------------------------------------------------------
Ran 58 tests in 2.184s

FAILED (failures=1)

----------
components: Tests
messages: 255737
nosy: haypo
priority: normal
severity: normal
status: open
title: test_traceback.test_walk_stack() fails when run directly (without regrtest)
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25783>
_______________________________________

From report at bugs.python.org  Wed Dec  2 12:54:16 2015
From: report at bugs.python.org (Alexander Finkel)
Date: Wed, 02 Dec 2015 17:54:16 +0000
Subject: [New-bugs-announce] [issue25784] Please consider integrating
 performance fix for ipaddress.py
Message-ID: <1449078856.21.0.545889486519.issue25784@psf.upfronthosting.co.za>


New submission from Alexander Finkel:

I encountered a performance problem using the ipaddr library to merge over 10000 network addresses. I sent a patch upstream to fix it, and that patch has been merged:
https://github.com/google/ipaddr-py/commit/6504b47a02739e853043f0a184f3c39462293e5c

Since ipaddr is also included in the standard lib of Python 3 (I think since version 3.3?) and above, I'd like to ask that this patch be considered for committing here too.

Background on including ipaddr into the std lib: https://bugs.python.org/issue14814

----------
messages: 255741
nosy: Alexander Finkel
priority: normal
severity: normal
status: open
title: Please consider integrating performance fix for ipaddress.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25784>
_______________________________________

From report at bugs.python.org  Wed Dec  2 14:27:52 2015
From: report at bugs.python.org (Felipe Cruz)
Date: Wed, 02 Dec 2015 19:27:52 +0000
Subject: [New-bugs-announce] [issue25785] TimedRotatingFileHandler missing
 rotations
Message-ID: <1449084472.03.0.0629669508216.issue25785@psf.upfronthosting.co.za>


New submission from Felipe Cruz:

I'm using TimedRotatingFileHandler to rotate a log file *every* minute.

If I stop my program, in the middle of a minute, and start again, the next rotation will happen at (currentTime + 60). The result of this behavior is that I'll end up with files "log_01" and "log_03", instead of "log_01", "log_02" and "log_03".

I'm using this class with a little modification which sets the next rollover 
time to (currentTime + (self.interval - currentSecond)). In this case, even If I stop and start my program in the middle a minute, the next rollover time will be the end of the current minute, not 60 seconds later and the result will be one file for each minute.

To sum up, what happen is that the same program with the very same configuration, produces a different result if stopped for even just one second. If the interval was "rotate every 60 seconds" I would be ok, but If I'm configuring to rotate every minute I expect one file for each minute if the program was running the time the minutes changed.

----------
messages: 255757
nosy: felipecruz
priority: normal
severity: normal
status: open
title: TimedRotatingFileHandler missing rotations
type: behavior
versions: Python 2.7, Python 3.4, Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25785>
_______________________________________

From report at bugs.python.org  Wed Dec  2 14:58:45 2015
From: report at bugs.python.org (Yury Selivanov)
Date: Wed, 02 Dec 2015 19:58:45 +0000
Subject: [New-bugs-announce] [issue25786] contextlib.ExitStack introduces a
 cycle in exception __context__
Message-ID: <1449086325.2.0.703552973067.issue25786@psf.upfronthosting.co.za>


New submission from Yury Selivanov:

See http://bugs.python.org/issue25779 and http://bugs.python.org/issue25782 for details.

----------
components: Library (Lib)
messages: 255762
nosy: gvanrossum, ncoghlan, serhiy.storchaka, yselivanov
priority: release blocker
severity: normal
status: open
title: contextlib.ExitStack introduces a cycle in exception __context__
versions: Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25786>
_______________________________________

From report at bugs.python.org  Wed Dec  2 22:29:39 2015
From: report at bugs.python.org (Karl Richter)
Date: Thu, 03 Dec 2015 03:29:39 +0000
Subject: [New-bugs-announce] [issue25787] Add an explanation what happens
 with subprocess parent and child processes when signals are sent
Message-ID: <1449113379.93.0.748465414277.issue25787@psf.upfronthosting.co.za>


New submission from Karl Richter:

The [documentation of subprocess](https://docs.python.org/3.6/library/subprocess.html) doesn't contain a substantial statement how signals are handled which are send to the python interpreter. After reading the referenced docs it should be clear

  * whether a signal is passed to both the parent and the child (If yes in which order? What happens if the child process spawns a process which isn't controlled by python?)
  * whether signal handlers are inherited (judging from the `restore_signals` parameter some are overwritten -> what's the purpose of this?). Are changes of a signal handler in the parent reflected in the child?

----------
assignee: docs at python
components: Documentation
messages: 255802
nosy: docs at python, krichter
priority: normal
severity: normal
status: open
title: Add an explanation what happens with subprocess parent and child processes when signals are sent
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25787>
_______________________________________

From report at bugs.python.org  Thu Dec  3 11:41:30 2015
From: report at bugs.python.org (Laura Creighton)
Date: Thu, 03 Dec 2015 16:41:30 +0000
Subject: [New-bugs-announce] [issue25788] fileinput.hook_encoded has no way
 to pass arguments to codecs
Message-ID: <1449160890.79.0.711012524776.issue25788@psf.upfronthosting.co.za>


New submission from Laura Creighton:

Right now there is no way, aside from writing your own openhook, to
get around the limitation that openhook=fileinput.hook_encoded("utf")
will open things with the default option for codecs.open()
of errors=strict.  Adding a way to pass the errors argument seems
both easy to do and useful.

----------
components: IO
messages: 255818
nosy: lac, serhiy.storchaka
priority: normal
severity: normal
status: open
title: fileinput.hook_encoded has no way to pass arguments to codecs
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25788>
_______________________________________

From report at bugs.python.org  Thu Dec  3 12:25:52 2015
From: report at bugs.python.org (Wolfgang Maier)
Date: Thu, 03 Dec 2015 17:25:52 +0000
Subject: [New-bugs-announce] [issue25789] py launcher stderr is not piped to
 subprocess.Popen.stderr
Message-ID: <1449163552.68.0.156481310646.issue25789@psf.upfronthosting.co.za>


New submission from Wolfgang Maier:

from the console:

> py -3.7

or any other not installed Python version gives:
Requested Python version (3.7) not installed


However, when the launcher is executed from python via subprocess.Popen:

>>>import subprocess
>>>p=subprocess.Popen(['py', '-3.7'], stdout=subprocess.PIPE, stderr=subprocess.PIPE)
>>>p.communicate()
(b'', b'')

the error message is not accessible. (Error messages from any successfully launched Python interpreter are available through p.stderr though.)

----------
components: Windows
messages: 255822
nosy: paul.moore, steve.dower, tim.golden, wolma, zach.ware
priority: normal
severity: normal
status: open
title: py launcher stderr is not piped to subprocess.Popen.stderr
type: behavior
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25789>
_______________________________________

From report at bugs.python.org  Thu Dec  3 15:27:33 2015
From: report at bugs.python.org (YoSTEALTH)
Date: Thu, 03 Dec 2015 20:27:33 +0000
Subject: [New-bugs-announce] [issue25790] shutil.chown function enhancement
Message-ID: <1449174453.32.0.268528261377.issue25790@psf.upfronthosting.co.za>


New submission from YoSTEALTH:

A very simple but useful enhancement for shutil.chown function

Currently "shutil.chown" function effects only one directory or file user/group permission by adding "recursive" parameter it can easily effect all sub-directories/files

Source: https://hg.python.org/cpython/file/3.5/Lib/shutil.py#l1007


# Current:
def chown(path, user=None, group=None):

    """Change owner user and group of the given path.


    user and group can be the uid/gid or the user/group names, and in that case,

    they are converted to their respective uid/gid.

    """


    if user is None and group is None:

        raise ValueError("user and/or group must be set")


    _user = user

    _group = group


    # -1 means don't change it

    if user is None:

        _user = -1

    # user can either be an int (the uid) or a string (the system username)

    elif isinstance(user, str):

        _user = _get_uid(user)

        if _user is None:

            raise LookupError("no such user: {!r}".format(user))


    if group is None:

        _group = -1

    elif not isinstance(group, int):

        _group = _get_gid(group)

        if _group is None:

            raise LookupError("no such group: {!r}".format(group))


    os.chown(path, _user, _group)


# Enhanced:

import os.path


# Internal Function
def _dir_walk(path):
    ''' Get All Directories & Files'''

    for dir_path, dir_names, file_names in os.walk(path):

        # Directories
        for dir_name in dir_names:
            yield os.path.join(dir_path, dir_name)

        # Files
        for file_name in file_names:
            yield os.path.join(dir_path, file_name)

def chown(path, user=None, group=None, recursive=False):

    """Change owner user and group of the given path.


    user and group can be the uid/gid or the user/group names, and in that case,

    they are converted to their respective uid/gid.

    """


    if user is None and group is None:

        raise ValueError("user and/or group must be set")


    _user = user

    _group = group


    # -1 means don't change it

    if user is None:

        _user = -1

    # user can either be an int (the uid) or a string (the system username)

    elif isinstance(user, str):

        _user = _get_uid(user)

        if _user is None:

            raise LookupError("no such user: {!r}".format(user))


    if group is None:

        _group = -1

    elif not isinstance(group, int):

        _group = _get_gid(group)

        if _group is None:

            raise LookupError("no such group: {!r}".format(group))

    # Default Do First
    if not recursive:
        os.chown(path, _user, _group)
    else:
        for recursive_path in _dir_walk(path):
            os.chown(recursive_path, _user, _group)


hope this helps :)

----------
hgrepos: 324
messages: 255834
nosy: YoSTEALTH
priority: normal
severity: normal
status: open
title: shutil.chown function enhancement
type: enhancement
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25790>
_______________________________________

From report at bugs.python.org  Thu Dec  3 15:48:12 2015
From: report at bugs.python.org (Brett Cannon)
Date: Thu, 03 Dec 2015 20:48:12 +0000
Subject: [New-bugs-announce] [issue25791] Raise an ImportWarning when
 __spec__.parent/__package__ isn't defined for a relative import
Message-ID: <1449175692.43.0.67090220632.issue25791@psf.upfronthosting.co.za>


New submission from Brett Cannon:

When you do a relative import, __package__ is used to help resolve it, but if it isn't defined we fall back on using __name__ and __path__. We should probably consider raising an ImportWarning if __package__ isn't defined so that some day we can consider cleaning up __import__ and its call signature to be a bit more sane and drop the `globals` argument. It would also help people catch errors where they went overboard deleting attributes off a module.

We should probably even extend it to start using __spec__.parent and then falling back to __package__, and only after both are found missing do we raise the ImportWarning about needing to use __name__ and __path__. That way __import__ can simply start taking in the spec of the calling module to do all of its work instead of having to pass all of globals().

----------
components: Interpreter Core
messages: 255838
nosy: brett.cannon, eric.snow, ncoghlan
priority: low
severity: normal
stage: test needed
status: open
title: Raise an ImportWarning when __spec__.parent/__package__ isn't defined for a relative import
type: enhancement
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25791>
_______________________________________

From report at bugs.python.org  Thu Dec  3 15:58:16 2015
From: report at bugs.python.org (Sam Obstgarten)
Date: Thu, 03 Dec 2015 20:58:16 +0000
Subject: [New-bugs-announce] [issue25792] sorted() is not stable given
 key=len and large inputs
Message-ID: <1449176296.73.0.525670564276.issue25792@psf.upfronthosting.co.za>


New submission from Sam Obstgarten:

Tested under MacOS 10.11.1
Python 2.7.8

When using sorted() with key=len, sorted() is not stable (i.e. it does not return the same sorting depending on the input file). I expected, that sorted() sorts (i) first according the string length and then (ii) alphabetically.

I used as input Bitcoin addresses (Base58 encoding). First with 1 million Bitcoin addresses, and then with only 9. The results of the last addresses differ in their respective order.

1) Test with 1 million addresses, and these are the last ones:

[...]
1W7ezLRaahQTRfgxwZjkyFASPqMcskeMi
1Jf5QEDgpdPYmj8VwKWcTQonwZqSfMvhA
1MttkWDPEgGRPrEfYD3awWfijWcKw6QJL
1QrH9dJexkL78T12B6LVm4yctFhFJS4S3
1pdbjAiEKVxUc1fudq3HtPzkxQxPxYxuN
1NgahguJexVUmW3FFhS4vQbfRkGHfbSn2
1111111AgxDnb8UWCwZnJGUNrX6cAzaL
11111116Jvg5YivHHTcuapzk5CtSEBVA
1111111111111111111114oLvT2

2) Test with only these 9 addresses:

1W7ezLRaahQTRfgxwZjkyFASPqMcskeMi
1QrH9dJexkL78T12B6LVm4yctFhFJS4S3
1pdbjAiEKVxUc1fudq3HtPzkxQxPxYxuN
1Jf5QEDgpdPYmj8VwKWcTQonwZqSfMvhA
1MttkWDPEgGRPrEfYD3awWfijWcKw6QJL
1NgahguJexVUmW3FFhS4vQbfRkGHfbSn2
1111111AgxDnb8UWCwZnJGUNrX6cAzaL
11111116Jvg5YivHHTcuapzk5CtSEBVA
1111111111111111111114oLvT2

I can provide more details and the full set of Bitcoin addresses if required.

----------
components: Interpreter Core
messages: 255840
nosy: Sam Obstgarten
priority: normal
severity: normal
status: open
title: sorted() is not stable given key=len and large inputs
type: behavior
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25792>
_______________________________________

From report at bugs.python.org  Thu Dec  3 16:40:30 2015
From: report at bugs.python.org (sami drif)
Date: Thu, 03 Dec 2015 21:40:30 +0000
Subject: [New-bugs-announce] [issue25793] "><svg/onload=prompt(2)>""<input
 onfocus=alert(1337)"autofocus
Message-ID: <1449178830.46.0.54260776795.issue25793@psf.upfronthosting.co.za>


New submission from sami drif:

"><svg/onload=prompt(2)>""<input onfocus=alert(1337)"autofocus
"><script>alert(1)</script>"><marquee><h1>alert("Xss By \Sami")</h1></marquee>

----------
components: Build
files: s.php
messages: 255843
nosy: sami drif
priority: normal
severity: normal
status: open
title: "><svg/onload=prompt(2)>""<input onfocus=alert(1337)"autofocus
type: resource usage
versions: Python 3.4
Added file: http://bugs.python.org/file41229/s.php

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25793>
_______________________________________

From report at bugs.python.org  Fri Dec  4 03:52:37 2015
From: report at bugs.python.org (Dominik Schmid)
Date: Fri, 04 Dec 2015 08:52:37 +0000
Subject: [New-bugs-announce] [issue25794] __setattr__ does not always
 overload operators
Message-ID: <1449219157.0.0.30103039285.issue25794@psf.upfronthosting.co.za>


New submission from Dominik Schmid:

While implementing my own Integer class that keeps track of when operations are applied I noticed that setattr had a strange behaviour when I tried to wrap operator functions.

When the attribute string had a different id to its literal it failed to overload the operator.
Are we doing a 'is' rather than a '==' somewhere in setattr?


expected result: 
139723705431168    a.__add__(b)= (5)    a+b= (5)
139723705431168    a.__add__(b)= (5)    a+b= (5)
139723704361584    a.__add__(b)= (5)    a+b= (5)


actual result:
139723705431168    a.__add__(b)= (5)    a+b= (5)
139723705431168    a.__add__(b)= (5)    a+b= (5)
139723704361584    a.__add__(b)= (5)    a+b=
Traceback (most recent call last):
  File "/home/dom/Documents/leastOps/bug.py", line 41, in <module>
    testSetattr(funcName3)
  File "/home/dom/Documents/leastOps/bug.py", line 28, in testSetattr
    print '   a+b=', a+b
TypeError: unsupported operand type(s) for +: 'Integer' and 'Integer'



version:
2.7.10 (default, Oct 14 2015, 16:09:02) 
[GCC 5.2.1 20151010]
ubuntu 14.10

----------
components: Interpreter Core
files: bug.py
messages: 255853
nosy: Dominik Schmid
priority: normal
severity: normal
status: open
title: __setattr__ does not always overload operators
type: behavior
versions: Python 2.7
Added file: http://bugs.python.org/file41234/bug.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25794>
_______________________________________

From report at bugs.python.org  Fri Dec  4 05:54:55 2015
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Dec 2015 10:54:55 +0000
Subject: [New-bugs-announce] [issue25795] test_fork1 cannot be run directly:
 ./pyhon Lib/test/test_fork1.py
Message-ID: <1449226495.18.0.11148597245.issue25795@psf.upfronthosting.co.za>


New submission from STINNER Victor:

haypo at smithers$ ./python Lib/test/test_fork1.py 
Traceback (most recent call last):
  File "Lib/test/test_fork1.py", line 111, in <module>
    unittest.main()
NameError: name 'unittest' is not defined

According to pyflakes, the error "undefined name 'unittest'" is found in:

- test_fork1
- test_list
- test_pyclbr
- test_telnetlib
- test_tuple
- test_userdict
- test_userlist
- test_wait4

I put the "easy" flag to give a simple issue to newcomers in Python ;-)

Please check other Python version: 2.7 and 3.5. I'm too lazy to check myself :-D

See issue the issue #25783 which is similar.

----------
components: Tests
keywords: easy
messages: 255856
nosy: haypo
priority: normal
severity: normal
status: open
title: test_fork1 cannot be run directly: ./pyhon Lib/test/test_fork1.py
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25795>
_______________________________________

From report at bugs.python.org  Fri Dec  4 06:51:57 2015
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Dec 2015 11:51:57 +0000
Subject: [New-bugs-announce] [issue25796] Running test_multiprocessing_spawn
 is slow (more than 8 minutes)
Message-ID: <1449229917.91.0.185617519884.issue25796@psf.upfronthosting.co.za>


New submission from STINNER Victor:

Hi,

When I run the Python test suite with "./python -m test -j0 -rW",  test_multiprocessing_spawn is almost the latest one to run. Example:
---
(...)
[399/401/1] test_lib2to3 (68 sec) -- running: test_zipfile (43 sec), test_multiprocessing_spawn (484 sec)
[400/401/1] test_zipfile (45 sec) -- running: test_multiprocessing_spawn (488 sec)
^C
Waiting for test_multiprocessing_spawn

Test suite interrupted by signal SIGINT.
1 test omitted:
    test_multiprocessing_spawn
(...)
---

Would it be possible to make it faster? Skip some tests? I don't know.

----------
messages: 255860
nosy: haypo
priority: normal
severity: normal
status: open
title: Running test_multiprocessing_spawn is slow (more than 8 minutes)
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25796>
_______________________________________

From report at bugs.python.org  Fri Dec  4 09:03:38 2015
From: report at bugs.python.org (Dhruv Rajvanshi)
Date: Fri, 04 Dec 2015 14:03:38 +0000
Subject: [New-bugs-announce] [issue25797] Default argument values with type
 hints break type correctness
Message-ID: <1449237818.22.0.235268413018.issue25797@psf.upfronthosting.co.za>


New submission from Dhruv Rajvanshi:

Specifying default arguments break the type system. The types of default values aren't matched with the type of the argument.
Moreover, having None as a default value changes the type declaration to Optional[T]. So, the declaration may be 
    f(a : int = None)
but this would be treated as
   f(a : Optional[int] = None)

----------
components: Library (Lib)
files: test.py
messages: 255864
nosy: Dhruv Rajvanshi
priority: normal
severity: normal
status: open
title: Default argument values with type hints break type correctness
type: behavior
versions: Python 3.5
Added file: http://bugs.python.org/file41238/test.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25797>
_______________________________________

From report at bugs.python.org  Fri Dec  4 15:34:31 2015
From: report at bugs.python.org (Ned Deily)
Date: Fri, 04 Dec 2015 20:34:31 +0000
Subject: [New-bugs-announce] [issue25798] Update python.org installers to
 use OpenSSL 1.0.2e
Message-ID: <1449261271.59.0.313913873542.issue25798@psf.upfronthosting.co.za>


New submission from Ned Deily:

https://www.openssl.org/news/secadv/20151203.txt

----------
components: Build
messages: 255880
nosy: benjamin.peterson, larry, ned.deily, steve.dower
priority: normal
severity: normal
stage: needs patch
status: open
title: Update python.org installers to use OpenSSL 1.0.2e
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25798>
_______________________________________

From report at bugs.python.org  Fri Dec  4 15:46:46 2015
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 04 Dec 2015 20:46:46 +0000
Subject: [New-bugs-announce] [issue25799] 2.7.11rc1 not added to Win10 app
 list (start menu)
Message-ID: <1449262006.23.0.517910182008.issue25799@psf.upfronthosting.co.za>


New submission from Terry J. Reedy:

I just installed 2.7.11rc1 on Win 10 and noticed that 'Python 2.7' is missing both from Start - All apps and from search bar results for 'python' (only 3.4 and 3.5 appear in local search results).  To be sure, I uninstalled, installed fresh, and even restarted. Same result.  2.7.11 is present on disk and py.exe finds and starts it, but it is not fully installed as an app, and the associated icons are not available.

I was able to work around this and make an 'IDLE icon' from a pythonw.exe shortcut, but if this problem is general to at least Win 10, there will be a lot of confused users.

----------
components: Installation, Windows
messages: 255881
nosy: benjamin.peterson, paul.moore, steve.dower, terry.reedy, tim.golden, zach.ware
priority: release blocker
severity: normal
stage: needs patch
status: open
title: 2.7.11rc1 not added to Win10 app list (start menu)
type: behavior
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25799>
_______________________________________

From report at bugs.python.org  Fri Dec  4 17:16:46 2015
From: report at bugs.python.org (SilentGhost)
Date: Fri, 04 Dec 2015 22:16:46 +0000
Subject: [New-bugs-announce] [issue25800] errors running test_capi from
 command line
Message-ID: <1449267406.87.0.412961046196.issue25800@psf.upfronthosting.co.za>


New submission from SilentGhost:

Running:

./python Lib/test/test_capi.py

I got EmbeddingTests erroring out in setUp: first line of which (a triple application of os.path.dirname) creates an empty string which cannot be used as an argument to os.chdir afterwards. I'm to be honest not at all sure how this should be properly solved.

Just for the record: running ./python -m test test_capi works fine.

----------
components: Tests
messages: 255888
nosy: SilentGhost, zach.ware
priority: normal
severity: normal
status: open
title: errors running test_capi from command line
versions: Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25800>
_______________________________________

From report at bugs.python.org  Fri Dec  4 17:36:35 2015
From: report at bugs.python.org (SilentGhost)
Date: Fri, 04 Dec 2015 22:36:35 +0000
Subject: [New-bugs-announce] [issue25801] ResourceWarning in test_zipfile64
Message-ID: <1449268595.5.0.95531754857.issue25801@psf.upfronthosting.co.za>


New submission from SilentGhost:

Running test_zipfile64 from command line (i.e., ./python Lib/test/test_zipfile64.py) I get two ResourceWarnings:

? ./python Lib/test/test_zipfile64.py                                                     
..Lib/test/test_zipfile64.py:82: ResourceWarning: unclosed file <_io.BufferedRandom name=4>
  for f in TemporaryFile(), TESTFN2:
.Lib/test/test_zipfile64.py:75: ResourceWarning: unclosed file <_io.BufferedRandom name=4>
  for f in TemporaryFile(), TESTFN2:
.
----------------------------------------------------------------------
Ran 4 tests in 356.228s

OK

Wasn't able to test with "-m test" even with -uall. Will try again tomorrow.

----------
components: Tests
messages: 255890
nosy: SilentGhost, alanmcintyre, serhiy.storchaka, twouters
priority: normal
severity: normal
status: open
title: ResourceWarning in test_zipfile64
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25801>
_______________________________________

From report at bugs.python.org  Fri Dec  4 19:07:43 2015
From: report at bugs.python.org (Brett Cannon)
Date: Sat, 05 Dec 2015 00:07:43 +0000
Subject: [New-bugs-announce] [issue25802] Finish deprecating load_module()
Message-ID: <1449274063.93.0.451300544059.issue25802@psf.upfronthosting.co.za>


New submission from Brett Cannon:

There are a couple concrete implementations of load_module() in importlib that have not been explicitly deprecated that probably should be. As part of this I will finally add an Examples section to the importlib docs to show how to do common tasks such as load a source file.

----------
assignee: brett.cannon
components: Library (Lib)
messages: 255905
nosy: brett.cannon, eric.snow, ncoghlan
priority: normal
severity: normal
stage: test needed
status: open
title: Finish deprecating load_module()
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25802>
_______________________________________

From report at bugs.python.org  Fri Dec  4 22:48:12 2015
From: report at bugs.python.org (Daniel Lepage)
Date: Sat, 05 Dec 2015 03:48:12 +0000
Subject: [New-bugs-announce] [issue25803] pathlib.Path('/').mkdir() raises
 wrong error type
Message-ID: <1449287292.61.0.915471984931.issue25803@psf.upfronthosting.co.za>


New submission from Daniel Lepage:

pathlib.Path('/').mkdir() raises an IsADirectoryError instead of a FileExistsError.

----------
components: Library (Lib)
messages: 255916
nosy: Daniel Lepage
priority: normal
severity: normal
status: open
title: pathlib.Path('/').mkdir() raises wrong error type
type: behavior
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25803>
_______________________________________

From report at bugs.python.org  Sat Dec  5 03:25:52 2015
From: report at bugs.python.org (Chiu-Hsiang Hsu)
Date: Sat, 05 Dec 2015 08:25:52 +0000
Subject: [New-bugs-announce] [issue25804] Make Profile.print_stats support
 sorting by mutiple values
Message-ID: <1449303952.27.0.310214243782.issue25804@psf.upfronthosting.co.za>


New submission from Chiu-Hsiang Hsu:

Currently, the result of profile.run can not easily sort by mutiple values with "sort" keyword argument. Following code will work with this patch.

>>> import cProfile
>>> cProfile.run('42**42', sort=('tottime', 'stdname'))
         3 function calls in 0.000 seconds

   Ordered by: internal time, standard name

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
        1    0.000    0.000    0.000    0.000 {built-in method builtins.exec}
        1    0.000    0.000    0.000    0.000 <string>:1(<module>)
        1    0.000    0.000    0.000    0.000 {method 'disable' of '_lsprof.Profiler' objects}

>>> import cProfile
>>> cProfile.run('42**42', sort=('tottime', 'stdname'))
         3 function calls in 0.000 seconds

   Ordered by: internal time, standard name

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
        1    0.000    0.000    0.000    0.000 {built-in method builtins.exec}
        1    0.000    0.000    0.000    0.000 <string>:1(<module>)
        1    0.000    0.000    0.000    0.000 {method 'disable' of '_lsprof.Profiler' objects}


>>> import profile
>>> profile.run('42**42', sort=('tottime', 'stdname'))
         4 function calls in 0.000 seconds

   Ordered by: internal time, standard name

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
        1    0.000    0.000    0.000    0.000 profile:0(42**42)
        1    0.000    0.000    0.000    0.000 :0(exec)
        1    0.000    0.000    0.000    0.000 :0(setprofile)
        1    0.000    0.000    0.000    0.000 <string>:1(<module>)
        0    0.000             0.000          profile:0(profiler)

----------
components: Library (Lib)
files: print_stats.patch
keywords: patch
messages: 255935
nosy: wdv4758h
priority: normal
severity: normal
status: open
title: Make Profile.print_stats support sorting by mutiple values
type: enhancement
versions: Python 3.6
Added file: http://bugs.python.org/file41247/print_stats.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25804>
_______________________________________

From report at bugs.python.org  Sat Dec  5 04:08:04 2015
From: report at bugs.python.org (SilentGhost)
Date: Sat, 05 Dec 2015 09:08:04 +0000
Subject: [New-bugs-announce] [issue25805] Failure in test_pkgutil run from
 command-line
Message-ID: <1449306484.59.0.680027150317.issue25805@psf.upfronthosting.co.za>


New submission from SilentGhost:

Running ./python Lib/test/test_pkgutil.py I got one test failing:

test.support.TestFailed: Traceback (most recent call last):
  File "Lib/test/test_pkgutil.py", line 346, in test_get_loader_handles_missing_loader_attribute
    self.assertIsNotNone(pkgutil.get_loader(__name__))
AssertionError: unexpectedly None

When run as `./python -m test test_pkgutil` everything is fine.

----------
components: Tests
messages: 255939
nosy: SilentGhost, alexis, dstufft, eric.araujo, lemburg, paul.moore, tarek
priority: normal
severity: normal
status: open
title: Failure in test_pkgutil run from command-line
type: behavior
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25805>
_______________________________________

From report at bugs.python.org  Sat Dec  5 06:36:02 2015
From: report at bugs.python.org (SilentGhost)
Date: Sat, 05 Dec 2015 11:36:02 +0000
Subject: [New-bugs-announce] [issue25806] ResourceWarning in test_tasks
Message-ID: <1449315362.86.0.102548647326.issue25806@psf.upfronthosting.co.za>


New submission from SilentGhost:

When running ./python Lib/test/test_asyncio/test_tasks.py I get a ResourceWarning:

Lib/asyncio/base_events.py:379: ResourceWarning: unclosed event loop <_UnixSelectorEventLoop running=False closed=False debug=False>

When running using test machinery: ./python -m test test_asyncio (I didn't figure out how to run that individual test) everything is fine.

----------
components: Tests, asyncio
messages: 255944
nosy: SilentGhost, gvanrossum, haypo, yselivanov
priority: normal
severity: normal
status: open
title: ResourceWarning in test_tasks
type: behavior
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25806>
_______________________________________

From report at bugs.python.org  Sat Dec  5 09:02:33 2015
From: report at bugs.python.org (SilentGhost)
Date: Sat, 05 Dec 2015 14:02:33 +0000
Subject: [New-bugs-announce] [issue25807]
 test_multiprocessing_fork.test_mymanager fails and hangs
Message-ID: <1449324153.86.0.866087116422.issue25807@psf.upfronthosting.co.za>


New submission from SilentGhost:

When running either of the test_multiprocessing_fork, test_multiprocessing_spawn or test_multiprocessing_forkserver I get error in test_mymanager that leads to hanging. Here is the fragment:

test_mymanager (test.test_multiprocessing_fork.WithManagerTestMyManager) ... Unhandled exception in thread started by <bound method Thread._bootstrap of <Thread(MainProcess, started daemon 140251183703808)>>
Traceback (most recent call last):
  File "cpython/Lib/multiprocessing/managers.py", line 235, in serve_client
    (methodname, type(obj), exposed)
AttributeError: method '_h' of <class 'test._test_multiprocessing.FooBar'> object is not in exposed={'g', 'f'}

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "cpython/Lib/multiprocessing/managers.py", line 258, in serve_client
    fallback_func = self.fallback_mapping[methodname]
KeyError: '_h'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "cpython/Lib/multiprocessing/managers.py", line 195, in handle_request
    result = func(c, *args, **kwds)
  File "cpython/Lib/multiprocessing/managers.py", line 386, in accept_connection
  File "cpython/Lib/multiprocessing/managers.py", line 264, in serve_client
    msg = ('#TRACEBACK', format_exc())
  File "cpython/Lib/traceback.py", line 163, in format_exc
    return "".join(format_exception(*sys.exc_info(), limit=limit, chain=chain))
  File "cpython/Lib/traceback.py", line 117, in format_exception
    type(value), value, tb, limit=limit).format(chain=chain))
  File "cpython/Lib/traceback.py", line 474, in __init__
    capture_locals=capture_locals)
  File "cpython/Lib/traceback.py", line 358, in extract
    f.line
  File "cpython/Lib/traceback.py", line 282, in line
    self._line = linecache.getline(self.filename, self.lineno).strip()
  File "cpython/Lib/linecache.py", line 16, in getline
    lines = getlines(filename, module_globals)
  File "cpython/Lib/linecache.py", line 47, in getlines
    return updatecache(filename, module_globals)
  File "cpython/Lib/linecache.py", line 137, in updatecache
    lines = fp.readlines()
  File "cpython/Lib/codecs.py", line 321, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xaa in position 4096: invalid start byte

This UnicodeDecodeError repeats couple more times and then everything stops. It doesn't seem to matter how the tests run, either directly or as part of a test suite.

----------
components: Library (Lib), Tests
messages: 255953
nosy: SilentGhost, jnoller, sbt
priority: normal
severity: normal
status: open
title: test_multiprocessing_fork.test_mymanager fails and hangs
type: behavior
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25807>
_______________________________________

From report at bugs.python.org  Sat Dec  5 12:25:57 2015
From: report at bugs.python.org (Ben Schreib)
Date: Sat, 05 Dec 2015 17:25:57 +0000
Subject: [New-bugs-announce] [issue25808] The Python Tutorial 5.3. Tuples
 and Sequences
Message-ID: <1449336357.7.0.799444279603.issue25808@psf.upfronthosting.co.za>


New submission from Ben Schreib:

The example given in section 5.3 shows an output of "t[0] = 88888" but I believe it should be "t[0] = 12345"

>>> t
(12345, 54321, 'hello!')
>>> # Tuples may be nested:
... u = t, (1, 2, 3, 4, 5)
>>> u
((12345, 54321, 'hello!'), (1, 2, 3, 4, 5))
>>> # Tuples are immutable:
... t[0] = 88888

----------
assignee: docs at python
components: Documentation
messages: 255962
nosy: Ben Schreib, docs at python
priority: normal
severity: normal
status: open
title: The Python Tutorial 5.3. Tuples and Sequences
type: enhancement
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25808>
_______________________________________

From report at bugs.python.org  Sat Dec  5 12:59:21 2015
From: report at bugs.python.org (bapt)
Date: Sat, 05 Dec 2015 17:59:21 +0000
Subject: [New-bugs-announce] [issue25809] "Invalid" tests on locales
Message-ID: <1449338361.54.0.813249849015.issue25809@psf.upfronthosting.co.za>


New submission from bapt:

the locale tests the return value of locale functions against known good values.

The problem is when those known good values becomes wrong because of an update of the locales.

For example in recent CLDR definition the french separator for thousands in a "non breaking space" and not a space, while it used to be a space.
On released FreeBSD (very old db) it was a space. On GNU libc (a more recent db but still old :)) it is a space.On FreeBSD 11 and Dragonfly 4.4 it is a fairly new db (v27.0.1) with the fixed separator: 0xa0!

Thant makes this test fail.

I have no idea on the way you would prefer to fix that, either remove the test (not sure it is really relevant in the python testsuite) or patch it.

https://hg.python.org/cpython/file/tip/Lib/test/test__locale.py#l70
the failures can be seen here:
http://buildbot.python.org/all/buildslaves/koobs-freebsd11

----------
components: Tests
messages: 255964
nosy: bapt, haypo
priority: normal
severity: normal
status: open
title: "Invalid" tests on locales
type: behavior
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25809>
_______________________________________

From report at bugs.python.org  Sat Dec  5 15:13:23 2015
From: report at bugs.python.org (Andre Roberge)
Date: Sat, 05 Dec 2015 20:13:23 +0000
Subject: [New-bugs-announce] [issue25810] Python 3 documentation for eval is
 incorrect
Message-ID: <1449346403.16.0.483198527619.issue25810@psf.upfronthosting.co.za>


New submission from Andre Roberge:

The documentation for eval() indicates that it takes keyword arguments:

eval(expression, globals=None, locals=None)

However, that is incorrect, as indicated by the builtin help:

>>> help(eval)
Help on built-in function eval in module builtins:

eval(...)
    eval(source[, globals[, locals]]) -> value

----------
assignee: docs at python
components: Documentation
messages: 255969
nosy: aroberge, docs at python
priority: normal
severity: normal
status: open
title: Python 3 documentation for eval is incorrect
versions: Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25810>
_______________________________________

From report at bugs.python.org  Sat Dec  5 15:34:19 2015
From: report at bugs.python.org (Eugene Yunak)
Date: Sat, 05 Dec 2015 20:34:19 +0000
Subject: [New-bugs-announce] [issue25811] return from random.shuffle
Message-ID: <1449347659.07.0.0890236268901.issue25811@psf.upfronthosting.co.za>


New submission from Eugene Yunak:

random.shuffle operates on a list, and changes it in place. I think returning a reference to this list, the same one we got in as the argument, is quite useful and makes it possible to use random.shuffle in chained function calls, e.g.:

somelist.append(''.join(shuffle(list('hello'))))
[i for i in shuffle(list(range(10))) if i%2]

I don't see any good arguments against this, and I couldn't think of a reasonable test for this ? is it necessary to test whether the returned reference is the same as the one passed in?

I'm open to any discussion or suggestions you might have.

----------
components: Library (Lib)
files: shuffle_return.patch
keywords: patch
messages: 255971
nosy: Eugene Yunak
priority: normal
severity: normal
status: open
title: return from random.shuffle
type: enhancement
Added file: http://bugs.python.org/file41251/shuffle_return.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25811>
_______________________________________

From report at bugs.python.org  Sat Dec  5 16:19:05 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 05 Dec 2015 21:19:05 +0000
Subject: [New-bugs-announce] [issue25812] locale.nl_langinfo() can't decode
 value
Message-ID: <1449350345.3.0.205814810685.issue25812@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

>>> import locale
>>> locale.setlocale(locale.LC_NUMERIC, 'uk_UA')
'uk_UA'
>>> locale.getlocale(locale.LC_NUMERIC)
('uk_UA', 'KOI8-U')
>>> locale.nl_langinfo(locale.THOUSEP)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
UnicodeDecodeError: 'locale' codec can't decode byte 0x9a in position 0: Invalid or incomplete multibyte or wide character

Looks as locale.nl_langinfo() always uses the UTF-8 encoding (or may be locale.getpreferredencoding()).

----------
components: Library (Lib)
messages: 255979
nosy: lemburg, loewis, serhiy.storchaka
priority: normal
severity: normal
status: open
title: locale.nl_langinfo() can't decode value
type: behavior
versions: Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25812>
_______________________________________

From report at bugs.python.org  Sat Dec  5 17:11:14 2015
From: report at bugs.python.org (Mark Lawrence)
Date: Sat, 05 Dec 2015 22:11:14 +0000
Subject: [New-bugs-announce] [issue25813] co_flags section of inspect module
 docs out of date
Message-ID: <1449353474.35.0.531055283092.issue25813@psf.upfronthosting.co.za>


New submission from Mark Lawrence:

It states "bitmap: 1=optimized | 2=newlocals | 4=*arg | 8=**arg" which is identical to the 2.7 docs.  Hence it bears no resemblance to the latest code.h, which for example has #define CO_ITERABLE_COROUTINE   0x0100.

----------
assignee: docs at python
components: Documentation
messages: 255985
nosy: BreamoreBoy, docs at python
priority: normal
severity: normal
status: open
title: co_flags section of inspect module docs out of date
versions: Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25813>
_______________________________________

From report at bugs.python.org  Sun Dec  6 10:00:03 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 06 Dec 2015 15:00:03 +0000
Subject: [New-bugs-announce] [issue25814] Propagate all errors from
 ElementTree.iterparse
Message-ID: <1449414003.26.0.361289515634.issue25814@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Some memory errors raised in handlers during XML parsing are explicitly or implicitly propagated to the caller of XMLParser methods feed(), close(), and _parse_whole(). But others are silenced with PyErr_Clear() with added comments "FIXME: propagate error". There are no reasons why one errors are propagated and others are not. For example memory error during creating tuple is not propagated, but memory error during resizing a list to which this tuple is appended is propagated. Looks as this is not intentional.

Not propagated errors can cause the lost of events. Proposed patch makes the parser to propagate all errors. Since it extracts common code into the treebuilder_append_event() function and inlines the treebuilder_handle_namespace() function, the resulting code becomes even simpler, its size is decreased by 49 lines.

----------
components: Extension Modules, XML
files: etree_propagate_errors.patch
keywords: patch
messages: 256012
nosy: brett.cannon, scoder, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Propagate all errors from ElementTree.iterparse
type: behavior
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41256/etree_propagate_errors.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25814>
_______________________________________

From report at bugs.python.org  Sun Dec  6 21:50:00 2015
From: report at bugs.python.org (Anthony Sottile)
Date: Mon, 07 Dec 2015 02:50:00 +0000
Subject: [New-bugs-announce] [issue25815] Improper subprocess output of
 arguments with braces in them on windows
Message-ID: <1449456600.09.0.498208325206.issue25815@psf.upfronthosting.co.za>


New submission from Anthony Sottile:

First some expected output:

```
# from cmd.exe
C:\Users\Anthony>echo hi{1}
hi{1}
# from MINGW
$ echo hi{1}
hi{1}
```

```
# On ubuntu
$ echo 'hi{1}'
hi{1}
$ python3.5 -c "import subprocess; print(subprocess.check_output(('echo', 'hi{1}')))"
b'hi{1}\n'
```

Now for the unexpected output (produced only by python on windows) (notice the missing braces)

```
C:\Python27\python.exe -c "import subprocess; print(subprocess.check_output(('echo', 'hi{1}')))"
hi1
C:\Python34\python.exe -c "import subprocess; print(subprocess.check_output(('echo', 'hi{1}')))"
b'hi1\n'
C:\Python35\python.exe -c "import subprocess; print(subprocess.check_output(('echo', 'hi{1}')))"
b'hi1\n'
```

Peculiarly, these all produce the output I expect:

```
C:\Python35\python.exe -c "import subprocess; print(subprocess.check_output(('echo', 'hi {1}')))"
b'hi {1}\n'
C:\Python35\python.exe -c "import subprocess; print(subprocess.check_output(('echo', 'hi{1}'), shell=True))"
b'hi{1}\r\n'
```

I don't have access to 3.6, but I imagine the issue exists there too.

----------
components: Windows
messages: 256043
nosy: Anthony Sottile, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Improper subprocess output of arguments with braces in them on windows
versions: Python 2.7, Python 3.4, Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25815>
_______________________________________

From report at bugs.python.org  Mon Dec  7 13:01:38 2015
From: report at bugs.python.org (Laura Creighton)
Date: Mon, 07 Dec 2015 18:01:38 +0000
Subject: [New-bugs-announce] [issue25816] https://www.python.org/downloads/
 not working for 3.5.1 for windows 10 users
Message-ID: <1449511298.85.0.748253125909.issue25816@psf.upfronthosting.co.za>


New submission from Laura Creighton:

webmaster has heard from 2 windows 10 users who say that when 
they click on 'download windows 3.5.1' they are sent to
this  page https://www.python.org/downloads/windows/

instead of actually getting a download.

----------
messages: 256063
nosy: lac
priority: normal
severity: normal
status: open
title: https://www.python.org/downloads/ not working for 3.5.1 for windows 10 users

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25816>
_______________________________________

From report at bugs.python.org  Mon Dec  7 16:55:15 2015
From: report at bugs.python.org (Myron Walker)
Date: Mon, 07 Dec 2015 21:55:15 +0000
Subject: [New-bugs-announce] [issue25817] modsupport: 'countformat' does not
 handle strings without bracket levels correctly
Message-ID: <1449525315.43.0.771475082927.issue25817@psf.upfronthosting.co.za>


New submission from Myron Walker:

'countformat' does not appear to be handling the case where a format string is passed with no parenthesis or brackets correctly. Here is an
example of a usage that might cause issues from typedobject.c:

static PyObject*
slot_sq_slice(PyObject *self, Py_ssize_t i, Py_ssize_t j)
{
	static PyObject *getslice_str;

	if (PyErr_WarnPy3k("in 3.x, __getslice__ has been removed; "
			    "use __getitem__", 1) < 0)
		return NULL;
	return call_method(self, "__getslice__", &getslice_str,
		"nn", i, j);      <<<<<<< Maybe Bad Format Str <<<<<<<
}

The format string "nn" does not have any level markers so when it gets
processed by 'countformat' the count will be incremented 2 times by the
'default' case but when the end of the string is reached and the NULL character is processed bay "case '\0':".  The function will ignore the count variable and just return -1 anyway.  The error created is unmatched paren in format but 'level' is never checked to see if a paren
was even hit to begin with.

It might be that the case should be changed to look at level before assuming a error condition if strings are supposed to be processed as the one in the example above.  case '\0' should probably be doing something like:

         case '\0':
            if (level > 0) {   // Check If Level Was Incremented
                /* Premature end */
                PyErr_SetString(PyExc_SystemError,
                                "unmatched paren in format");
                return -1;
            }
            break;

----------
components: Interpreter Core
messages: 256075
nosy: Myron Walker
priority: normal
severity: normal
status: open
title: modsupport: 'countformat' does not handle strings without bracket levels correctly
type: behavior
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25817>
_______________________________________

From report at bugs.python.org  Mon Dec  7 17:33:02 2015
From: report at bugs.python.org (Isaac Dickinson)
Date: Mon, 07 Dec 2015 22:33:02 +0000
Subject: [New-bugs-announce] [issue25818] If protocol_factory raises an
 error, the connection closes but no stacktrace is printed on the server.
Message-ID: <1449527582.65.0.816850557982.issue25818@psf.upfronthosting.co.za>


New submission from Isaac Dickinson:

This makes it a nightmare to figure out why your connections are abruptly closing.  It should print an error at least.

----------
components: asyncio
files: broken.py
messages: 256081
nosy: SunDwarf, gvanrossum, haypo, yselivanov
priority: normal
severity: normal
status: open
title: If protocol_factory raises an error, the connection closes but no stacktrace is printed on the server.
versions: Python 3.4, Python 3.5
Added file: http://bugs.python.org/file41265/broken.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25818>
_______________________________________

From report at bugs.python.org  Mon Dec  7 17:44:49 2015
From: report at bugs.python.org (Calvin Simpkinson)
Date: Mon, 07 Dec 2015 22:44:49 +0000
Subject: [New-bugs-announce] [issue25819] print "Hi" in python 3 exception
 handling doesn't work
Message-ID: <1449528289.55.0.0778388229784.issue25819@psf.upfronthosting.co.za>


New submission from Calvin Simpkinson:

When you execute the code:
try:
    print "Hi"
except:
    print("Hello")

in python 3.5, it creates a syntax error in Terminal on Mac and a pop-up error in IDLE, while it should just print Hello in the console.

----------
messages: 256083
nosy: Calvin Simpkinson
priority: normal
severity: normal
status: open
title: print "Hi" in python 3 exception handling doesn't work
type: behavior
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25819>
_______________________________________

From report at bugs.python.org  Mon Dec  7 18:57:25 2015
From: report at bugs.python.org (Martin Panter)
Date: Mon, 07 Dec 2015 23:57:25 +0000
Subject: [New-bugs-announce] [issue25820] Clean up run_gdb() calls
Message-ID: <1449532645.93.0.282939842221.issue25820@psf.upfronthosting.co.za>


New submission from Martin Panter:

This small patch cleans up two oddities calling run_gdb() in /Lib/test/test_gdb.py that I noticed. They were both added in revision b71cda2f48c6. The first one is a whole GDB command being passed to GDB as extra arguments. Notice ?gdb --batch -nx? is in the argument tuple twice:

test_NULL_ob_type (test.test_gdb.PrettyPrintTests)
Ensure that a PyObject* with NULL ob_type is handled gracefully ... ('gdb', '--batch', '-nx', '-iex', 'add-auto-load-safe-path /media/disk/home/proj/python/cpython/python-gdb.py', 'gdb', '--batch', '-nx', '--eval-command=set breakpoint pending yes', '--eval-command=break builtin_id', '--eval-command=set print address off', '--eval-command=run', '--eval-command=set print entry-values no', '--eval-command=set v->ob_type=0', '--eval-command=backtrace', '--args', '/media/disk/home/proj/python/cpython/python', '-S', '-c', 'id(42)')
ok

The other is just an assignment that was never used.

----------
components: Tests
files: gdb-cleanup.patch
keywords: patch
messages: 256092
nosy: martin.panter, r.david.murray
priority: normal
severity: normal
stage: patch review
status: open
title: Clean up run_gdb() calls
type: enhancement
versions: Python 2.7, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41266/gdb-cleanup.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25820>
_______________________________________

From report at bugs.python.org  Mon Dec  7 18:58:32 2015
From: report at bugs.python.org (Anthony Green)
Date: Mon, 07 Dec 2015 23:58:32 +0000
Subject: [New-bugs-announce] [issue25821] Documentation for
 threading.enumerate / threading.Thread.is_alive is contradictory.
Message-ID: <1449532712.62.0.975258260554.issue25821@psf.upfronthosting.co.za>


Changes by Anthony Green <phoniel at gmail.com>:


----------
assignee: docs at python
components: Documentation
nosy: anthonygreen, docs at python, pitrou
priority: normal
severity: normal
status: open
title: Documentation for threading.enumerate / threading.Thread.is_alive is contradictory.
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25821>
_______________________________________

From report at bugs.python.org  Tue Dec  8 04:15:40 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Dec 2015 09:15:40 +0000
Subject: [New-bugs-announce] [issue25822] Add docstrings to fields of
 urllib.parse results
Message-ID: <1449566140.42.0.349073725206.issue25822@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Results of urlsplit() and urlparse() functions in the urllib.parse module are named tuple with a number of fields. Since property docstrings are writable now (issue24064), we can provide docstrings for all these fields. See also issue24878.

----------
components: Library (Lib)
messages: 256105
nosy: rhettinger, serhiy.storchaka
priority: normal
severity: normal
stage: needs patch
status: open
title: Add docstrings to fields of urllib.parse results
type: enhancement
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25822>
_______________________________________

From report at bugs.python.org  Tue Dec  8 04:34:11 2015
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 08 Dec 2015 09:34:11 +0000
Subject: [New-bugs-announce] [issue25823] Speed-up oparg decoding on
 little-endian machines
Message-ID: <1449567251.61.0.853791637694.issue25823@psf.upfronthosting.co.za>


New submission from Raymond Hettinger:

On little-endian machines, the decoding of an oparg can be sped-up by using a single 16-bit pointer deference.

Current decoding:
    leaq    2(%rcx), %rbp
    movzbl  -1(%rbp), %eax
    movzbl  -2(%rbp), %r14d
    sall    $8, %eax
    addl    %eax, %r14d

New decoding:
    leaq    2(%rdx), %r12
    movzwl  -2(%r12), %r8d

The patch uses (unsigned short *) like the struct module does, but it could use uint16_t if necessary.

If next_instr can be advanced after the lookup rather than before, the generated code would be tighter still (removing the data dependency and shortening the movzwl instruction to drop the offset byte):

    movzwl  (%rdx), %r8d
    leaq    2(%rdx), %rbp

----------
assignee: serhiy.storchaka
components: Interpreter Core
messages: 256106
nosy: rhettinger, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Speed-up oparg decoding on little-endian machines
type: performance
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25823>
_______________________________________

From report at bugs.python.org  Tue Dec  8 09:16:40 2015
From: report at bugs.python.org (Arnaud Diederen)
Date: Tue, 08 Dec 2015 14:16:40 +0000
Subject: [New-bugs-announce] [issue25824] 32-bit 2.7.11 installer creates
 registry keys that are incompatible with the installed python27.dll
Message-ID: <1449584200.04.0.891595448742.issue25824@psf.upfronthosting.co.za>


New submission from Arnaud Diederen:

[First of all let me say I'm not all that familiar with Windows, so please let me know if the wording in my analysis below is not clear and/or misleading.]

It would appear the 32-bit installer for Python 2.7.11 creates the registry key:
---
HKLM\Software\Wow6432Node\Python\PythonCore\2.7\PythonPath
---
(...just like previous 2.7 versions did.)

However, registry accesses (PC/getpathp.c's getpythonpath()) are done like so:
---
    (...)
    keyBuf = keyBufPtr = PyMem_RawMalloc(keyBufLen);
    if (keyBuf==NULL) goto done;

    memcpy_s(keyBufPtr, keyBufLen, keyPrefix, sizeof(keyPrefix)-sizeof(WCHAR));
    keyBufPtr += Py_ARRAY_LENGTH(keyPrefix) - 1;
    mbstowcs(keyBufPtr, PyWin_DLLVersionString, versionLen);
    (...)
---
where 'PyWin_DLLVersionString' now is "2.7-32":
---
.rsrc:1E2760FA                 unicode 0, <2.7-32>,0
---
(it used to be "2.7" in previous versions) 


Thus, the key that python27.dll builds is:
 HKLM\Software\Wow6432Node\Python\PythonCore\2.7-32\PythonPath
and not
 HKLM\Software\Wow6432Node\Python\PythonCore\2.7\PythonPath

and consequently the runtime cannot build a proper sys.path, which causes embedded interpreters to fail loading core modules.

As a workaround, it seems renaming the registry key to its "-32"-suffixed name, does help.

----------
components: Installation
messages: 256113
nosy: aundro
priority: normal
severity: normal
status: open
title: 32-bit 2.7.11 installer creates registry keys that are incompatible with the installed python27.dll
type: behavior
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25824>
_______________________________________

From report at bugs.python.org  Tue Dec  8 14:29:34 2015
From: report at bugs.python.org (David Edelsohn)
Date: Tue, 08 Dec 2015 19:29:34 +0000
Subject: [New-bugs-announce] [issue25825] AIX shared library extension
 modules installation broken
Message-ID: <1449602974.51.0.754649695687.issue25825@psf.upfronthosting.co.za>


New submission from David Edelsohn:

AIX requires helper scripts to build Python shared extension modules.  The definitions and Makefile installation rules have bitrotted.

Makefile.pre.in:

      @if [ -s Programs/python.exp -a \

except python.exp is created in Modules/python.exp, not Programs.exp

               $(INSTALL_DATA) Programs/python.exp             \
                               $(DESTDIR)$(LIBPL)/python.exp;

Post-substitution Makefile.pre:

BINLIBDEST=     $(LIBDIR)/python$(VERSION)
LIBDEST=        $(SCRIPTDIR)/python$(VERSION)
LIBPL=          $(LIBDEST)/config-$(LDVERSION)

configure.ac:

        AIX*)
                BLDSHARED="\$(srcdir)/Modules/ld_so_aix \$(CC) -bI:\$(srcdir)/Modules/python.exp"
                LDSHARED="\$(BINLIBDEST)/config/ld_so_aix \$(CC) -bI:\$(BINLIBDEST)/config/python.exp"

which is forever enshrined in _sysconfigdata.py

In other words, configure sets LDSHARED to $(BINLIBDEST)/config, which does not exist in current installations.  And Makefile installs the files in LIBPL, which is based on LIBDEST (prefix and exec_prefix could be different).

And the files are not installed, because the installation tests Programs/python.exp instead of Modules/python.exp.

Changing Makefile.pre.in to test Modules/python.exp is easy enough as a partial fix.

What is the preferred location to install the files so that configure.ac and Makefile.pre.in can be adjusted to match each other?

----------
components: Installation
messages: 256123
nosy: David.Edelsohn
priority: normal
severity: normal
status: open
title: AIX shared library extension modules installation broken
type: behavior
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25825>
_______________________________________

From report at bugs.python.org  Tue Dec  8 14:51:35 2015
From: report at bugs.python.org (David Wahlund)
Date: Tue, 08 Dec 2015 19:51:35 +0000
Subject: [New-bugs-announce] [issue25826] imaplib can't process lines after
 starttls
Message-ID: <1449604295.12.0.701575427107.issue25826@psf.upfronthosting.co.za>


New submission from David Wahlund:

File "C:\Python34\lib\imaplib.py", line 536, in login
    typ, dat = self._simple_command('LOGIN', user, self._quote(password))
  File "C:\Python34\lib\imaplib.py", line 1141, in _simple_command
    return self._command_complete(name, self._command(name, *args))
  File "C:\Python34\lib\imaplib.py", line 956, in _command_complete
    typ, data = self._get_tagged_response(tag)
  File "C:\Python34\lib\imaplib.py", line 1076, in _get_tagged_response
    self._get_response()
  File "C:\Python34\lib\imaplib.py", line 984, in _get_response
    resp = self._get_line()
  File "C:\Python34\lib\imaplib.py", line 1098, in _get_line
    if not line.endswith(b'\r\n'):
TypeError: endswith first arg must be str or a tuple of str, not bytes

imaplib uses SSLContext to initiate a SSLSocket. It overrides makefile() from Socket. It in turn uses TextIOWrapper on top of the stream. TextIOWrapper.readline() returns an Unicode str but IMAP4._get_line() expects bytes.

----------
messages: 256124
nosy: David Wahlund
priority: normal
severity: normal
status: open
title: imaplib can't process lines after starttls
type: crash
versions: Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25826>
_______________________________________

From report at bugs.python.org  Wed Dec  9 02:45:54 2015
From: report at bugs.python.org (Zachary Ware)
Date: Wed, 09 Dec 2015 07:45:54 +0000
Subject: [New-bugs-announce] [issue25827] Support ICC in configure
Message-ID: <1449647154.73.0.177335074012.issue25827@psf.upfronthosting.co.za>


New submission from Zachary Ware:

Attached is a patch that adds support for ICC to configure, making it easier to build with ICC on Unix and adjusting arguments to better fit ICC.

- Adds '--with-icc' argument to configure, which sets 'CC=icc' and 'CXX=icpc'
- Adds support for ICC PGO
- Prevents '-Wno-unused-result' from being added to CFLAGS if CC=icc (issue24709)
- Adds '-fp-model strict' to BASECFLAGS (I'm not 100% sure that's the right place, perhaps CFLAGS_NODIST would be better?).  Adding '-fp-model strict' clears up all the failures on the Ubuntu ICC Non-Debug buildbot, and most of the failures I get on OSX with -O3.  From a quick run of the 'math' benchmarks (perf.py -b math), adding '-fp-model strict' does not hurt performance (with the flag was always faster or negligibly slower).

Be sure to run autoreconf before testing.

----------
components: Build
files: configure_icc.diff
keywords: patch
messages: 256141
nosy: r.david.murray, zach.ware
priority: normal
severity: normal
stage: patch review
status: open
title: Support ICC in configure
type: enhancement
versions: Python 2.7, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41272/configure_icc.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25827>
_______________________________________

From report at bugs.python.org  Wed Dec  9 03:03:24 2015
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 09 Dec 2015 08:03:24 +0000
Subject: [New-bugs-announce] [issue25828] PyCode_Optimize() (peephole
 optimizer) doesn't handle KeyboardInterrupt correctly
Message-ID: <1449648204.19.0.769728792688.issue25828@psf.upfronthosting.co.za>


New submission from STINNER Victor:

The peephole optimizer computes 2**(2**100), but if I press CTRL+c (the result will probably kills my memory anyway), I get an assertion error (with a Python compiled in debug mode).

$ ./python
>>> 2**(2**100)
^C
python: Python/ceval.c:1218: PyEval_EvalFrameEx: Assertion `!PyErr_Occurred()' failed.
Abandon (core dumped)

fold_binops_on_constants() returns 0 with an exception (KeyboardInterrupt) raised. The problem is in the caller which doesn't handle the exception properly:

                if (h >= 0 &&
                    ISBASICBLOCK(blocks, h, i-h+1)  &&
                    fold_binops_on_constants(&codestr[i], consts, CONST_STACK_LASTN(2))) {
                    i -= 2;
                    memset(&codestr[h], NOP, i - h);
                    assert(codestr[i] == LOAD_CONST);
                    CONST_STACK_POP(2);
                    CONST_STACK_PUSH_OP(i);
                }

There is probably the same error on fold_unaryops_on_constants().


Python 2.7 looks to behave correctly:

$ python2.7
>>> 2**(2**100)
^C
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
KeyboardInterrupt


But in fact Python 2.7 is much worse :-D Peephole optimizer of Python 2.7 clears *all* exceptions (!) and it only optimizes 2**100, but not 2**(2**100). That's why the bug is not easily reproduced on Python 2.7. fold_binops_on_constants():

    if (newconst == NULL) {
        if(!PyErr_ExceptionMatches(PyExc_KeyboardInterrupt))
            PyErr_Clear();
        return 0;
    }

----------
messages: 256143
nosy: haypo
priority: normal
severity: normal
status: open
title: PyCode_Optimize() (peephole optimizer) doesn't handle KeyboardInterrupt correctly
type: crash
versions: Python 2.7, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25828>
_______________________________________

From report at bugs.python.org  Wed Dec  9 05:04:34 2015
From: report at bugs.python.org (Ami Koren)
Date: Wed, 09 Dec 2015 10:04:34 +0000
Subject: [New-bugs-announce] [issue25829] Mixing multiprocessing pool and
 subprocess may create zombie process, and cause program to hang.
Message-ID: <1449655474.19.0.730082771595.issue25829@psf.upfronthosting.co.za>


New submission from Ami Koren:

Happens on Linux (Debian), Linux version 3.16.0-4-amd64 .
Seems like a multiprocessing issue.

When I use both multiprocessing pool and subprocess somewhere in the same python program, sometimes the subprocess become
'zombie', and the parent wait for it forever.

Reproduce:
 run the attached script (I ran it on both python 3.4 and 3.5), and wait (up to a minute in my
computer). Eventually, the script will hang (wait forever).

After it hangs:
ps -ef | grep "hang_multiprocess\|ls"

You should see now the "[ls] <defunct>" process - zombie.


Analysis:
Players:
- Parent process
- Subprocess Child - forked by parent using subprocess.popen()
- Handle_workers thread - multiprocessing thread responsible for verifying all workers are OK, and create them if not.
- Multiprocessing Worker - forked by multiprocessing, either at handle_workers thread context, or at main thread context.

The problem, in a nutshell, is that Handle_workers thread forks a Worker, while Subprocess Child creation.
This causes one of the Child pipes to be 'copied' to the Worker. When the Subprocess Child finishes, the
pipe is still alive (at Worker), hence Parent Process wait forever for the pipe to finish. Child turn into zombie because Parent doesn't reach the communicate/wait line.

In more details:
- The problematic line at subprocess is at  subprocess.py->_execute_child(), before  'while True:' loop, where errpipe_read pipe is read.
- The entry point at multiprocessing is at multiprocessing/pool.py->_handle_workers(). There the thread sleeps for 0.1,
  and then try to create (=fork) new workers.

Handle_workers thread 'copies' errpipe_read to the forked Worker. Hence the pipe never gets closed.

To me, it seems like a multiprocessing issue: The forking from a thread at multiprocessing module is the cause for this mess.

I'm a newbe at Python (first bug launched), so please be patient if I missed anything or jumped into non-based conclusions.

----------
components: Extension Modules
files: hang_multiprocess_subprocess.py
messages: 256150
nosy: amikoren at yahoo.com
priority: normal
severity: normal
status: open
title: Mixing multiprocessing pool and subprocess may create zombie process, and cause program to hang.
type: behavior
versions: Python 3.4, Python 3.5
Added file: http://bugs.python.org/file41275/hang_multiprocess_subprocess.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25829>
_______________________________________

From report at bugs.python.org  Wed Dec  9 06:57:32 2015
From: report at bugs.python.org (flying sheep)
Date: Wed, 09 Dec 2015 11:57:32 +0000
Subject: [New-bugs-announce] [issue25830] _TypeAlias: Discrepancy between
 docstring and behavior
Message-ID: <1449662252.92.0.779493267097.issue25830@psf.upfronthosting.co.za>


New submission from flying sheep:

_TypeAlias claims in its docstring that ?It can be used in instance and subclass checks?, yet promptly contradicts itself if you try it: ?Type aliases cannot be used with isinstance().?

it would be useful to either document (and therefore bless) type_impl, or make it actually work with isinstance (probably by delegating to type_impl)

----------
components: Library (Lib)
messages: 256154
nosy: flying sheep
priority: normal
severity: normal
status: open
title: _TypeAlias: Discrepancy between docstring and behavior
type: behavior
versions: Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25830>
_______________________________________

From report at bugs.python.org  Wed Dec  9 14:04:21 2015
From: report at bugs.python.org (Isaac Schwabacher)
Date: Wed, 09 Dec 2015 19:04:21 +0000
Subject: [New-bugs-announce] [issue25831] dbm.gnu leaks file descriptors on
 .reorganize()
Message-ID: <1449687861.19.0.740703646408.issue25831@psf.upfronthosting.co.za>


New submission from Isaac Schwabacher:

I found because test_dbm_gnu fails on NFS; my initial thought was that the test was failing to close a file somewhere (similarly to #20876), but a little digging suggested that the problem is in dbm.gnu itself:

    $ ./python
    Python 3.5.1 (default, Dec  9 2015, 11:55:23) 
    [GCC 4.8.3 20140911 (Red Hat 4.8.3-9)] on linux
    Type "help", "copyright", "credits" or "license" for more information.
    >>> import dbm.gnu
    >>> import subprocess
    >>> db = dbm.gnu.open('foo', 'c')
    >>> db.reorganize()
    >>> db.close()
    >>> subprocess.check_call(['lsof', 'foo'])
    COMMAND     PID        USER  FD   TYPE DEVICE SIZE/OFF        NODE NAME
    python  2302377 schwabacher mem-W  REG   0,52    98304 25833923756 foo
    0

A quick look at _gdbmmodule.c makes clear that the problem is upstream, but their bug tracker has 9 total entries... The best bet might just be to skip the test on NFS.

----------
components: Library (Lib)
messages: 256159
nosy: ischwabacher
priority: normal
severity: normal
status: open
title: dbm.gnu leaks file descriptors on .reorganize()
type: behavior
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25831>
_______________________________________

From report at bugs.python.org  Thu Dec 10 09:08:20 2015
From: report at bugs.python.org (Ram Rachum)
Date: Thu, 10 Dec 2015 14:08:20 +0000
Subject: [New-bugs-announce] [issue25832] Document weird behavior of
 `finally` when it has `break` in it
Message-ID: <1449756500.07.0.727119628461.issue25832@psf.upfronthosting.co.za>


New submission from Ram Rachum:

Today I spent 30 minutes because of weird behavior of `finally` when it has a `break` statement inside of it. (The behavior is that the exception gets suppressed, which I found unexpected.) I think this behavior should be documented.

Example:

    
    
    c:\Users\Administrator\Desktop>cat s.py                    
    for x in [1, 2, 3]:                                        
      try:                                                     
        1/0                                                    
      finally:                                                 
        break                                                  
    print(x)                                                   
                                                              
    c:\Users\Administrator\Desktop>c:\Python34\python.exe s.py 
    1

----------
assignee: docs at python
components: Documentation
messages: 256173
nosy: cool-RR, docs at python
priority: normal
severity: normal
status: open
title: Document weird behavior of `finally` when it has `break` in it
type: enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25832>
_______________________________________

From report at bugs.python.org  Thu Dec 10 10:15:28 2015
From: report at bugs.python.org (Chad Moore)
Date: Thu, 10 Dec 2015 15:15:28 +0000
Subject: [New-bugs-announce] [issue25833] pyvenv: venvs cannot be moved
 because activate scripts hard-code paths
Message-ID: <1449760528.92.0.724215878047.issue25833@psf.upfronthosting.co.za>


New submission from Chad Moore:

venv/bin/activate contains an absolute path to the virtual environment.  Is it possible to make that relative from activate itself so that the entire venv can be moved elsewhere and still work?

I found this using Jenkins to get a Perforce workspace, then build a virtual environment, and clone that for downstream jobs.  The cloned workspaces are extracted elsewhere and when they activate the environment they're actually pointing back to the upstream job's venv.

Feel free to route this request as appropriate.  I'm a new tracker user.  Thanks!

----------
components: Library (Lib)
messages: 256176
nosy: moorecm
priority: normal
severity: normal
status: open
title: pyvenv: venvs cannot be moved because activate scripts hard-code paths
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25833>
_______________________________________

From report at bugs.python.org  Thu Dec 10 14:01:21 2015
From: report at bugs.python.org (=?utf-8?q?Adam_Barto=C5=A1?=)
Date: Thu, 10 Dec 2015 19:01:21 +0000
Subject: [New-bugs-announce] [issue25834] getpass falls back when sys.stdin
 is changed
Message-ID: <1449774081.69.0.580172668816.issue25834@psf.upfronthosting.co.za>


New submission from Adam Barto?:

There is a check in Lib/getpass.py:win_getpass that causes a fallback version to be used when `sys.stdin` is changed. I change `sys.stdin` in my `win_unicode_console` package, and in this situation there is no reason to use the fallback version (see https://github.com/Drekin/win-unicode-console/issues/24).

It seems the check was added because of some issue with IDLE (https://hg.python.org/cpython/rev/6d5ac3c43416). Could this check be changed so it satisfies all the needs?

----------
components: Library (Lib), Windows
messages: 256180
nosy: Drekin, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: getpass falls back when sys.stdin is changed
type: behavior
versions: Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25834>
_______________________________________

From report at bugs.python.org  Thu Dec 10 21:12:41 2015
From: report at bugs.python.org (calin marina)
Date: Fri, 11 Dec 2015 02:12:41 +0000
Subject: [New-bugs-announce] [issue25835] httplib uses print for debugging
Message-ID: <1449799961.35.0.0559647845102.issue25835@psf.upfronthosting.co.za>


New submission from calin marina:

httplib is using print for debugging messages and it is causing a lot of annoyance in multiprocess debugging or even single process but headless running...
As it is still used by a lot of libraries, including requests the recommended one over this for HTTP protocol client I thought sharing my update lib using logging module would be useful by someone

----------
components: Library (Lib)
files: mywork.patch
hgrepos: 326
keywords: patch
messages: 256184
nosy: calin marina
priority: normal
severity: normal
status: open
title: httplib uses print for debugging
type: behavior
versions: Python 2.7
Added file: http://bugs.python.org/file41280/mywork.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25835>
_______________________________________

From report at bugs.python.org  Thu Dec 10 23:13:55 2015
From: report at bugs.python.org (Russell Keith-Magee)
Date: Fri, 11 Dec 2015 04:13:55 +0000
Subject: [New-bugs-announce] [issue25836] Documentation of MAKE_FUNCTION is
 still incorrect
Message-ID: <1449807235.86.0.17166679506.issue25836@psf.upfronthosting.co.za>


New submission from Russell Keith-Magee:

Refs Issue16554, Issue13026, Issue14349, and probably others.

The documentation for the interpretation of the argc argument to MAKE_FUNCTION in Doc/library/dis.rst is incorrect. 

As of 13 August 2015, the docs say:

"""
Pushes a new function object on the stack.  From bottom to top, the consumed
stack must consist of:

   * ``argc & 0xFF`` default argument objects in positional order
   * ``(argc >> 8) & 0xFF`` pairs of name and default argument, with the name
     just below the object on the stack, for keyword-only parameters
   * ``(argc >> 16) & 0x7FFF`` parameter annotation objects
   * a tuple listing the parameter names for the annotations (only if there are
     ony annotation objects)
   * the code associated with the function (at TOS1)
   * the :term:`qualified name` of the function (at TOS)
"""

However, this doesn't capture the fact that:

 * if there are annotations, the number of default arguments returned by `argc & 0xFF` must be reduced by `(argc >> 16) & 0x7FFF`

 * The value `(argc >> 16) & 0x7FFF` for the number of annotations *includes* the "extra" entry for the tuple describing which arguments the annotations apply to. This means that `(argc >> 16) & 0x7FFF` will be either 0, or 2+; it can't be 1 (because if you have one annotation, you must also have a tuple describing which arguments is annotated).

----------
assignee: docs at python
components: Documentation
messages: 256189
nosy: docs at python, freakboy3742
priority: normal
severity: normal
status: open
title: Documentation of MAKE_FUNCTION is still incorrect
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25836>
_______________________________________

From report at bugs.python.org  Thu Dec 10 23:38:08 2015
From: report at bugs.python.org (Alexander Whatley)
Date: Fri, 11 Dec 2015 04:38:08 +0000
Subject: [New-bugs-announce] [issue25837] Errors when Installing Anaconda 3
Message-ID: <1449808688.5.0.398469382022.issue25837@psf.upfronthosting.co.za>


New submission from Alexander Whatley:

Got some error messages while installing Python 3.5.1 (Anaconda). Here is the traceback:

Extracting packages ...
[      COMPLETE      ]|##################################################| 100%
Unlinking packages ...
menuinst Exception:Traceback (most recent call last):                    |   0%
  File "C:\Users\Alexander\Anaconda3\lib\site-packages\conda\install.py", line 3
43, in mk_menus
    env_setup_cmd=env_setup_cmd)
TypeError: install() got an unexpected keyword argument 'root_prefix'
menuinst Exception:Traceback (most recent call last):                    |  25%
  File "C:\Users\Alexander\Anaconda3\lib\site-packages\conda\install.py", line 3
43, in mk_menus
TypeError: install() got an unexpected keyword argument 'root_prefix'
menuinst Exception:Traceback (most recent call last):###########         |  82%
  File "C:\Users\Alexander\Anaconda3\lib\site-packages\conda\install.py", line 3
43, in mk_menus
TypeError: install() got an unexpected keyword argument 'root_prefix'
[      COMPLETE      ]|##################################################| 100%
Linking packages ...
        1 file(s) copied.##############################                  |  65%
menuinst Exception:Traceback (most recent call last):#######             |  74%
  File "C:\Users\Alexander\Anaconda3\lib\site-packages\conda\install.py", line 3
43, in mk_menus
    try:
TypeError: install() got an unexpected keyword argument 'root_prefix'
menuinst Exception:Traceback (most recent call last):##############      |  88%
  File "C:\Users\Alexander\Anaconda3\lib\site-packages\conda\install.py", line 3
43, in mk_menus
    try:
TypeError: install() got an unexpected keyword argument 'root_prefix'
menuinst Exception:Traceback (most recent call last):##################  |  97%
  File "C:\Users\Alexander\Anaconda3\lib\site-packages\conda\install.py", line 3
43, in mk_menus
    try:
TypeError: install() got an unexpected keyword argument 'root_prefix'
[      COMPLETE      ]|##################################################| 100%

----------
messages: 256192
nosy: aewhatley
priority: normal
severity: normal
status: open
title: Errors when Installing Anaconda 3

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25837>
_______________________________________

From report at bugs.python.org  Fri Dec 11 02:36:46 2015
From: report at bugs.python.org (Mikhail Gulyaev)
Date: Fri, 11 Dec 2015 07:36:46 +0000
Subject: [New-bugs-announce] [issue25838] Lib/httplib.py: Resend http
 request on server close connection
Message-ID: <1449819406.11.0.669175603507.issue25838@psf.upfronthosting.co.za>


New submission from Mikhail Gulyaev:

Hello guys!

Recently I recived some strange behavior for sending http requests using httplib

My python script uses httplib and interacts with a web server which have a keep-alive timeout 5 seconds. Script makes PUT requests and sends files to server. At first time it works ok. Then after 5 seconds server closes connection. And then I doing second PUT request, that fails in two stages:
 - HTTPConnection trys to send PUT request to closed socket.
 - HTTPConnection reconnects to server and sends request again but no file sended.
This behavior was checked using wireshark and debug output of httplib.

The best solution IMHO would be to checking socket state on each request, and reconnects if needed - but it seems this issue has no unique solution.

So I offer a patch which simply rewinds file before sending if needed. 
hasattr(data,'tell') could be used in checking condition
-----------------------------------
diff -r 002d8b981128 Lib/httplib.py
--- a/Lib/httplib.py	Wed Dec 09 19:44:30 2015 +0200
+++ b/Lib/httplib.py	Fri Dec 11 12:59:47 2015 +0600
@@ -865,6 +865,7 @@
         blocksize = 8192
         if hasattr(data,'read') and not isinstance(data, array):
             if self.debuglevel > 0: print "sendIng a read()able"
+            if data.tell() > 0: data.seek(0) # rewind for retry send file
             datablock = data.read(blocksize)
             while datablock:
                 self.sock.sendall(datablock)
-----------------------------------

----------
messages: 256204
nosy: gmixo
priority: normal
severity: normal
status: open
title: Lib/httplib.py: Resend http request on server close connection
type: enhancement
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25838>
_______________________________________

From report at bugs.python.org  Fri Dec 11 03:44:59 2015
From: report at bugs.python.org (Mark Lundeberg)
Date: Fri, 11 Dec 2015 08:44:59 +0000
Subject: [New-bugs-announce] [issue25839] negative zero components are
 ignored in complex number literals
Message-ID: <1449823499.05.0.146335841063.issue25839@psf.upfronthosting.co.za>


New submission from Mark Lundeberg:

Although -0.0 and +0.0 compare as equal using the == operator, they are distinct floating point numbers and in some cases behave differently. (See more information on the wikipedia article "Signed zero".) The distinction between +0.0 and -0.0 is most important in complex arithmetic, for example it is conventional and useful that sqrt(-1+0i) ==> +i and sqrt(-1-0i) ==> -i. Python currently allows the floating point number -0.0 to be entered as a literal:

>>> -0.0
-0.0

Complex floating point numbers in python also can hold negative zero components, as shown in their repr()

>>> -(1+0j)
(-1-0j)

However they cannot be input directly as literals; it is currently necessary to use the above construction. Unfortunately the output of the repr() cannot be used as a string literal to obtain the same number:

>>> (-1-0j)
(-1+0j)

except, in contrast:

>>> complex('-1-0j')
(-1-0j)


The literal -1-0j should yield a complex number with negative zero imaginary part. Note also that complex literals with negative zero real parts have the same bug, e.g. -0+1j is not the same as -(0-1j)

----------
components: Interpreter Core
messages: 256209
nosy: Mark Lundeberg
priority: normal
severity: normal
status: open
title: negative zero components are ignored in complex number literals
type: behavior
versions: Python 2.7, Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25839>
_______________________________________

From report at bugs.python.org  Fri Dec 11 10:02:00 2015
From: report at bugs.python.org (leewz)
Date: Fri, 11 Dec 2015 15:02:00 +0000
Subject: [New-bugs-announce] [issue25840] Allow `False` to be passed to
 `filter`
Message-ID: <1449846120.95.0.0940124187557.issue25840@psf.upfronthosting.co.za>


New submission from leewz:

Meaning:

    filter(False, lst)
    == (x for x in lst if not x)
    == itertools.filterfalse(None, lst)

I understand that it is a very minor enhancement, and with not much benefit. I just happened to think about it, and wondered why it didn't already exist. I figured it wouldn't hurt to put the idea out here.

(If anyone is interested, I was looking into ways that filter/map/itertools could "unwrap" each other at the C level to improve composition of generators, inspired by the functools.partial optimization.)

----------
messages: 256218
nosy: leewz
priority: normal
severity: normal
status: open
title: Allow `False` to be passed to `filter`
type: enhancement
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25840>
_______________________________________

From report at bugs.python.org  Fri Dec 11 10:42:25 2015
From: report at bugs.python.org (Denis Savenko)
Date: Fri, 11 Dec 2015 15:42:25 +0000
Subject: [New-bugs-announce] [issue25841] In FancyURLopener error in example
 with http address.
Message-ID: <1449848545.54.0.701964592914.issue25841@psf.upfronthosting.co.za>


New submission from Denis Savenko:

In documentation from this page https://docs.python.org/3.5/library/urllib.request.html#examples in examples uses default address to python site with http. ( http://python.org/ ). But now python.org use https. When i try use example in ipython i get I/0 error, but error is very simple - http change by https. I found this error on many pages, where use http://python.org/ address, but on FancyURLopener example compiller error very difficult for understanding.

----------
assignee: docs at python
components: Documentation
messages: 256221
nosy: Denis Savenko, docs at python
priority: normal
severity: normal
status: open
title: In FancyURLopener error in example with http address.
versions: Python 3.3, Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25841>
_______________________________________

From report at bugs.python.org  Fri Dec 11 12:02:54 2015
From: report at bugs.python.org (Laura Creighton)
Date: Fri, 11 Dec 2015 17:02:54 +0000
Subject: [New-bugs-announce] [issue25842] Installer does not set permissions
 correctly?
Message-ID: <1449853374.94.0.359716454722.issue25842@psf.upfronthosting.co.za>


New submission from Laura Creighton:

This in from python-list.  2 complaints.  
conflict with a notepad++ plugin and incorrect permissions.

Date:    Fri, 11 Dec 2015 16:30:32 +0000
To:      "python-list at python.org" <python-list at python.org>
From:    Jay Hamm <hammj at vmware.com>
Subject: python 351x64


Hi

I was trying to use your windows version of python 3.5.1 x64.

It has a conflict with a notepad++ plugin NppFTP giving api-ms-win-crt-runtime-
I1-1-0.dll error on start up.

This seems pretty well documented on the web. The work around is to delete the 
plugin and reinstall since it borks the install.

Since about every other admin I've ever known uses notepad++, you might want to
 fix this.

Also your installer fails to set the permissions correctly:

H:\>py -m pip install requests
Collecting requests
  Downloading requests-2.8.1-py2.py3-none-any.whl (497kB)
    100% |################################| 499kB 875kB/s
Installing collected packages: requests
Exception:
Traceback (most recent call last):
  File "C:\Program Files\Python35\lib\site-packages\pip\basecommand.py", line 2
11, in main    status = self.run(options, args)
  File "C:\Program Files\Python35\lib\site-packages\pip\commands\install.py", l
ine 311, in run    root=options.root_path,
  File "C:\Program Files\Python35\lib\site-packages\pip\req\req_set.py", line 6
46, in install    **kwargs
  File "C:\Program Files\Python35\lib\site-packages\pip\req\req_install.py", li
ne 803, in install    self.move_wheel_files(self.source_dir, root=root)
  File "C:\Program Files\Python35\lib\site-packages\pip\req\req_install.py", li
ne 998, in move_wheel_files    isolated=self.isolated,
  File "C:\Program Files\Python35\lib\site-packages\pip\wheel.py", line 339, in
 move_wheel_files    clobber(source, lib_dir, True)
  File "C:\Program Files\Python35\lib\site-packages\pip\wheel.py", line 310, in
 clobber    ensure_dir(destdir)
  File "C:\Program Files\Python35\lib\site-packages\pip\utils\__init__.py", lin
e 71, in ensure_dir    os.makedirs(path)
  File "C:\Program Files\Python35\lib\os.py", line 241, in makedirs    mkdir(na
me, mode) PermissionError: [WinError 5] Access is denied: 'C:\\Program Files\\P
ython35\\Lib\\site-packages\\requests'

Once I gave myself control it started working.

This is pretty shoddy for released software.
Thanks,
Jacob Hamm (Jay) VCP-DCV, RHCE
Senior Cloud Services Engineer - VMware vCloud Air

380 Interlocken Crescent Blvd - Ste 500, Broomfield CO 80021
Office 303 942 4638 - hammj at vmware.com<mailto:hammj at vmware.com>
Want to learn more about VMware vCloud Air?
Go to http://vcloud.vmware.com/tutorials
[vCloudAir]

----------
components: Installation, Windows
messages: 256223
nosy: lac, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Installer does not set permissions correctly?
versions: Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25842>
_______________________________________

From report at bugs.python.org  Fri Dec 11 14:23:13 2015
From: report at bugs.python.org (Tijs Van Oevelen)
Date: Fri, 11 Dec 2015 19:23:13 +0000
Subject: [New-bugs-announce] [issue25843]
 unexpected-output-using-pythons-ternary-operator-in-combination-with-lambda
Message-ID: <1449861793.94.0.13967463155.issue25843@psf.upfronthosting.co.za>


New submission from Tijs Van Oevelen:

The bug is described on Stack Overflow in length:

http://stackoverflow.com/questions/34100732/unexpected-output-using-pythons-ternary-operator-in-combination-with-lambda

----------
messages: 256229
nosy: Tijs Van Oevelen
priority: normal
severity: normal
status: open
title: unexpected-output-using-pythons-ternary-operator-in-combination-with-lambda
type: behavior
versions: Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25843>
_______________________________________

From report at bugs.python.org  Fri Dec 11 23:33:27 2015
From: report at bugs.python.org (Alexander Riccio)
Date: Sat, 12 Dec 2015 04:33:27 +0000
Subject: [New-bugs-announce] [issue25844] Pylauncher,
 launcher.c: Assigning NULL to a pointer instead of testing against
 NULL
Message-ID: <1449894807.83.0.191660385398.issue25844@psf.upfronthosting.co.za>


New submission from Alexander Riccio:

I found this while writing up a separate bug (CPython doesn't use static analysis!).

In PC/launcher.c, get_env has a bug:

        /* Large environment variable. Accept some leakage */
        wchar_t *buf2 = (wchar_t*)malloc(sizeof(wchar_t) * (result+1));
        if (buf2 = NULL) {
            error(RC_NO_MEMORY, L"Could not allocate environment buffer");
        }
        GetEnvironmentVariableW(key, buf2, result);
        return buf2;

See: https://hg.python.org/cpython/file/tip/PC/launcher.c#l117


Instead of `buf2 == NULL`, Vinay Sajip wrote `buf2 = NULL`. The commit where the error was introduced: https://hg.python.org/cpython/rev/4123e002a1af

Thus, whatever value was in buf2 is lost, the branch is NOT taken (because buf2 evaluates to false), and GetEnvironmentVariableW will (probably) cause an access violation. 


Compiling with /analyze found this quite easily:

c:\pythondev\repo\pc\launcher.c(117): warning C6282: Incorrect operator:  assignment of constant in Boolean context. Consider using '==' instead.

----------
components: Windows
messages: 256254
nosy: Alexander Riccio, paul.moore, steve.dower, tim.golden, vinay.sajip, zach.ware
priority: normal
severity: normal
status: open
title: Pylauncher, launcher.c: Assigning NULL to a pointer instead of testing against NULL

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25844>
_______________________________________

From report at bugs.python.org  Fri Dec 11 23:50:49 2015
From: report at bugs.python.org (Alexander Riccio)
Date: Sat, 12 Dec 2015 04:50:49 +0000
Subject: [New-bugs-announce] [issue25845] _ctypes\cfield.c identical
 subexpressions in Z_set
Message-ID: <1449895849.48.0.817393868037.issue25845@psf.upfronthosting.co.za>


New submission from Alexander Riccio:

I found this while writing up a separate bug (CPython doesn't use static analysis!).


In _ctypes/cfield.c, Z_set has a bug of some sort:

    if (PyLong_Check(value) || PyLong_Check(value)) {

See: https://hg.python.org/cpython/file/tip/Modules/_ctypes/cfield.c#l1378

...which has been there for at least 5 years: https://hg.python.org/cpython/rev/cab14be0ada1


I'm not sure what the original programmer meant - it's been around forever & I don't know what was there before it - but PyLong_Check(value) is evaluated twice. Which doesn't really make sense.

Compiling with /analyze found this quite easily:

c:\pythondev\repo\modules\_ctypes\cfield.c(1378): warning C6287: Redundant code:  the left and right sub-expressions are identical.



There's a similar issue in P_set, at line 1486.

----------
components: ctypes
messages: 256256
nosy: Alexander Riccio, amaury.forgeotdarc, belopolsky, meador.inge
priority: normal
severity: normal
status: open
title: _ctypes\cfield.c identical subexpressions in Z_set

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25845>
_______________________________________

From report at bugs.python.org  Sat Dec 12 00:01:29 2015
From: report at bugs.python.org (Alexander Riccio)
Date: Sat, 12 Dec 2015 05:01:29 +0000
Subject: [New-bugs-announce] [issue25846] Use of Py_ARRAY_LENGTH on pointer
 in posixmodule.c, win32_wchdir
Message-ID: <1449896489.9.0.639940283646.issue25846@psf.upfronthosting.co.za>


New submission from Alexander Riccio:

I found this while writing up a separate bug (CPython doesn't use static analysis!).

In modules/posixmodule.c, win32_wchdir uses Py_ARRAY_LENGTH on a wchar_t*:

    wchar_t _new_path[MAX_PATH], *new_path = _new_path;
    int result;
    wchar_t env[4] = L"=x:";

    if(!SetCurrentDirectoryW(path))
        return FALSE;
    result = GetCurrentDirectoryW(Py_ARRAY_LENGTH(new_path), new_path);


...instead of using Py_ARRAY_LENGTH(_new_path), the programmer wrote Py_ARRAY_LENGTH(new_path), doesn't work on pointers:

/* Get the number of elements in a visible array

   This does not work on pointers, or arrays declared as [], or function
   parameters. With correct compiler support, such usage will cause a build
   error (see Py_BUILD_ASSERT_EXPR).

   Written by Rusty Russell, public domain, http://ccodearchive.net/
*/
#define Py_ARRAY_LENGTH(array) \
    (sizeof(array) / sizeof((array)[0]))


The same issue occurs two lines later:

    if (result > Py_ARRAY_LENGTH(new_path)) {



Compiling with /analyze found this quite easily:

c:\pythondev\repo\modules\posixmodule.c(1354): warning C6384: Dividing sizeof a pointer by another value.

----------
components: Windows
messages: 256260
nosy: Alexander Riccio, larry, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Use of Py_ARRAY_LENGTH on pointer in posixmodule.c, win32_wchdir

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25846>
_______________________________________

From report at bugs.python.org  Sat Dec 12 00:59:47 2015
From: report at bugs.python.org (Alexander Riccio)
Date: Sat, 12 Dec 2015 05:59:47 +0000
Subject: [New-bugs-announce] [issue25847] CPython not using Visual Studio
 code analysis!
Message-ID: <1449899987.42.0.470300295936.issue25847@psf.upfronthosting.co.za>


New submission from Alexander Riccio:

Visual Studio comes with static analysis, enabled by /analyze (command line) or "Code analysis" in the project configuration dialog. Currently, none of the CPython projects in PCbuild have Code Analysis turned on, in any configuration.

I was going to write my first patch, for issue25386, but noticed this, ran a (partial) build with /analyze, and ended up filing three bugs instead (Issue25844, Issue25845, Issue25846) from bugs /analyze found.

There's quite a bad signal-to-noise ratio at the moment, as there's lots of variable shadowing, and there's lots of code that /analyze doesn't understand is benign (parsing a tuple into a variable confuses /analyze), but there is also lots of code that isn't *obviously* incorrect.

Of the code that's not obviously incorrect, /analyze usually complains about possibly out-of-bounds reads in very complex conditions, and I really can't tell. Some assertions would probably help.


Thoughts?

----------
components: Build
messages: 256265
nosy: Alexander Riccio, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: CPython not using Visual Studio code analysis!

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25847>
_______________________________________

From report at bugs.python.org  Sat Dec 12 12:01:12 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 12 Dec 2015 17:01:12 +0000
Subject: [New-bugs-announce] [issue25848] Tkinter tests failed on Windows
 buildbots
Message-ID: <1449939672.03.0.965226031522.issue25848@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Tkinter related tests are failed on 4 of 6 Windows 3.4 buildbots.

http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.4/builds/1418/steps/test/logs/stdio
http://buildbot.python.org/all/builders/AMD64%20Windows10%203.4/builds/220/steps/test/logs/stdio
http://buildbot.python.org/all/builders/AMD64%20Windows8%203.4/builds/779/steps/test/logs/stdio
http://buildbot.python.org/all/builders/AMD64%20Windows8.1%20Non-Debug%203.4/builds/333/steps/test/logs/stdio

======================================================================
ERROR: setUpModule (test.test_tcl)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\buildbot.python.org\3.4.kloth-win64\build\lib\test\test_tcl.py", line 685, in setUpModule
    tcl = Tcl()
  File "C:\buildbot.python.org\3.4.kloth-win64\build\lib\tkinter\__init__.py", line 1955, in Tcl
    return Tk(screenName, baseName, className, useTk)
  File "C:\buildbot.python.org\3.4.kloth-win64\build\lib\tkinter\__init__.py", line 1856, in __init__
    self.tk = _tkinter.create(screenName, baseName, className, interactive, wantobjects, useTk, sync, use)
_tkinter.TclError: Can't find a usable init.tcl in the following directories: 
    C:/buildbot.python.org/3.4.kloth-win64/build/PCbuild/lib/tcl8.6 C:/buildbot.python.org/3.4.kloth-win64/build/PCbuild/lib/tcl8.6 C:/buildbot.python.org/3.4.kloth-win64/build/lib/tcl8.6 C:/buildbot.python.org/3.4.kloth-win64/build/PCbuild/library C:/buildbot.python.org/3.4.kloth-win64/build/library C:/buildbot.python.org/3.4.kloth-win64/build/tcl8.6.1/library C:/buildbot.python.org/3.4.kloth-win64/tcl8.6.1/library



This probably means that Tcl wasn't installed properly.


----------------------------------------------------------------------

Is this a test suite defect, or there is an issue with using Tkinter on Windows? In latter case this is a release blocker.

----------
components: Tests, Tkinter, Windows
messages: 256287
nosy: larry, paul.moore, serhiy.storchaka, steve.dower, tim.golden, zach.ware
priority: release blocker
severity: normal
status: open
title: Tkinter tests failed on Windows buildbots
type: behavior
versions: Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25848>
_______________________________________

From report at bugs.python.org  Sat Dec 12 15:19:49 2015
From: report at bugs.python.org (=?utf-8?b?0JzQsNGA0Log0JrQvtGA0LXQvdCx0LXRgNCz?=)
Date: Sat, 12 Dec 2015 20:19:49 +0000
Subject: [New-bugs-announce] [issue25849] files,
 opened in unicode (text): write() returns symbols count,
 but seek() expect offset in bytes
Message-ID: <1449951589.63.0.511826880998.issue25849@psf.upfronthosting.co.za>


New submission from ???? ?????????:

It seems, that we should deprecate .seek() on files, opened in text mode.

Since it is not possible to seek to position between symbols. Yes, it is possible to decode UTF-8 (or other charset) starting from beginning of the file and count symbols, but it is EXTREMELY SLOW, and is not what user expect. If so, seeking from end of file back to begin may be implemented in even more hard and error-prone way.

Moreover, I consider that we should disallow seek in text files except seek() to begin of the file (position 0) or end of file (seek(0, SEEK_END)).

Seel also issue25190 #25190 about something related for that.

----------
components: IO, Library (Lib), Unicode
messages: 256291
nosy: ezio.melotti, haypo, mmarkk
priority: normal
severity: normal
status: open
title: files, opened in unicode (text): write() returns symbols count, but seek() expect offset in bytes
versions: Python 3.3, Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25849>
_______________________________________

From report at bugs.python.org  Sat Dec 12 16:20:25 2015
From: report at bugs.python.org (Sami Salonen)
Date: Sat, 12 Dec 2015 21:20:25 +0000
Subject: [New-bugs-announce] [issue25850] Building extensions with MSVC 2015
 Express fails
Message-ID: <1449955225.5.0.401578921369.issue25850@psf.upfronthosting.co.za>


New submission from Sami Salonen:

MSVC 2015 Express doesn't include the 64-bit compiler [1], and this causes distutils to fail to load proper compiler settings when using a 64-bit machine to compile extensions for 64-bit python. _msvccompiler.py tries to call "vcvarsall.bat amd64", but the VC\bin\amd64 directory contains only one file "vcmeta.dll".

[1] https://msdn.microsoft.com/en-us/library/hs24szh9(v=vs.140).aspx

----------
components: Distutils, Extension Modules, Windows
messages: 256296
nosy: Sami Salonen, dstufft, eric.araujo, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Building extensions with MSVC 2015 Express fails
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25850>
_______________________________________

From report at bugs.python.org  Sat Dec 12 17:43:27 2015
From: report at bugs.python.org (Laura Creighton)
Date: Sat, 12 Dec 2015 22:43:27 +0000
Subject: [New-bugs-announce] [issue25851] installing 3.5 on windows server
 2003 x86 R2 Standard Edition Sp2 ENU, 
Message-ID: <1449960207.46.0.30287402139.issue25851@psf.upfronthosting.co.za>


New submission from Laura Creighton:

Another one in to webmaster.

Somebody tried to install 3.5 on his windows server 2003 x86 R2 Standard Edition Sp2 ENU, and was told that Vista or later is required.

Is this correct behaviour, or did we forget about such people?  Near as
I can tell some of them can still be on their very last gasp of 
being supported by Microsoft.

----------
messages: 256298
nosy: lac
priority: normal
severity: normal
status: open
title: installing 3.5 on windows server 2003 x86 R2 Standard Edition Sp2 ENU,

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25851>
_______________________________________

From report at bugs.python.org  Sat Dec 12 17:59:22 2015
From: report at bugs.python.org (W. Trevor King)
Date: Sat, 12 Dec 2015 22:59:22 +0000
Subject: [New-bugs-announce] [issue25852] smtplib's SMTP.connect() should
 store the server name in ._host for .starttls()
Message-ID: <1449961162.47.0.978986314472.issue25852@psf.upfronthosting.co.za>


New submission from W. Trevor King:

With the current tip, starttls uses ._host when calling wrap_socket [1], but ._host is only setup in SMTP.__init__ [2].  Before #22921 [3] starttls would ignore ._host when SNI wasn't available locally.  But as far as I can tell, starttls has never used _host when connection happens via an explicit connect() call.  This leads to errors like [4]:

  >>> smtp = smtplib.SMTP()
  >>> smtp.connect(host="smtp.gmail.com", port=587)
  >>> smtp.ehlo()
  >>> smtp.starttls()
  File "smtp_test.py", line 10, in <module>
    smtp.starttls()
  File "/usr/lib/python3.4/smtplib.py", line 676, in starttls
    server_hostname=server_hostname)
  File "/usr/lib/python3.4/ssl.py", line 344, in wrap_socket
    _context=self)
  File "/usr/lib/python3.4/ssl.py", line 540, in __init__
    self.do_handshake()
  File "/usr/lib/python3.4/ssl.py", line 767, in do_handshake
    self._sslobj.do_handshake()
  ssl.SSLError: [SSL: TLSV1_ALERT_DECODE_ERROR] tlsv1 alert decode error (_ssl.c:598)

I think a better approach would be to move the ._host set into .connect (patch attached).  It would still happen in SMTP(host=?) because [5], but would also allow starttls when users use SMTP() and then call connect(host=?) explicitly.

I've formatted the patch with Git, but its simple enough that it should be easy to apply in Mercurial.  Still, let me know if I can make applying it easier by rerolling the patch.

[1]: https://hg.python.org/cpython/file/323c10701e5d/Lib/smtplib.py#l766
[2]: https://hg.python.org/cpython/file/323c10701e5d/Lib/smtplib.py#l244
[3]: http://bugs.python.org/issue22921
[4]: http://stackoverflow.com/questions/23616803/smtplib-smtp-starttls-fails-with-tlsv1-alert-decode-error
[5]: https://hg.python.org/cpython/file/323c10701e5d/Lib/smtplib.py#l251

----------
components: Library (Lib)
files: 0001-smtplib-Set-SMTP._host-in-.connect.patch
keywords: patch
messages: 256299
nosy: labrat
priority: normal
severity: normal
status: open
title: smtplib's SMTP.connect() should store the server name in ._host for .starttls()
type: behavior
versions: Python 3.3, Python 3.4, Python 3.5
Added file: http://bugs.python.org/file41291/0001-smtplib-Set-SMTP._host-in-.connect.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25852>
_______________________________________

From report at bugs.python.org  Sat Dec 12 18:09:50 2015
From: report at bugs.python.org (jamespharvey20)
Date: Sat, 12 Dec 2015 23:09:50 +0000
Subject: [New-bugs-announce] [issue25853] Compile error with pytime.h -
 struct timespec declared inside parameter list
Message-ID: <1449961790.19.0.27307751032.issue25853@psf.upfronthosting.co.za>


New submission from jamespharvey20:

When including pytime.h:

n file included from /usr/include/python3.5m/Python.h:65:0,
                 from src/package.c:25:
/usr/include/python3.5m/pytime.h:136:56: error: ?struct timespec? declared inside parameter list [-Werror]
 PyAPI_FUNC(int) _PyTime_AsTimespec(_PyTime_t t, struct timespec *ts);
                                                        ^
/usr/include/python3.5m/pytime.h:136:56: error: its scope is only this definition or declaration, which is probably not what you want [-Werror]
cc1: all warnings being treated as errors
error: command 'gcc' failed with exit status 1

----------
components: Library (Lib)
messages: 256301
nosy: jamespharvey20
priority: normal
severity: normal
status: open
title: Compile error with pytime.h - struct timespec declared inside parameter list
type: compile error
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25853>
_______________________________________

From report at bugs.python.org  Sat Dec 12 19:24:50 2015
From: report at bugs.python.org (Andrei Tumbar)
Date: Sun, 13 Dec 2015 00:24:50 +0000
Subject: [New-bugs-announce] [issue25854] rest in _interpolate_some is a
 list not str
Message-ID: <1449966290.96.0.564607381585.issue25854@psf.upfronthosting.co.za>


New submission from Andrei Tumbar:

Create a list called _rest from rest
then will del rest
instead of while rest:
for rest in _rest

----------
components: Interpreter Core
files: configparser.py
messages: 256307
nosy: Andrei Tumbar
priority: normal
severity: normal
status: open
title: rest in _interpolate_some is a list not str
type: compile error
versions: Python 3.4
Added file: http://bugs.python.org/file41294/configparser.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25854>
_______________________________________

From report at bugs.python.org  Sat Dec 12 23:13:51 2015
From: report at bugs.python.org (Jon Sobocinski)
Date: Sun, 13 Dec 2015 04:13:51 +0000
Subject: [New-bugs-announce] [issue25855] str.title()
Message-ID: <1449980031.11.0.249375758094.issue25855@psf.upfronthosting.co.za>


New submission from Jon Sobocinski:

Perhaps not a bug, but an odd behavior of pythons built in .title() method. When calling this method on a string such as this: "bill's", python will change the string to "Bill'S". This seems like a behavior that may want to be changed.

----------
components: Library (Lib)
messages: 256314
nosy: Jon Sobocinski
priority: normal
severity: normal
status: open
title: str.title()
type: behavior
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25855>
_______________________________________

From report at bugs.python.org  Sun Dec 13 11:17:44 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 13 Dec 2015 16:17:44 +0000
Subject: [New-bugs-announce] [issue25856] The __module__ attribute of
 itertools members is not interned
Message-ID: <1450023464.36.0.165437491365.issue25856@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

One of purposes of the STACK_GLOBAL opcode introduced in pickle protocol 4 is to avoid repeating module name for different globals of the same module.

>>> pickletools.dis(pickletools.optimize(pickle.dumps([sys.getsizeof, sys.intern], 4)))
    0: \x80 PROTO      4
    2: \x95 FRAME      33
   11: ]    EMPTY_LIST
   12: (    MARK
   13: \x8c     SHORT_BINUNICODE 'sys'
   18: \x94     MEMOIZE    (as 0)
   19: \x8c     SHORT_BINUNICODE 'getsizeof'
   30: \x93     STACK_GLOBAL
   31: h        BINGET     0
   33: \x8c     SHORT_BINUNICODE 'intern'
   41: \x93     STACK_GLOBAL
   42: e        APPENDS    (MARK at 12)
   43: .    STOP
highest protocol among opcodes = 4

But this doesn't work with the itertools module.

>>> pickletools.dis(pickletools.optimize(pickle.dumps([itertools.chain, itertools.accumulate], 4)))
    0: \x80 PROTO      4
    2: \x95 FRAME      47
   11: ]    EMPTY_LIST
   12: (    MARK
   13: \x8c     SHORT_BINUNICODE 'itertools'
   24: \x8c     SHORT_BINUNICODE 'chain'
   31: \x93     STACK_GLOBAL
   32: \x8c     SHORT_BINUNICODE 'itertools'
   43: \x8c     SHORT_BINUNICODE 'accumulate'
   55: \x93     STACK_GLOBAL
   56: e        APPENDS    (MARK at 12)
   57: .    STOP
highest protocol among opcodes = 4

That is because the __module__ attribute of itertools members is not interned.

>>> sys.getsizeof.__module__ is sys.intern.__module__
True
>>> itertools.chain.__module__ is itertools.chain.__module__
False

In addition to inefficient pickle this perhaps leads to small performance hit on accessing the __module__ attribute or using its value as dictionary key.

----------
components: Extension Modules
messages: 256322
nosy: alexandre.vassalotti, pitrou, rhettinger, serhiy.storchaka
priority: normal
severity: normal
status: open
title: The __module__ attribute of itertools members is not interned
type: performance
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25856>
_______________________________________

From report at bugs.python.org  Sun Dec 13 20:56:20 2015
From: report at bugs.python.org (Ioan Fintescu)
Date: Mon, 14 Dec 2015 01:56:20 +0000
Subject: [New-bugs-announce] [issue25857] csv: unexpected result
Message-ID: <1450058180.96.0.22857468917.issue25857@psf.upfronthosting.co.za>


New submission from Ioan Fintescu:

Python 3.4.3 (v3.4.3:9b73f1c3e601, Feb 24 2015, 22:44:40) [MSC v.1600 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import csv
>>> s = 'x = "a", y = "b, c"'
>>> s
'x = "a", y = "b, c"'
>>> for row in csv.reader([s]): print(row)
...
['x = "a"', ' y = "b', ' c"']
>>> len(row)
3
>>> for row1 in csv.reader([s], skipinitialspace=True):print(row1)
...
['x = "a"', 'y = "b', 'c"']
>>> len(row1)
3
>>> s2 = 'x = "a",y="b,c"'
>>> s2
'x = "a",y="b,c"'
>>> for row2 in csv.reader([s]): print(row2)
...
['x = "a"', ' y = "b', ' c"']
>>> len(row2)
3
>>> for row3 in csv.reader([s], skipinitialspace=True): print(row3)
...
['x = "a"', 'y = "b', 'c"']
>>> len(row3)
3

----------
messages: 256355
nosy: muss
priority: normal
severity: normal
status: open
title: csv: unexpected result
type: behavior
versions: Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25857>
_______________________________________

From report at bugs.python.org  Sun Dec 13 21:52:10 2015
From: report at bugs.python.org (Charles Machalow)
Date: Mon, 14 Dec 2015 02:52:10 +0000
Subject: [New-bugs-announce] [issue25858] Structure field size/ofs __str__
 wrong with large size fields
Message-ID: <1450061530.03.0.0248609360686.issue25858@psf.upfronthosting.co.za>


New submission from Charles Machalow:

Large sized fields in Structures lead to incorrect string representations because it is assuming that because the size is so large, it must be a bit field instead of a byte field.

class bugStruct(Structure):
    _pack_ = 1
    _fields_ = [
                ("correct", c_uint8 * 65535),
                ("wrongSizeAndOffset", c_uint8 * 999999),
               ]

print(str(bugStruct.correct))
<Field type=c_ubyte_Array_65535, ofs=0, size=65535> # Correct

print(str(bugStruct.wrongSizeAndOffset))
<Field type=c_ubyte_Array_999999, ofs=65535:16959, bits=15> # Incorrect
# Should be: <Field type=c_ubyte_Array_999999, ofs=65535, size=999999>

To get the math for this do the following on an incorrect size/offset:
  size = (bits << 16) + ofs.split(":")[1]
  ofs = ofs.split(":")[0]
    Though this isn't really safe because the field may actually be bit-sized

----------
components: ctypes
files: ctypesBug.py
messages: 256359
nosy: Charles Machalow
priority: normal
severity: normal
status: open
title: Structure field size/ofs __str__ wrong with large size fields
type: behavior
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41297/ctypesBug.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25858>
_______________________________________

From report at bugs.python.org  Mon Dec 14 04:00:26 2015
From: report at bugs.python.org (Martin Panter)
Date: Mon, 14 Dec 2015 09:00:26 +0000
Subject: [New-bugs-announce] [issue25859] EOFError in
 test_nntplib.NetworkedNNTPTests.test_starttls()
Message-ID: <1450083626.81.0.0429805941711.issue25859@psf.upfronthosting.co.za>


New submission from Martin Panter:

The AMD64 Debian root buildbot and the x86 Gentoo Installed with X buildbot have been persistently failing test_nntplib for a while, and I can also reproduce it locally when ?test -unetwork? is enabled. Six test cases fail. There is a pause before test_starttls() fails, then all the others fail immediately:

test_newgroups (test.test_nntplib.NetworkedNNTPTests) ... ok
test_over (test.test_nntplib.NetworkedNNTPTests) ... ok
test_starttls (test.test_nntplib.NetworkedNNTPTests) ... ERROR
test_unknown_command (test.test_nntplib.NetworkedNNTPTests) ... ERROR
test_welcome (test.test_nntplib.NetworkedNNTPTests) ... ok
test_with_statement (test.test_nntplib.NetworkedNNTPTests) ... ok
test_xhdr (test.test_nntplib.NetworkedNNTPTests) ... ERROR
test_xover (test.test_nntplib.NetworkedNNTPTests) ... ERROR
test_zlogin (test.test_nntplib.NetworkedNNTPTests) ... ERROR
test_zzquit (test.test_nntplib.NetworkedNNTPTests) ... ERROR
test_article_head_body (test.test_nntplib.NetworkedNNTP_SSLTests) ... ok
test_capabilities (test.test_nntplib.NetworkedNNTP_SSLTests) ... ok

Traceback from first failure:

======================================================================
ERROR: test_starttls (test.test_nntplib.NetworkedNNTPTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/media/disk/home/proj/python/cpython/Lib/test/test_nntplib.py", line 252, in wrapped
    meth(self)
  File "/media/disk/home/proj/python/cpython/Lib/test/test_nntplib.py", line 210, in test_starttls
    self.server.starttls()
  File "/media/disk/home/proj/python/cpython/Lib/nntplib.py", line 1014, in starttls
    self.getcapabilities()
  File "/media/disk/home/proj/python/cpython/Lib/nntplib.py", line 390, in getcapabilities
    resp, caps = self.capabilities()
  File "/media/disk/home/proj/python/cpython/Lib/nntplib.py", line 558, in capabilities
    resp, lines = self._longcmdstring("CAPABILITIES")
  File "/media/disk/home/proj/python/cpython/Lib/nntplib.py", line 525, in _longcmdstring
    resp, list = self._getlongresp(file)
  File "/media/disk/home/proj/python/cpython/Lib/nntplib.py", line 476, in _getlongresp
    resp = self._getresp()
  File "/media/disk/home/proj/python/cpython/Lib/nntplib.py", line 449, in _getresp
    resp = self._getline()
  File "/media/disk/home/proj/python/cpython/Lib/nntplib.py", line 437, in _getline
    if not line: raise EOFError
EOFError

It seems like as soon as the TLS connection is successfully set up, the server (news.trigofacile.com) shuts down the connection.

Would it be appropriate to change this test so that instead of connecting to a remote server, we connect to a local server running in a background thread? I attach a Python script that runs a minimal server with hardcoded responses allowing test_starttls() to pass. Perhaps we could use this for test_starttls(). Maybe even extend it to other remote server tests as well.

----------
components: Tests
files: starttls_server.py
keywords: buildbot
messages: 256374
nosy: martin.panter
priority: normal
severity: normal
status: open
title: EOFError in test_nntplib.NetworkedNNTPTests.test_starttls()
type: behavior
versions: Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41303/starttls_server.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25859>
_______________________________________

From report at bugs.python.org  Mon Dec 14 05:30:55 2015
From: report at bugs.python.org (Samson Lee)
Date: Mon, 14 Dec 2015 10:30:55 +0000
Subject: [New-bugs-announce] [issue25860] os.fwalk() silently skips
 remaining directories when error occurs
Message-ID: <1450089055.62.0.989850865471.issue25860@psf.upfronthosting.co.za>


New submission from Samson Lee:

I noticed os.fwalk() produced different results as os.walk(). It turned out
that os.fwalk() skips all remaining directories when OSError occurs (e.g. due
to PermissionError).

To reproduce the bug, first create a test directory structure:

    $ mkdir 1; touch 1/a
    $ mkdir 2; touch 2/b
    $ mkdir 3; touch 3/c
    $ mkdir 4; touch 4/c

At this stage, everything is okay, both os.fwalk() os.walk() produce the same
results:

    >>> import os
    >>> for root, dirs, files in os.walk('.'):
    ...     dirs.sort()
    ...     print(root, dirs, files)
    . ['1', '2', '3', '4'] []
    ./1 [] ['a']
    ./2 [] ['b']
    ./3 [] ['c']
    ./4 [] ['d']
    >>> for root, dirs, files, fd in os.fwalk('.'):
    ...     dirs.sort()
    ...     print(root, dirs, files)
    . ['1', '2', '3', '4'] []
    ./1 [] ['a']
    ./2 [] ['b']
    ./3 [] ['c']
    ./4 [] ['d']

To introduce an error, force a PermissionError on one of the directories:

    $ sudo chown root:root 2
    $ sudo chmod 700 2

Now, the os.fwalk() results are different (trust me, os.walk() is still okay):

    >>> for root, dirs, files, fd in os.fwalk('.'):
    ...     dirs.sort()
    ...     print(root, dirs, files)
    . ['1', '2', '3', '4'] []
    ./1 [] ['a']

So it seems that os.fwalk skips remaining directories after an error occurs.

The cause of the problem is in this part of os.py:

    for name in dirs:
        try:
            orig_st = stat(name, dir_fd=topfd, follow_symlinks=follow_symlinks)
            dirfd = open(name, O_RDONLY, dir_fd=topfd)
        except OSError as err:
            if onerror is not None:
                onerror(err)
            break

To fix it, simply replace break with continue. Patch attached.

Cheers

----------
components: Library (Lib)
files: fwalk-silently-skips-dirs-when-error-occurs.patch
keywords: patch
messages: 256377
nosy: Samson Lee
priority: normal
severity: normal
status: open
title: os.fwalk() silently skips remaining directories when error occurs
type: behavior
versions: Python 3.4, Python 3.5
Added file: http://bugs.python.org/file41304/fwalk-silently-skips-dirs-when-error-occurs.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25860>
_______________________________________

From report at bugs.python.org  Mon Dec 14 09:35:30 2015
From: report at bugs.python.org (=?utf-8?q?Geoffrey_M=C3=A9gardon?=)
Date: Mon, 14 Dec 2015 14:35:30 +0000
Subject: [New-bugs-announce] [issue25861] Can't use Pickle. AttributeError:
 'module' object has no attribute '_new_Index'
Message-ID: <1450103730.5.0.342530922522.issue25861@psf.upfronthosting.co.za>


New submission from Geoffrey M?gardon:

Hello,

I am trying to run a piece of code that I programmed some time ago.
Back then, it was working fine and it was plotting some data.
But today, while I am trying to improve the plots, I ran the code and did not work!

Here the message:

D:\Users\Geoffrey\Anaconda\python.exe "D:/Google Drive/Work/Experiences/experiment-deviation-initial/analysis/FigureTrajAndDeviation.py"
Traceback (most recent call last):
  File "D:/Google Drive/Work/Experiences/experiment-deviation-initial/analysis/FigureTrajAndDeviation.py", line 36, in <module>
    m = pickle.load( open(output_path+"/traj_and_RT_second_only.p", "rb" ) )
  File "D:\Users\Geoffrey\Anaconda\lib\pickle.py", line 1378, in load
    return Unpickler(file).load()
  File "D:\Users\Geoffrey\Anaconda\lib\pickle.py", line 858, in load
    dispatch[key](self)
  File "D:\Users\Geoffrey\Anaconda\lib\pickle.py", line 1090, in load_global
    klass = self.find_class(module, name)
  File "D:\Users\Geoffrey\Anaconda\lib\pickle.py", line 1126, in find_class
    klass = getattr(mod, name)
AttributeError: 'module' object has no attribute '_new_Index'

Process finished with exit code 1

I hope that you may now what it is about!!
I attached the code file.

----------
components: Library (Lib)
files: FigureTrajAndDeviation.py
messages: 256379
nosy: Geoffrey M?gardon
priority: normal
severity: normal
status: open
title: Can't use Pickle. AttributeError: 'module' object has no attribute '_new_Index'
type: crash
versions: Python 2.7
Added file: http://bugs.python.org/file41305/FigureTrajAndDeviation.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25861>
_______________________________________

From report at bugs.python.org  Mon Dec 14 20:43:10 2015
From: report at bugs.python.org (Martin Panter)
Date: Tue, 15 Dec 2015 01:43:10 +0000
Subject: [New-bugs-announce] [issue25862] TextIOWrapper assertion failure
 after read() and SEEK_CUR
Message-ID: <1450143790.74.0.198268951027.issue25862@psf.upfronthosting.co.za>


New submission from Martin Panter:

Python 3.5.1+ (3.5:014e6f7d7c1a, Dec 14 2015, 11:20:58) 
[GCC 5.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from io import *
>>> text = TextIOWrapper(BytesIO(b"x"), "ascii")
>>> text.read(1)
'x'
>>> text.read()
''
>>> text.seek(0, SEEK_CUR)
python: ./Modules/_io/textio.c:2293: _io_TextIOWrapper_tell_impl: Assertion `self->decoded_chars == ((void *)0) || PyUnicode_GetLength(self->decoded_chars) == 0' failed.
Aborted (core dumped)
[Exit 134]

May affect other versions; I haven?t looked.

----------
components: IO
messages: 256430
nosy: martin.panter
priority: normal
severity: normal
status: open
title: TextIOWrapper assertion failure after read() and SEEK_CUR
type: crash
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25862>
_______________________________________

From report at bugs.python.org  Mon Dec 14 21:37:24 2015
From: report at bugs.python.org (Martin Panter)
Date: Tue, 15 Dec 2015 02:37:24 +0000
Subject: [New-bugs-announce] [issue25863] ISO-2022 seeking forgets state
Message-ID: <1450147044.33.0.0242462239972.issue25863@psf.upfronthosting.co.za>


New submission from Martin Panter:

>>> from io import *
>>> text = TextIOWrapper(BytesIO(), "iso-2022-jp")
>>> text.write(u"P")
1
>>> text.tell()
1
>>> text.write(u"anter ?")
7
>>> text.tell()
12
>>> text.write(u"?")
1
>>> text.seek(12)
12
>>> text.read()  # Should return ?, not ASCII
"9'"
>>> text.buffer.getvalue()
b"Panter \x1b$B at 59'"
>>> text.seek(1)
1
>>> text.read(7)
'anter ?'
>>> text.tell()  # Another bug?
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
UnicodeDecodeError: 'iso2022_jp' codec can't decode bytes in position 2-3: illegal multibyte sequence

----------
components: IO, Unicode
messages: 256431
nosy: ezio.melotti, haypo, martin.panter
priority: normal
severity: normal
status: open
title: ISO-2022 seeking forgets state
type: behavior
versions: Python 2.7, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25863>
_______________________________________

From report at bugs.python.org  Mon Dec 14 22:38:38 2015
From: report at bugs.python.org (Andrew Barnert)
Date: Tue, 15 Dec 2015 03:38:38 +0000
Subject: [New-bugs-announce] [issue25864] collections.abc.Mapping should
 include a __reversed__ that raises TypeError
Message-ID: <1450150718.99.0.697293755498.issue25864@psf.upfronthosting.co.za>


New submission from Andrew Barnert:

Example:

    class MyDict(collections.abc.Mapping):
        def __init__(self, d): self.d = d
        def __len__(self): return len(self.d)
        def __getitem__(self, key): return self.d[key]
        def __iter__(self): return iter(self.d)

    d = {1:2, 3:4}
    m = MyDict({1: 2, 3: 4})

If you do `reversed(d)`, you get a nice `TypeError: argument to reversed() must be a sequence`. But if you do `reversed(m)`, you get a `reversed` iterator. And when you iterate it, presumably expecting to get 0 and 1 in some arbitrary order, you instead get 3, and then a `KeyError: 0`.

Of course it's obvious why this happens once you think about it: in order to handle types that implement the old-style sequence protocol (just respond to `__getitem__` for all integers from 0 to `len(self)`), `reversed` has to fall back to trying `__getitem__` for all integers from `len(d)-1` to 0.

If you provide a `__reversed__` method, it just calls that. Or, if you're a C-API mapping like `dict`, `PySequence_Check` will return false and it'll raise a `TypeError`. But for a Python mapping, there's no way `PySequence_Check` or anything else can know that you're not actually a sequence (after all, you implement `__getitem__` and `__len__`), so it tries to use you as one, and confusion results.

I think trying to fix this for _all_ possible mappings is a non-starter.

But fixing it for mappings that use `collections.abc.Mapping` is easy: just provide a default implementation of `collections.abc.Mapping.__reversed__` that just raises a `TypeError`.

I can't imagine this would break any working code. If it did, the workaround would be simple: just implement `def __reversed__(self): return (self[k] for k in reversed(range(len(self))))`.

----------
components: Library (Lib)
messages: 256434
nosy: abarnert
priority: normal
severity: normal
status: open
title: collections.abc.Mapping should include a __reversed__ that raises TypeError
type: behavior

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25864>
_______________________________________

From report at bugs.python.org  Tue Dec 15 02:47:24 2015
From: report at bugs.python.org (Andrew Barnert)
Date: Tue, 15 Dec 2015 07:47:24 +0000
Subject: [New-bugs-announce] [issue25865] 7.2 Assignment statements
 documentation is vague and slightly misleading
Message-ID: <1450165644.56.0.226489817502.issue25865@psf.upfronthosting.co.za>


New submission from Andrew Barnert:

>From https://docs.python.org/3/reference/simple_stmts.html#assignment-statements

> If the target list contains one target prefixed with an asterisk, called a ?starred? target: The object must be a sequence with at least as many items as there are targets in the target list, minus one. The first items of the sequence are assigned, from left to right, to the targets before the starred target. The final items of the sequence are assigned to the targets after the starred target. A list of the remaining items in the sequence is then assigned to the starred target (the list can be empty).
> Else: The object must be a sequence with the same number of items as there are targets in the target list, and the items are assigned, from left to right, to the corresponding targets.

The word "sequence" is used here multiple times. But the object being assigned to the target list can be any iterable (including an iterator, a set, some weird custom iterable you invent, ...).

> If the target is a target list enclosed in parentheses or in square brackets: The object must be an iterable with the same number of items as there are targets in the target list, and its items are assigned, from left to right, to the corresponding targets.

This doesn't mention that you can have a starred target inside the parenthesized or bracketed target list. More importantly, it covers the exact same case already covered above. There's semantics for "assignment of an object to a target list, optionally enclosed in parentheses or square brackets", and then semantics for "Assignment of an object to a single target... If the target is a target list enclosed in parentheses or in square brackets".

According to the grammar, a single target (no commas, parens, or brackets) is a target list, but according to the previous paragraphs it seems like it isn't.

Finally, there's nothing that explains what distinguishes between target list assignment and single?target assignment. As far as I can tell, it's treated as a target list iff there's a comma, or there's square brackets around it (similar to the fact that tuples are defined by commas, but lists by square brackets--but without the exception for `()`); that should probably be documented.

There's also some needless repetition there.

I think better wording might be something like this:

> Assignment is recursively defined as follows.

> * If the target list is a comma-separated list of two or more targets, optionally enclosed in parentheses, or a comma-separated list of zero or more targets enclosed in square brackets:

(It might be worth having a note here pointing out that these are almost the same rules for non-comprehension tuple and list displays, except that () is a tuple but not a target list. Or would that just be confusing?)

(It might also be worth mentioning that this is the same feature referred to as "iterable unpacking", "sequence unpacking", and/or "tuple unpacking" in PEP 3132, the official tutorial, and lots of non-official materials?)

> ** If the target list contains one target prefixed with an asterisk, called a ?starred? target: The object must be an iterable with at least as many items as there are targets in the target list, minus one. The first items of the iterable are assigned, from left to right, to the targets before the starred target. The final items of the iterable are assigned to the targets after the starred target. A list of the remaining items in the iterable is then assigned to the starred target (the list can be empty).

> ** Else: The object must be an iterable with the same number of items as there are targets in the target list, and the items are assigned, from left to right, to the corresponding targets.

> * Otherwise, the target list is treated as a single target. 

> ** If the target is an identifier (name): ...

(No section on bracketed target list here; that's already covered above.)

> ** If the target is an attribute reference: ...

> ** ...

----------
assignee: docs at python
components: Documentation
messages: 256443
nosy: abarnert, docs at python
priority: normal
severity: normal
status: open
title: 7.2 Assignment statements documentation is vague and slightly misleading

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25865>
_______________________________________

From report at bugs.python.org  Tue Dec 15 03:12:47 2015
From: report at bugs.python.org (Andrew Barnert)
Date: Tue, 15 Dec 2015 08:12:47 +0000
Subject: [New-bugs-announce] [issue25866] Reference 3. Data Model:
 miscellaneous minor cleanups on the word "sequence".
Message-ID: <1450167167.45.0.614001159878.issue25866@psf.upfronthosting.co.za>


New submission from Andrew Barnert:

None of the below are very serious or likely to mislead anyone using or implementing Python, but...

---

3.3.2. Customizing attribute access

The docs for `__dir__` say:

> A sequence must be returned. dir() converts the returned sequence to a list and sorts it.

At least in CPython and PyPy, this isn't enforced; any iterable can be returned (and it's then converted to a list and sorted). You can even make `__dir__` a generator function. (I've never seen that in the wild--but I have seen code that returns a `map` iterator.)

I think it would be better to say "An iterable must be returned. dir() converts the returned iterable to a list and sorts it."

---

3.3.2.3. __slots__

> This class variable can be assigned a string, iterable, or sequence of strings...

While it's true that you can assign any iterable, it's at best misleading to assign an iterator. For example, if you use `__slots__ = iter('abc')`, you will get a class with descriptors named `a`, `b`, and `c`, but with an empty iterator in `__slots__`. There's probably no reason to actually outlaw that, but it might be worth noting in 3.3.2.3.1 along with the other weird possibilities like assigning a mapping.

---

3.3.6. Emulating container types

The docs still say that the ABCs are in `collections` rather than `collections.abc`.

> ... for mappings, __iter__() should be the same as keys()

No; `__iter__()` should be an iterator over the keys; `keys()` _can_ be an iterator, but generally should be a view instead.

> The membership test operators (in and not in) are normally implemented as an iteration through a sequence. However, container objects can supply the following special method with a more efficient implementation, which also does not require the object be a sequence.

I don't think this should say "through a sequence". They're implemented as iteration through whatever the container is, whether it's a sequence, a set, a linked list, or anything else. The documentation on `__contains__` immediately below clarifies this, but it's probably better to be clear from the start.

----------
assignee: docs at python
components: Documentation
messages: 256445
nosy: abarnert, docs at python
priority: normal
severity: normal
status: open
title: Reference 3. Data Model: miscellaneous minor cleanups on the word "sequence".
type: enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25866>
_______________________________________

From report at bugs.python.org  Tue Dec 15 03:33:11 2015
From: report at bugs.python.org (Ondrej Sejvl)
Date: Tue, 15 Dec 2015 08:33:11 +0000
Subject: [New-bugs-announce] [issue25867] os.stat raises exception when
 using unicode and no locale is set
Message-ID: <1450168391.42.0.368048088305.issue25867@psf.upfronthosting.co.za>


New submission from Ondrej Sejvl:

os.stat() raises exception UnicodeEncodeError when path is unicode and no locale is set in envinronment (this occures when running app with daemon tools -> LC_ALL=)

How to simulate:
$ env -i python
>>> import os
>>> os.stat(u"\xf0")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
UnicodeEncodeError: 'ascii' codec can't encode character u'\xf0' in position 0: ordinal not in range(128)

Is this a valid behaviour? Then maybe some notification in documentation would be nice (I am using os.path.isfile and now UnicodeEncodeError raised...)

Thanks
Ondra

----------
messages: 256446
nosy: sejvlond
priority: normal
severity: normal
status: open
title: os.stat raises exception when using unicode and no locale is set

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25867>
_______________________________________

From report at bugs.python.org  Tue Dec 15 05:20:56 2015
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Dec 2015 10:20:56 +0000
Subject: [New-bugs-announce] [issue25868] test_eintr.test_sigwaitinfo()
 hangs on "AMD64 FreeBSD CURRENT 3.x" buildbot
Message-ID: <1450174856.95.0.354294896083.issue25868@psf.upfronthosting.co.za>


New submission from STINNER Victor:

Re-running test 'test_eintr' in verbose mode
test_all (test.test_eintr.EINTRTests) ... test test_eintr failed
FAIL

======================================================================
FAIL: test_all (test.test_eintr.EINTRTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/test_eintr.py", line 20, in test_all
    script_helper.assert_python_ok("-u", tester)
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/support/script_helper.py", line 135, in assert_python_ok
    return _assert_python(True, *args, **env_vars)
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/support/script_helper.py", line 121, in _assert_python
    err))
AssertionError: Process return code is 1
command line: ['/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/python', '-X', 'faulthandler', '-I', '-u', '/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/eintrdata/eintr_tester.py']

stdout:
---
test_read (__main__.OSEINTRTest) ... ok
test_wait (__main__.OSEINTRTest) ... ok
test_wait3 (__main__.OSEINTRTest) ... ok
test_wait4 (__main__.OSEINTRTest) ... ok
test_waitpid (__main__.OSEINTRTest) ... ok
test_write (__main__.OSEINTRTest) ... ok
test_accept (__main__.SocketEINTRTest) ... ok
test_open (__main__.SocketEINTRTest) ... ok
test_os_open (__main__.SocketEINTRTest) ... ok
test_recv (__main__.SocketEINTRTest) ... ok
test_recvmsg (__main__.SocketEINTRTest) ... ok
test_send (__main__.SocketEINTRTest) ... ok
test_sendall (__main__.SocketEINTRTest) ... ok
test_sendmsg (__main__.SocketEINTRTest) ... ok
test_sleep (__main__.TimeEINTRTest) ... ok
test_sigtimedwait (__main__.SignalEINTRTest) ... ok
test_sigwaitinfo (__main__.SignalEINTRTest) ...
---

stderr:
---
Timeout (0:10:00)!
Thread 0x0000000801815000 (most recent call first):
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/eintrdata/eintr_tester.py", line 404 in test_sigwaitinfo
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/case.py", line 600 in run
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/case.py", line 648 in __call__
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/suite.py", line 122 in run
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/suite.py", line 84 in __call__
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/suite.py", line 122 in run
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/suite.py", line 84 in __call__
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/runner.py", line 176 in run
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/support/__init__.py", line 1780 in _run_suite
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/support/__init__.py", line 1814 in run_unittest
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/eintrdata/eintr_tester.py", line 472 in test_main
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/eintrdata/eintr_tester.py", line 476 in <module>
---

----------------------------------------------------------------------
Ran 1 test in 607.737s

FAILED (failures=1)
1 test failed again:
    test_eintr
*** Error code 1

----------
messages: 256449
nosy: bapt, haypo, koobs
priority: normal
severity: normal
status: open
title: test_eintr.test_sigwaitinfo() hangs on "AMD64 FreeBSD CURRENT 3.x" buildbot
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25868>
_______________________________________

From report at bugs.python.org  Tue Dec 15 05:48:07 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 15 Dec 2015 10:48:07 +0000
Subject: [New-bugs-announce] [issue25869] Faster ElementTree deepcopying
Message-ID: <1450176487.07.0.677302980007.issue25869@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

According to lxml benchmark [1], deepcopying a tree in ElementTree is about 20 times slower than in lxml. Proposed patch optimizes deepcopying C implementation of ElementTree about 20 times. It is now 5% to 3 times faster than in lxml.

[1] http://lxml.de/performance.html

----------
components: Extension Modules
files: etree_deepcopy.patch
keywords: patch
messages: 256455
nosy: brett.cannon, scoder, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Faster ElementTree deepcopying
type: performance
versions: Python 3.6
Added file: http://bugs.python.org/file41314/etree_deepcopy.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25869>
_______________________________________

From report at bugs.python.org  Tue Dec 15 10:54:57 2015
From: report at bugs.python.org (Bernhard M. Wiedemann)
Date: Tue, 15 Dec 2015 15:54:57 +0000
Subject: [New-bugs-announce] [issue25870] textwrap is very slow on long
 words without spaces
Message-ID: <1450194897.19.0.781302598821.issue25870@psf.upfronthosting.co.za>


New submission from Bernhard M. Wiedemann:

Many python scripts use textwrap to break base64-encoded strings from openssl into lines - e.g. https://bugs.launchpad.net/python-keystoneclient/+bug/1404402
and https://github.com/diafygi/acme-tiny/blob/master/acme_tiny.py#L166

Steps To Reproduce:
time python -c "import textwrap; textwrap.wrap('x'*9000, 64)"

This has a complexity of O(n^2), meaning wrapping 18000 chars takes 4 times as long as 9000.

one known workaround is to use
textwrap.wrap('x'*9000, 64, break_on_hyphens=False)

this also has O(n^2) complexity, but is around 2000 times faster.

----------
components: Benchmarks, Extension Modules, Library (Lib), Regular Expressions
messages: 256461
nosy: bmwiedemann, brett.cannon, ezio.melotti, mrabarnett, pitrou
priority: normal
severity: normal
status: open
title: textwrap is very slow on long words without spaces
type: performance
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25870>
_______________________________________

From report at bugs.python.org  Tue Dec 15 11:16:01 2015
From: report at bugs.python.org (Chris Tozer)
Date: Tue, 15 Dec 2015 16:16:01 +0000
Subject: [New-bugs-announce] [issue25871] textwrap.dedent doesn't find
 common substring when spaces and tabs are mixed
Message-ID: <1450196161.19.0.609801434085.issue25871@psf.upfronthosting.co.za>


New submission from Chris Tozer:

Two lines, one has three spaces, one has two spaces then a tab - dedent doesn't take the two spaces away...

Python 2.7.5 (default, Nov 20 2015, 02:00:19) 
[GCC 4.8.5 20150623 (Red Hat 4.8.5-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from textwrap import dedent
>>> dedent("   some\n  \tthing")
'   some\n  \tthing'
>>> dedent("   some\n   \tthing")
'some\n\tthing'

Looks very similar to issue 21827, but having upgraded to a newer build of 2.7 (Nov 2015, as above), I still see the same behaviour.  I assume the November build would have a fix made in October, but I don't know how the process actually works...

----------
components: Library (Lib)
messages: 256463
nosy: Chris Tozer
priority: normal
severity: normal
status: open
title: textwrap.dedent doesn't find common substring when spaces and tabs are mixed
type: behavior
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25871>
_______________________________________

From report at bugs.python.org  Tue Dec 15 12:21:04 2015
From: report at bugs.python.org (Michael Allen)
Date: Tue, 15 Dec 2015 17:21:04 +0000
Subject: [New-bugs-announce] [issue25872] multithreading traceback KeyError
 when modifying file
Message-ID: <1450200064.35.0.872448112145.issue25872@psf.upfronthosting.co.za>


New submission from Michael Allen:

Modifying a file while getting a stacktrace across multiple threads causes linecache's cache to bust and del to be called on the global cache variable. This is not thread safe and raises a KeyError.

Reproducible with,

import threading
import traceback

def main():
    with open(__file__, 'a') as fp:
        fp.write(' ')
        traceback.format_stack()

threads = [
    threading.Thread(target=main)
    for i in range(100)
]
map(lambda t: t.start(), threads)
map(lambda t: t.join(), threads)

I see the following error,

Exception in thread Thread-56:
Traceback (most recent call last):
  File "/Users/me/.pyenv/versions/2.7.10/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/Users/me/.pyenv/versions/2.7.10/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "test.py", line 7, in main
    traceback.format_stack()
  File "/Users/me/.pyenv/versions/2.7.10/lib/python2.7/traceback.py", line 279, in format_stack
    return format_list(extract_stack(f, limit))
  File "/Users/me/.pyenv/versions/2.7.10/lib/python2.7/traceback.py", line 305, in extract_stack
    linecache.checkcache(filename)
  File "/Users/me/.pyenv/versions/2.7.10/lib/python2.7/linecache.py", line 69, in checkcache
    del cache[filename]
KeyError: 'test.py'

Possible solution is to ignore KeyError on del cache[filename].

----------
components: Library (Lib)
messages: 256469
nosy: Michael Allen
priority: normal
severity: normal
status: open
title: multithreading traceback KeyError when modifying file
type: crash
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25872>
_______________________________________

From report at bugs.python.org  Tue Dec 15 14:17:03 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 15 Dec 2015 19:17:03 +0000
Subject: [New-bugs-announce] [issue25873] Faster ElementTree iterating
Message-ID: <1450207023.67.0.072498678693.issue25873@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Proposed patch refactors and optimize the code for iterating ElementTree. Refactoring and minor optimization makes the code about 30 lines smaller and 2-3% faster. Using a continuous array instead of linked list makes the code up to 40% faster (lxml benchmark was used to measurement).

In addition the patch fixes possible issue with owning references.

----------
components: Extension Modules
files: etree_iter.patch
keywords: patch
messages: 256472
nosy: brett.cannon, scoder, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Faster ElementTree iterating
type: performance
versions: Python 3.6
Added file: http://bugs.python.org/file41318/etree_iter.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25873>
_______________________________________

From report at bugs.python.org  Tue Dec 15 14:24:35 2015
From: report at bugs.python.org (Chris Wilcox)
Date: Tue, 15 Dec 2015 19:24:35 +0000
Subject: [New-bugs-announce] [issue25874] Add notice that XP is not
 supported on Python 3.5+
Message-ID: <1450207475.07.0.153862605779.issue25874@psf.upfronthosting.co.za>


New submission from Chris Wilcox:

This is a documentation change to make it easier to discover that XP is not a supported OS.  Content was taken from the 'whats new' section and added to the top of the main article.

----------
assignee: docs at python
components: Documentation
files: add-supported-versions-section-windows.diff
keywords: patch
messages: 256473
nosy: crwilcox, docs at python
priority: normal
severity: normal
status: open
title: Add notice that XP is not supported on Python 3.5+
type: enhancement
versions: Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41319/add-supported-versions-section-windows.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25874>
_______________________________________

From report at bugs.python.org  Tue Dec 15 15:30:12 2015
From: report at bugs.python.org (William Abdo)
Date: Tue, 15 Dec 2015 20:30:12 +0000
Subject: [New-bugs-announce] [issue25875] PYODBC talk to Oracle under
 Windows 10.
Message-ID: <1450211412.48.0.393165880363.issue25875@psf.upfronthosting.co.za>


New submission from William Abdo:

PYODBC  talk to Oracle under Windows 10.
I tried everything I could  however,  I was unable to make PYODBC talk to Oracle 11g under Windows 10.

I have recently upgraded to Windows 10 and I have an issue with PYODBC connecting to Oracle 11g.

It was working OK in Windows 7,  till I upgraded to Windows 10. 
I have tried setting it to Windows 7 compatibility mode .
I have updated the drivers to the latest (Which I think I already had).

Nothing works.

The actual error I get is 
 Traceback (most recent call last):
  File "oraclecountsDec1.py", line 32, in <module>
    pconnObj =  pyodbc.connect( pconnString )
pyodbc.Error: ('NA000', "[NA000] [Microsoft][ODBC driver for Oracle][Oracle]Error while trying to retrieve text for error ORA-01019 (1019) (SQLDriverConnect); [01000] [Microsoft][ODBC Driver Manager] The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr). (0)")

SQL Log file states:
Fatal NI connect error 12560, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleORCX)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(SID=ORCX)(CID=(PROGRAM=D:\Python26\python.exe)(HOST=xxxxxxx-xxxxxxxx)(USER=xxxxxxxxxxxxxx))))

  VERSION INFORMATION:
                TNS for 32-bit Windows: Version 12.1.0.2.0 - Production
                Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 12.1.0.2.0 - Production
                Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version 12.1.0.2.0 - Production
  Time: 06-AUG-2015 17:12:31
  Tracing not turned on.
  Tns error struct:
    ns main err code: 12560
    TNS-12560: Message 12560 not found; No message file for product=NETWORK, facility=TNS
    ns secondary err code: 0
    nt main err code: 530
    TNS-00530: Message 530 not found; No message file for product=NETWORK, facility=TNS
    nt secondary err code: 126
    nt OS err code: 0

----------
components: Windows
messages: 256482
nosy: paul.moore, steve.dower, tim.golden, wabdo, zach.ware
priority: normal
severity: normal
status: open
title: PYODBC  talk to Oracle under Windows 10.
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25875>
_______________________________________

From report at bugs.python.org  Tue Dec 15 15:40:38 2015
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Dec 2015 20:40:38 +0000
Subject: [New-bugs-announce] [issue25876] test_gdb: use
 subprocess._args_from_interpreter_flags() to test Python with more options
Message-ID: <1450212038.89.0.962872352971.issue25876@psf.upfronthosting.co.za>


New submission from STINNER Victor:

Attached patch pass Python options to the Python program run in gdb, so it allows to test more cases.

What do you think?

I don't think that it's worth to apply the patch to Python < 3.6.

----------
components: Tests
files: test_gdb.patch
keywords: patch
messages: 256484
nosy: haypo
priority: normal
severity: normal
status: open
title: test_gdb: use subprocess._args_from_interpreter_flags() to test Python with more options
versions: Python 3.6
Added file: http://bugs.python.org/file41320/test_gdb.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25876>
_______________________________________

From report at bugs.python.org  Tue Dec 15 18:39:19 2015
From: report at bugs.python.org (Thomas Latimer)
Date: Tue, 15 Dec 2015 23:39:19 +0000
Subject: [New-bugs-announce] [issue25877] python av docs has broken links
Message-ID: <1450222759.52.0.72518805209.issue25877@psf.upfronthosting.co.za>


New submission from Thomas Latimer:

https://www.python.org/doc/av/

I was looking for an audio lecture on python to listen to on my drive. I found this page, which looked promising, except...

both 'python411' and 'a little bit of python' are broken links.

----------
assignee: docs at python
components: Documentation
messages: 256489
nosy: Thomas Latimer, docs at python
priority: normal
severity: normal
status: open
title: python av docs has broken links
type: behavior

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25877>
_______________________________________

From report at bugs.python.org  Tue Dec 15 19:12:35 2015
From: report at bugs.python.org (Alexander Riccio)
Date: Wed, 16 Dec 2015 00:12:35 +0000
Subject: [New-bugs-announce] [issue25878] CPython on Windows builds with /W3, not /W4
Message-ID: <1450224755.83.0.682115702996.issue25878@psf.upfronthosting.co.za>


New submission from Alexander Riccio:

This issue is related to Issue25847.

Compiling at /W4 is generally a good idea. It's an industry best practice, and even though I don't expect disagreement, I'll throw in a few coding standard links:

https://www.securecoding.cert.org/confluence/display/c/MSC00-C.+Compile+cleanly+at+high+warning+levels

https://books.google.com/books?id=pDsFCAAAQBAJ&pg=PA557&lpg=PA557&dq=compile+at+highest+warning+level&source=bl&ots=RlKoHFuuWW&sig=mcz-wqdpf3MhiyGZSYKFvpTmd9A&hl=en&sa=X&ved=0ahUKEwjkhN2Rh9_JAhXIth4KHTTbCiMQ6AEIgwEwEQ#v=onepage&q=compile%20at%20highest%20warning%20level&f=false

http://programmers.stackexchange.com/questions/232626/is-it-a-good-practice-to-choose-the-highest-warning-level-in-c-programming

http://ptgmedia.pearsoncmg.com/images/0321113586/items/sutter_item1.pdf


...so I was surprised to discover that the Windows build of CPython compiles at /W3!

Bumping it up to /W4 produces ~9,000 warnings (up from ~20).


The patch that I'll include with this issue (first iteration) bumps the warning level up to /W4, and I've disabled warnings that (appear) aren't useful. That suppresses ~8,000 of those warnings.

The patch isn't quite yet perfect, as Visual Studio made changes that I didn't ask for, such as:

-    <ClCompile Include="..\PC\bdist_wininst\extract.c">
+    <ClCompile Include="extract.c">

...but that's about it. I had to use `hg diff -w`, because Visual Studio also decided to change the spacing in all of the .vcxproj files.

----------
messages: 256494
nosy: Alexander Riccio
priority: normal
severity: normal
status: open
title: CPython on Windows builds with /W3, not /W4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25878>
_______________________________________

From report at bugs.python.org  Tue Dec 15 23:07:47 2015
From: report at bugs.python.org (Kirk McDonald)
Date: Wed, 16 Dec 2015 04:07:47 +0000
Subject: [New-bugs-announce] [issue25879] Code objects from same line can
 compare equal
Message-ID: <1450238867.99.0.650627137884.issue25879@psf.upfronthosting.co.za>


New submission from Kirk McDonald:

The following code gives an unexpected result:

>>> a, b = lambda: 1, lambda: 1.0
>>> a()
1
>>> b()
1
>>> type(b())
<class 'int'>
>>> a.__code__ is b.__code__
True

The cause boils down to this line of code:

https://hg.python.org/cpython/file/33ff335da34c/Objects/codeobject.c#l442

When it compiles the two lambdas, their code objects compare equal. They have the same name, the same bytecode, and start on the same line. And, because 1 == 1.0, their constants compare equal. This then prompts the compiler to combine the two code objects into a single constant in the enclosing code object, discarding the second one.

I think the solution is to have code_richcompare also check whether the types of the constants are equal, in addition to the constants themselves.

----------
messages: 256508
nosy: KirkMcDonald
priority: normal
severity: normal
status: open
title: Code objects from same line can compare equal

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25879>
_______________________________________

From report at bugs.python.org  Wed Dec 16 03:03:52 2015
From: report at bugs.python.org (SpaceOne)
Date: Wed, 16 Dec 2015 08:03:52 +0000
Subject: [New-bugs-announce] =?utf-8?b?W2lzc3VlMjU4ODBdIHUnLi4nLmVuY29k?=
 =?utf-8?q?e=28=27idna=27=29_=E2=86=92_UnicodeError=3A_label_empty_or_too_?=
 =?utf-8?q?long?=
Message-ID: <1450253032.62.0.362649983897.issue25880@psf.upfronthosting.co.za>


New submission from SpaceOne:

Python 3.4.2 (default, Oct  8 2014, 10:45:20)
>>> u'..'.encode('idna')
Traceback (most recent call last):
  File "/usr/lib/python3.4/encodings/idna.py", line 165, in encode
    raise UnicodeError("label empty or too long")
UnicodeError: label empty or too long

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
UnicodeError: encoding with 'idna' codec failed (UnicodeError: label empty or too long)

? I was expecting that this raises either not at all or UnicodeEncodeError.

>>> b'..'.decode('idna')
'..'
? Why doesn't this raise then, too?

The error message is also messed up which wasn't the case in python 2.7. It could be cleaned up.

----------
components: Unicode
messages: 256514
nosy: ezio.melotti, haypo, spaceone
priority: normal
severity: normal
status: open
title: u'..'.encode('idna') ? UnicodeError: label empty or too long
versions: Python 2.7, Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25880>
_______________________________________

From report at bugs.python.org  Wed Dec 16 07:51:47 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 16 Dec 2015 12:51:47 +0000
Subject: [New-bugs-announce] [issue25881] A little faster ElementTree
 serializing
Message-ID: <1450270307.19.0.659331230306.issue25881@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Proposed patch makes ElementTree serializing to xml and html formats a little faster. For example the write_utf8_parse_bytesIO test from lxml benchmark suite now is up to 5% faster, tostring_utf8 now is up to 9% faster.

Even with this patch, serializing ElementTree still is a weak link in comparison with lxml, it is 3-5 times slower.

----------
components: Library (Lib), XML
files: etree_write.patch
keywords: patch
messages: 256517
nosy: scoder, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: A little faster ElementTree serializing
type: performance
versions: Python 3.6
Added file: http://bugs.python.org/file41328/etree_write.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25881>
_______________________________________

From report at bugs.python.org  Wed Dec 16 08:14:43 2015
From: report at bugs.python.org (=?utf-8?q?Bal=C3=A1zs_Reg=C3=A9nyi?=)
Date: Wed, 16 Dec 2015 13:14:43 +0000
Subject: [New-bugs-announce] [issue25882] argparse help error: arguments
 created by add_mutually_exclusive_group() are shown outside their parent
 group created by add_argument_group()
Message-ID: <1450271683.16.0.602190712987.issue25882@psf.upfronthosting.co.za>


New submission from Bal?zs Reg?nyi:

So, a parent parser is created. It has a "global arguments" group (by add_argument_group()) and this group has a mutually exclusive group. Then a child parser is created used previous parser as parent. 
The error: in the child parser help: the arguments of the mutually exclusive group are printed into the part of child parser instead of their "global arguments" group.

The next code shows the problem:

import argparse
# create parent parser
parent_parser = argparse.ArgumentParser(add_help = False)
# create group for its arguments
global_group = parent_parser.add_argument_group("global arguments")
global_group.add_argument("--global-arg1")
global_group.add_argument("--global-arg2")
mutex_group = global_group.add_mutually_exclusive_group()
mutex_group.add_argument("--mutex-arg1")
mutex_group.add_argument("--mutex-arg2")
# create child parser
child_parser = argparse.ArgumentParser(parents = [parent_parser])
child_parser.add_argument("--child-arg1")
child_parser.add_argument("--child-arg2")
print("="*100)
parent_parser.print_help()
print("="*100)
child_parser.print_help()


The output:

====================================================================================================
usage: test.py [--global-arg1 GLOBAL_ARG1] [--global-arg2 GLOBAL_ARG2]
               [--mutex-arg1 MUTEX_ARG1 | --mutex-arg2 MUTEX_ARG2]

global arguments:
  --global-arg1 GLOBAL_ARG1
  --global-arg2 GLOBAL_ARG2
  --mutex-arg1 MUTEX_ARG1
  --mutex-arg2 MUTEX_ARG2
====================================================================================================
usage: test.py [-h] [--global-arg1 GLOBAL_ARG1] [--global-arg2 GLOBAL_ARG2]
               [--mutex-arg1 MUTEX_ARG1 | --mutex-arg2 MUTEX_ARG2]
               [--child-arg1 CHILD_ARG1] [--child-arg2 CHILD_ARG2]

optional arguments:
  -h, --help            show this help message and exit
  --mutex-arg1 MUTEX_ARG1
  --mutex-arg2 MUTEX_ARG2
  --child-arg1 CHILD_ARG1
  --child-arg2 CHILD_ARG2

global arguments:
  --global-arg1 GLOBAL_ARG1
  --global-arg2 GLOBAL_ARG2


The error is that the --mutex-arg-s can be seen in "optional arguments" part instead of "global arguments" part in the second (child help) case.
In the first (parent help) case the --mutex-arg-s are printed into the good section.

----------
messages: 256518
nosy: balage
priority: normal
severity: normal
status: open
title: argparse help error: arguments created by add_mutually_exclusive_group() are shown outside their parent group created by add_argument_group()
type: behavior
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25882>
_______________________________________

From report at bugs.python.org  Wed Dec 16 09:49:53 2015
From: report at bugs.python.org (stephan)
Date: Wed, 16 Dec 2015 14:49:53 +0000
Subject: [New-bugs-announce] [issue25883] python 2.7.11 mod_wsgi regression
 on windows
Message-ID: <1450277393.92.0.39025404616.issue25883@psf.upfronthosting.co.za>


New submission from stephan:

Hi,

I use apache 32 bit on windows with mod_wsgi for my trac instance,
and other django instances which are attached by reverse-proxy.

With python (32bit) 2.7.10 it works, but as soon
as I updated to python 2.7.11 apache doesn't work anymore
(it does not respond to requests). 

I find out that the mod_wsgi.so module
causes the problem.
If I deactivate mod_wsgi (and by this my trac instance) the
other stuff works again.

In the apache error log I see the following:

------------
[Wed Dec 16 08:56:57.130160 2015] [mpm_winnt:notice] [pid 4184:tid 664] AH00428: Parent: child process 6708 exited with status 1 -- Restarting.
[Wed Dec 16 08:56:57.130160 2015] [core:error] [pid 4184:tid 664] AH00546: no record of generation 0 of exiting child 6708
[Wed Dec 16 08:56:57.817228 2015] [ssl:warn] [pid 4184:tid 664] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache]
[Wed Dec 16 08:56:57.817228 2015] [mpm_winnt:notice] [pid 4184:tid 664] AH00455: Apache/2.4.10 (Win32) mod_authn_ntlm/1.0.0 OpenSSL/1.0.1h mod_wsgi/4.4.9 Python/2.7.11 configured -- resuming normal operations
[Wed Dec 16 08:56:57.817228 2015] [mpm_winnt:notice] [pid 4184:tid 664] AH00456: Apache Lounge VC9 Server built: Jul 19 2014 13:07:40
[Wed Dec 16 08:56:57.817228 2015] [core:notice] [pid 4184:tid 664] AH00094: Command line: 'd:\\Programme\\Apache24\\bin\\httpd.exe -d D:/Programme/Apache24'
[Wed Dec 16 08:56:57.820229 2015] [mpm_winnt:notice] [pid 4184:tid 664] AH00418: Parent: Created child process 3656
[Wed Dec 16 08:56:59.035350 2015] [ssl:warn] [pid 3656:tid 676] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache]
ImportError: No module named site
[Wed Dec 16 08:56:59.054352 2015] [mpm_winnt:notice] [pid 4184:tid 664] AH00428: Parent: child process 3656 exited with status 1 -- Restarting.
[Wed Dec 16 08:56:59.054352 2015] [core:error] [pid 4184:tid 664] AH00546: no record of generation 0 of exiting child 3656
[Wed Dec 16 08:56:59.819429 2015] [ssl:warn] [pid 4184:tid 664] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache]
[Wed Dec 16 08:56:59.819429 2015] [mpm_winnt:notice] [pid 4184:tid 664] AH00455: Apache/2.4.10 (Win32) mod_authn_ntlm/1.0.0 OpenSSL/1.0.1h mod_wsgi/4.4.9 Python/2.7.11 configured -- resuming normal operations
[Wed Dec 16 08:56:59.819429 2015] [mpm_winnt:notice] [pid 4184:tid 664] AH00456: Apache Lounge VC9 Server built: Jul 19 2014 13:07:40
[Wed Dec 16 08:56:59.819429 2015] [core:notice] [pid 4184:tid 664] AH00094: Command line: 'd:\\Programme\\Apache24\\bin\\httpd.exe -d D:/Programme/Apache24'
[Wed Dec 16 08:56:59.821429 2015] [mpm_winnt:notice] [pid 4184:tid 664] AH00418: Parent: Created child process 8056
[Wed Dec 16 08:57:01.159563 2015] [ssl:warn] [pid 8056:tid 672] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache]
ImportError: No module named site
...
...
------------

and so on ... the error.log grows continuously even 
if do not send any request to apache,
because the process is restarted and restarted.

Now: 
 Or mod_wsgi.so (mod_wsgi-4.4.21.tar.gz) has a bug
 which didn't cause problems all the time,
 or the new python version introduced this bug.

----------
components: Windows
messages: 256522
nosy: paul.moore, stephan, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: python 2.7.11 mod_wsgi regression on windows
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25883>
_______________________________________

From report at bugs.python.org  Wed Dec 16 10:31:56 2015
From: report at bugs.python.org (Brandon Zerbe)
Date: Wed, 16 Dec 2015 15:31:56 +0000
Subject: [New-bugs-announce] [issue25884] inspect.getmro() fails when base
 class lacks __bases__ attribute.
Message-ID: <1450279916.96.0.180877215544.issue25884@psf.upfronthosting.co.za>


New submission from Brandon Zerbe:

I am using a possibly non-standard python package called Forthon, and when I inspect an object that is dependent on the Forthon class, I get the following error:

  File "/Users/zerbeb/homemade_programs/config2class/src/method_parsing.py", line 18, in get_all_init_args
    inherited_classes = inspect.getmro(class_obj)  
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/inspect.py", line 346, in getmro
    if hasattr(cls, "__bases__"):
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/inspect.py", line 337, in _searchbases
    for base in cls.__bases__:
AttributeError: 'Forthon' object has no attribute '__bases__'

This was easy enough to fix, simply add "if not hasattr(cls,'__bases__'): return" to the _searchbases function:

def _searchbases(cls, accum):
    # Simulate the "classic class" search order.
    if cls in accum:
        return
    if not hasattr(cls, "__bases__"): #Additional code.
        return
    accum.append(cls)
    for base in cls.__bases__:
        _searchbases(base, accum)

Maybe you have a better solution, but I think this edge case can be trivially solved however you decide to edit the code.

Thanks!

----------
messages: 256525
nosy: billyziege
priority: normal
severity: normal
status: open
title: inspect.getmro() fails when base class lacks __bases__ attribute.
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25884>
_______________________________________

From report at bugs.python.org  Wed Dec 16 16:09:07 2015
From: report at bugs.python.org (Myron Walker)
Date: Wed, 16 Dec 2015 21:09:07 +0000
Subject: [New-bugs-announce] [issue25885] ast Str type does not annotate the
 string type when it parses a python document
Message-ID: <1450300147.35.0.979412805294.issue25885@psf.upfronthosting.co.za>


New submission from Myron Walker:

The 'ast' module does not indicate the type of string, ''' or '"' or '"""', that it has encountered when it parses a python document.

This prevents accurate reproduction of the original parsed document by a writer walking over an instance of a abstract syntax tree.

----------
components: Extension Modules
messages: 256529
nosy: Myron Walker
priority: normal
severity: normal
status: open
title: ast Str type does not annotate the string type when it parses a python document
type: behavior
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25885>
_______________________________________

From report at bugs.python.org  Wed Dec 16 16:45:04 2015
From: report at bugs.python.org (Myron Walker)
Date: Wed, 16 Dec 2015 21:45:04 +0000
Subject: [New-bugs-announce] [issue25886] ast module is combining string
 literals that are concatenated with plus operator
Message-ID: <1450302304.12.0.51873465137.issue25886@psf.upfronthosting.co.za>


New submission from Myron Walker:

ast module is combining string literals that are concatenated with plus operator into a single string in the parsestrplus module rather than maintaining the true syntax tree of the original document.

The fact that ast combines strings and does not maintain the original syntax of the document means that original syntax information is lost and a writer walking the abstract syntax tree is unable to reproduce the original syntax
of the document.

----------
components: Interpreter Core
messages: 256533
nosy: Myron Walker
priority: normal
severity: normal
status: open
title: ast module is combining string literals that are concatenated with plus operator
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25886>
_______________________________________

From report at bugs.python.org  Wed Dec 16 16:46:57 2015
From: report at bugs.python.org (Yury Selivanov)
Date: Wed, 16 Dec 2015 21:46:57 +0000
Subject: [New-bugs-announce] [issue25887] awaiting on coroutine more than
 once should be an error
Message-ID: <1450302417.78.0.492418197951.issue25887@psf.upfronthosting.co.za>


New submission from Yury Selivanov:

async def foo():
    return 123

print(await foo())   # will print 123
print(await foo())   # prints None
print(await foo())   # prints None


The above code illustrates the current behaviour.  I propose to change it, so that second 'await' will trigger a RuntimeError, explaining the the coroutine was awaited more than once.

This would make coroutines more predictable, and would allow users to catch subtle bugs in their code.

This topic was originally brought up in this thread: https://mail.python.org/pipermail/python-dev/2015-December/142443.html

----------
assignee: yselivanov
components: Interpreter Core
messages: 256535
nosy: asvetlov, gvanrossum, haypo, ncoghlan, yselivanov
priority: normal
severity: normal
status: open
title: awaiting on coroutine more than once should be an error
type: enhancement
versions: Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25887>
_______________________________________

From report at bugs.python.org  Wed Dec 16 16:51:12 2015
From: report at bugs.python.org (Yury Selivanov)
Date: Wed, 16 Dec 2015 21:51:12 +0000
Subject: [New-bugs-announce] [issue25888] awaiting on coroutine that is
 being awaited should be an error
Message-ID: <1450302672.61.0.939075659371.issue25888@psf.upfronthosting.co.za>


New submission from Yury Selivanov:

This problem was discussed in one of the asyncio issues here: https://github.com/python/asyncio/issues/288

I propose to raise a RuntimeError if an 'await' expression is used for a coroutine object that's being awaited on already.  This change shouldn't impact performance in any way.  It will prevent users from writing code that behaves in a very weird ways (see the github link for an example).

----------
assignee: yselivanov
components: Interpreter Core
messages: 256539
nosy: asvetlov, gvanrossum, haypo, ncoghlan, yselivanov
priority: normal
severity: normal
status: open
title: awaiting on coroutine that is being awaited should be an error
type: enhancement
versions: Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25888>
_______________________________________

From report at bugs.python.org  Wed Dec 16 17:28:45 2015
From: report at bugs.python.org (Alexander Riccio)
Date: Wed, 16 Dec 2015 22:28:45 +0000
Subject: [New-bugs-announce] [issue25889] Find_BOM accepts a char*, but is
 passed an unsigned char*; and related usage
Message-ID: <1450304925.0.0.820557510114.issue25889@psf.upfronthosting.co.za>


New submission from Alexander Riccio:

This is safe, but warns on /W4. In maybe_handle_shebang, an unsigned char* is passed to find_BOM, which accepts a char* (https://hg.python.org/cpython/file/tip/PC/launcher.c#l1139).

Without an explicit cast, this generates a warning:

10>..\PC\launcher.c(1139): warning C4057: 'function': 'char *' differs in indirection to slightly different base types from 'unsigned char [256]'

    for `bom = find_BOM(buffer);`

Similarly, assigning start to buffer generates warnings:

10>..\PC\launcher.c(1141): warning C4057: '=': 'char *' differs in indirection to slightly different base types from 'unsigned char *'

    for `start = buffer;`


10>..\PC\launcher.c(1148): warning C4057: '=': 'char *' differs in indirection to slightly different base types from 'unsigned char *'
    for `start = &buffer[bom->length];`

----------
components: Windows
messages: 256547
nosy: Alexander Riccio, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Find_BOM accepts a char*, but is passed an unsigned char*; and related usage
type: compile error

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25889>
_______________________________________

From report at bugs.python.org  Wed Dec 16 17:38:25 2015
From: report at bugs.python.org (Alexander Riccio)
Date: Wed, 16 Dec 2015 22:38:25 +0000
Subject: [New-bugs-announce] [issue25890] PyObject *po in
 _listdir_windows_no_opendir is initialized but not used
Message-ID: <1450305505.9.0.129270836576.issue25890@psf.upfronthosting.co.za>


New submission from Alexander Riccio:

See: https://hg.python.org/cpython/file/tip/Modules/posixmodule.c#l3466

The variable PyObject *po in _listdir_windows_no_opendir is initialized but not used. Given that there's a variable named po_wchars, and two PyObject variables, I'm going to guess that the programmer forgot about `v`.

----------
components: Windows
messages: 256549
nosy: Alexander Riccio, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: PyObject *po in _listdir_windows_no_opendir is initialized but not used
type: compile error

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25890>
_______________________________________

From report at bugs.python.org  Wed Dec 16 17:41:41 2015
From: report at bugs.python.org (Alexander Riccio)
Date: Wed, 16 Dec 2015 22:41:41 +0000
Subject: [New-bugs-announce] [issue25891] Stray variable meth_idx in
 enable_symlink
Message-ID: <1450305701.06.0.764656657931.issue25891@psf.upfronthosting.co.za>


New submission from Alexander Riccio:

See: https://hg.python.org/cpython/file/tip/Modules/posixmodule.c#l12383

The variable int meth_idx is initialized but not used. I have no idea how it got there.

----------
components: Windows
messages: 256553
nosy: Alexander Riccio, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Stray variable meth_idx in enable_symlink
type: compile error

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25891>
_______________________________________

From report at bugs.python.org  Wed Dec 16 17:44:22 2015
From: report at bugs.python.org (Alexander Riccio)
Date: Wed, 16 Dec 2015 22:44:22 +0000
Subject: [New-bugs-announce] [issue25892] PyObject *exc in
 encode_code_page_strict is initialized but not used
Message-ID: <1450305862.36.0.643311084113.issue25892@psf.upfronthosting.co.za>


New submission from Alexander Riccio:

See: https://hg.python.org/cpython/file/tip/Objects/unicodeobject.c#l7335

The variable PyObject *exc in encode_code_page_strict is initialized but not used.

----------
components: Windows
messages: 256554
nosy: Alexander Riccio, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: PyObject *exc in encode_code_page_strict is initialized but not used
type: compile error

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25892>
_______________________________________

From report at bugs.python.org  Wed Dec 16 17:47:25 2015
From: report at bugs.python.org (Alexander Riccio)
Date: Wed, 16 Dec 2015 22:47:25 +0000
Subject: [New-bugs-announce] [issue25893] Second variable DWORD reqdSize in
 getpythonregpath is initialized but not used
Message-ID: <1450306045.17.0.49085988096.issue25893@psf.upfronthosting.co.za>


New submission from Alexander Riccio:

See: https://hg.python.org/cpython/file/tip/PC/getpathp.c#l324

The second variable named `reqdSize` in getpythonregpath is initialized but not used.

----------
components: Windows
messages: 256555
nosy: Alexander Riccio, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Second variable DWORD reqdSize in getpythonregpath is initialized but not used
type: compile error

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25893>
_______________________________________

From report at bugs.python.org  Thu Dec 17 00:49:35 2015
From: report at bugs.python.org (Zachary Ware)
Date: Thu, 17 Dec 2015 05:49:35 +0000
Subject: [New-bugs-announce] [issue25894] unittest subTest failure causes
 result to be omitted from listing
Message-ID: <1450331375.94.0.689081172202.issue25894@psf.upfronthosting.co.za>


New submission from Zachary Ware:

The title can barely be called accurate; the description of the problem isn't easy to condense to title length.  Here's the issue:

$ cat subtest_test.py 
import os
import unittest

class TestClass(unittest.TestCase):

    def test_subTest(self):
        for t in map(int, os.environ.get('tests', '1')):
            with self.subTest(t):
                if t > 1:
                    raise unittest.SkipTest('skipped')
                self.assertTrue(t)

if __name__ == '__main__':
    unittest.main()
$ ./python.exe subtest_test.py 
.
----------------------------------------------------------------------
Ran 1 test in 0.000s

OK
$ tests=01 ./python.exe subtest_test.py 

======================================================================
FAIL: test_subTest (__main__.TestClass) (<subtest>)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "subtest_test.py", line 12, in test_subTest
    self.assertTrue(t)
AssertionError: 0 is not true

----------------------------------------------------------------------
Ran 1 test in 0.001s

FAILED (failures=1)
$ tests=012 ./python.exe subtest_test.py 
s
======================================================================
FAIL: test_subTest (__main__.TestClass) (<subtest>)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "subtest_test.py", line 12, in test_subTest
    self.assertTrue(t)
AssertionError: 0 is not true

----------------------------------------------------------------------
Ran 1 test in 0.001s

FAILED (failures=1, skipped=1)



Note that on the first run, the short summary is ".", as expected.  The second is "", when one of the subTests fails, but then the third is "s", when one subtest fails but another is skipped.  This also extends to verbose mode:

$ ./python.exe subtest_test.py -v
test_subTest (__main__.TestClass) ... ok

----------------------------------------------------------------------
Ran 1 test in 0.001s

OK
$ tests=01 ./python.exe subtest_test.py -v
test_subTest (__main__.TestClass) ... 
======================================================================
FAIL: test_subTest (__main__.TestClass) (<subtest>)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "subtest_test.py", line 12, in test_subTest
    self.assertTrue(t)
AssertionError: 0 is not true

----------------------------------------------------------------------
Ran 1 test in 0.001s

FAILED (failures=1)
$ tests=012 ./python.exe subtest_test.py -v
test_subTest (__main__.TestClass) ... skipped 'skipped'

======================================================================
FAIL: test_subTest (__main__.TestClass) (<subtest>)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "subtest_test.py", line 12, in test_subTest
    self.assertTrue(t)
AssertionError: 0 is not true

----------------------------------------------------------------------
Ran 1 test in 0.001s

FAILED (failures=1, skipped=1)


Note the first run shows "... ok", the second "... ", and the third "... skipped 'skipped'"


I'm unsure what the solution should be.  There should at least be some indication that the test finished, but should mixed results be reported as 'm' ("mixed results" in verbose mode), or should failure/error take precedence, or should every different result be represented?

----------
components: Library (Lib)
messages: 256580
nosy: ezio.melotti, michael.foord, pitrou, rbcollins, zach.ware
priority: normal
severity: normal
stage: test needed
status: open
title: unittest subTest failure causes result to be omitted from listing
type: behavior
versions: Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25894>
_______________________________________

From report at bugs.python.org  Thu Dec 17 00:58:53 2015
From: report at bugs.python.org (Gergely Imreh)
Date: Thu, 17 Dec 2015 05:58:53 +0000
Subject: [New-bugs-announce] [issue25895] urllib.parse.urljoin does not
 handle WebSocket URLs
Message-ID: <1450331933.69.0.301225840177.issue25895@psf.upfronthosting.co.za>


New submission from Gergely Imreh:

Handling the "ws" and "wss" schemes of the WebSocket protocol in urllib.parse.urlparse was discussed in a previous issue http://bugs.python.org/issue13244 Parsing them seems to work correctly:

>>> urllib.parse.urlparse("wss://domain/endpoint")
ParseResult(scheme='wss', netloc='domain', path='/endpoint', params='', query='', fragment='')

On the other hand, urllib.parse.urljoin does not know about these schemes and thus cannot be used to construct WebSocket URLs (as, for example some streaming data APIs now seem to use it, such as https://starfighter.readme.io/docs/quotes-ticker-tape-websocket).

Using the example above I get:

>>> urllib.parse.urljoin("wss://domain/","/endpoint")
'/endpoint'

This is not the expected result, 'wss://example.com/endpoint', because these WebSocket schemes are not included in the uses_relative and uses_netloc lists in the library settings. For clarity, based on the previous issue's discussion and RFC6455 Section 11.1 https://tools.ietf.org/html/rfc6455#section-11.1 , these are the only two portions that apply, and should not be listed in uses_params.

As a workaround, similarly to the previous issue's recommendation, one can use:

>> import urlparse.parse
>> wsschemes = ["ws", "wss"]
>> urlparse.parse.uses_relative.extend(wsschemes)
>> urlparse.parse.uses_netloc.extend(wsschemes)

Attached patch to this effect. Also added tests to cover these schemes, though comments are definitely welcome on all of this!

----------
files: 0001-urllib.parse-enable-WebSocket-URL-schemes-to-be-corr.patch
keywords: patch
messages: 256581
nosy: imrehg
priority: normal
severity: normal
status: open
title: urllib.parse.urljoin does not handle WebSocket URLs
type: behavior
versions: Python 3.4, Python 3.5
Added file: http://bugs.python.org/file41334/0001-urllib.parse-enable-WebSocket-URL-schemes-to-be-corr.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25895>
_______________________________________

From report at bugs.python.org  Thu Dec 17 15:18:44 2015
From: report at bugs.python.org (Zoinkity .)
Date: Thu, 17 Dec 2015 20:18:44 +0000
Subject: [New-bugs-announce] [issue25896] array.array accepting byte-order
 codes in format strings
Message-ID: <1450383524.81.0.399490494849.issue25896@psf.upfronthosting.co.za>


New submission from Zoinkity .:

I'd like to propose allowing the use of byte-order characters in the typecode string used by the array.array class.  

This removes any ambiguity on the order of the data, especially when that data is not known and loaded from an outside source.  You wouldn't need to presume little or big endian machine byteorder or test the system to determine this.  Also, it removes the necessity of byteswapping data that isn't in the correct order.

----------
components: Extension Modules
messages: 256614
nosy: Zoinkity..
priority: normal
severity: normal
status: open
title: array.array accepting byte-order codes in format strings
type: enhancement
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25896>
_______________________________________

From report at bugs.python.org  Thu Dec 17 16:29:54 2015
From: report at bugs.python.org (G)
Date: Thu, 17 Dec 2015 21:29:54 +0000
Subject: [New-bugs-announce] [issue25897] Python 3.5.1 and Active Tcl/Tk
 8.6.4.1
Message-ID: <1450387794.43.0.482847270391.issue25897@psf.upfronthosting.co.za>


New submission from G:

I have installed one copy of Python 3.5.1 and Tcl/Tk 8.6.4.1 in a high school lab with 28 more computers. Want to be sure I'm doing it correctly. Before the update we were running Python 2.7.10 and always got a warning: Tcl/Tk (8.5.9) may be unstable. I'm still getting the same warning after installing Tcl/Tk 8.6.4.1 . What to I need to do so 3.5.1 sees the correct Tcl/Tk file? What does unstable in this context mean? We had no issues I was aware of.

----------
files: python update 1.png
messages: 256616
nosy: ccgm
priority: normal
severity: normal
status: open
title: Python 3.5.1 and Active Tcl/Tk 8.6.4.1
type: behavior
versions: Python 3.5
Added file: http://bugs.python.org/file41340/python update 1.png

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25897>
_______________________________________

From report at bugs.python.org  Thu Dec 17 20:45:11 2015
From: report at bugs.python.org (Sebastian Linke)
Date: Fri, 18 Dec 2015 01:45:11 +0000
Subject: [New-bugs-announce] [issue25898] Check for subsequence inside a
 sequence
Message-ID: <1450403111.33.0.306166289689.issue25898@psf.upfronthosting.co.za>


New submission from Sebastian Linke:

With the attached patch I propose to add a new function to the "collections" module. It is meant to be used for determining whether a given subsequence is part of a particular sequence (with respect to the ordering of the subsequence). 

Doing this in pure Python (using the CPython interpreter) is relatively slow. So I did the implementation in C.

----------
components: Library (Lib)
files: has_subsequence.patch
keywords: patch
messages: 256633
nosy: seblin
priority: normal
severity: normal
status: open
title: Check for subsequence inside a sequence
type: enhancement
versions: Python 3.6
Added file: http://bugs.python.org/file41342/has_subsequence.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25898>
_______________________________________

From report at bugs.python.org  Fri Dec 18 02:43:12 2015
From: report at bugs.python.org (Chris Angelico)
Date: Fri, 18 Dec 2015 07:43:12 +0000
Subject: [New-bugs-announce] [issue25899] Unnecessary non-ASCII characters
 in standard library
Message-ID: <1450424592.81.0.453226541982.issue25899@psf.upfronthosting.co.za>


New submission from Chris Angelico:

Discussion on python-list led to searching out unnecessary non-ASCII in the stdlib. While there are places where non-ASCII text is good and worthwhile (eg in comments identifying people such as ?ukasz Langa, Peter ?strand, Martin v. L?wis, and Gerhard H?ring, or code specifically demonstrating or implementing non-ASCII behaviour), there are some instances which are unnecessary. Attached is a patch converting apostrophes, dashes, and one space.

----------
components: Library (Lib)
files: asciify.diff
keywords: patch
messages: 256647
nosy: Rosuav
priority: normal
severity: normal
status: open
title: Unnecessary non-ASCII characters in standard library
versions: Python 3.6
Added file: http://bugs.python.org/file41344/asciify.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25899>
_______________________________________

From report at bugs.python.org  Fri Dec 18 03:48:29 2015
From: report at bugs.python.org (Marius Gedminas)
Date: Fri, 18 Dec 2015 08:48:29 +0000
Subject: [New-bugs-announce] [issue25900] unittest ignores the first ctrl-c
 when it shouldn't
Message-ID: <1450428509.62.0.620097682631.issue25900@psf.upfronthosting.co.za>


New submission from Marius Gedminas:

unittest.signals._InterruptHandler is very nice: on first ^C it tells any registered unittest Result instances to gracefully stop the test run, and on any subsequent ^C it defers to the default interrupt handler, which immediately terminates the test run (possibly without giving it a chance to output summary information).

This doesn't work very well when a test runner forgets to register the Result instance: the first ^C is then quietly ignored.  (See https://github.com/django-nose/django-nose/issues/252 for an example.)

Suggestion: if there are no registered results in the unittest.signals._results dict, don't silently ignore the first ^C.  Instead, immediately defer to the saved interrupt handler.

Since code is often clearer than words, I'm attaching a patch.

----------
components: Library (Lib)
files: dont-ignore-first-ctrl-c.patch
keywords: patch
messages: 256656
nosy: mgedmin
priority: normal
severity: normal
status: open
title: unittest ignores the first ctrl-c when it shouldn't
type: behavior
Added file: http://bugs.python.org/file41345/dont-ignore-first-ctrl-c.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25900>
_______________________________________

From report at bugs.python.org  Fri Dec 18 04:39:56 2015
From: report at bugs.python.org (fluyy)
Date: Fri, 18 Dec 2015 09:39:56 +0000
Subject: [New-bugs-announce] [issue25901] make test crash
Message-ID: <1450431596.39.0.127057535.issue25901@psf.upfronthosting.co.za>


New submission from fluyy:

I Compile the Python interpreter statically.

$ uname -a
Linux ubuntu 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

fluyy at ubuntu:~/tmp/Python-3.5.1$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 5.2.1-22ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-5 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)


 ./configure LDFLAGS="-Wl,-no-export-dynamic -Wl,--no-as-needed -static-libgcc -static" CPPFLAGS="-static -fPIC" -disable-shared -prefix="/home/fluyy/python3.5"

and I change -O3 to -O2 in Makefile

I had change some complie options. because make is error

the options I changed is :

1.gcc -pthread -Wl,-no-export-dynamic -Wl,--no-as-needed -static-libgcc -static  -o Programs/_freeze_importlib Programs/_freeze_importlib.o Modules/getbuildinfo.o Parser/acceler.o Parser/grammar1.o Parser/listnode.o Parser/node.o Parser/parser.o Parser/bitset.o Parser/metagrammar.o Parser/firstsets.o Parser/grammar.o Parser/pgen.o Parser/myreadline.o Parser/parsetok.o Parser/tokenizer.o Objects/abstract.o Objects/accu.o Objects/boolobject.o Objects/bytes_methods.o Objects/bytearrayobject.o Objects/bytesobject.o Objects/cellobject.o Objects/classobject.o Objects/codeobject.o Objects/complexobject.o Objects/descrobject.o Objects/enumobject.o Objects/exceptions.o Objects/genobject.o Objects/fileobject.o Objects/floatobject.o Objects/frameobject.o Objects/funcobject.o Objects/iterobject.o Objects/listobject.o Objects/longobject.o Objects/dictobject.o Objects/odictobject.o Objects/memoryobject.o Objects/methodobject.o Objects/moduleobject.o Objects/namespaceobject.o Objects/object.o Objects/obmalloc.o Objects/capsule.o Objects/rangeobject.o Objects/setobject.o Objects/sliceobject.o Objects/structseq.o Objects/tupleobject.o Objects/typeobject.o Objects/unicodeobject.o Objects/unicodectype.o Objects/weakrefobject.o Python/_warnings.o Python/Python-ast.o Python/asdl.o Python/ast.o Python/bltinmodule.o Python/ceval.o Python/compile.o Python/codecs.o Python/dynamic_annotations.o Python/errors.o Python/frozenmain.o Python/future.o Python/getargs.o Python/getcompiler.o Python/getcopyright.o Python/getplatform.o Python/getversion.o Python/graminit.o Python/import.o Python/importdl.o Python/marshal.o Python/modsupport.o Python/mystrtoul.o Python/mysnprintf.o Python/peephole.o Python/pyarena.o Python/pyctype.o Python/pyfpe.o Python/pyhash.o Python/pylifecycle.o Python/pymath.o Python/pystate.o Python/pythonrun.o Python/pytime.o Python/random.o Python/structmember.o Python/symtable.o Python/sysmodule.o Python/traceback.o Python/getopt.o Python/pystrcmp.o Python/pystrtod.o Python/pystrhex.o Python/dtoa.o Python/formatter_unicode.o Python/fileutils.o Python/dynload_shlib.o   Python/thread.o Modules/config.o Modules/getpath.o Modules/main.o Modules/gcmodule.o  Modules/_threadmodule.o  Modules/signalmodule.o  Modules/posixmodule.o  Modules/errnomodule.o  Modules/pwdmodule.o  Modules/_sre.o  Modules/_codecsmodule.o  Modules/_weakref.o  Modules/_functoolsmodule.o  Modules/_operator.o  Modules/_collectionsmodule.o  Modules/itertoolsmodule.o  Modules/atexitmodule.o  Modules/_stat.o  Modules/timemodule.o  Modules/_localemodule.o  Modules/_iomodule.o Modules/iobase.o Modules/fileio.o Modules/bytesio.o Modules/bufferedio.o Modules/textio.o Modules/stringio.o  Modules/zipimport.o  Modules/faulthandler.o  Modules/_tracemalloc.o Modules/hashtable.o  Modules/symtablemodule.o  Modules/readline.o  Modules/arraymodule.o  Modules/mathmodule.o Modules/_math.o  Modules/_struct.o  Modules/_randommodule.o  Modules/_elementtree.o  Modules/_pickle.o  Modules/_datetimemodule.o  Modules/_bisectmodule.o  Modules/_heapqmodule.o  Modules/unicodedata.o  Modules/fcntlmodule.o  Modules/spwdmodule.o  Modules/grpmodule.o  Modules/selectmodule.o  Modules/mmapmodule.o  Modules/_csv.o  Modules/socketmodule.o  Modules/_ssl.o  Modules/_cryptmodule.o  Modules/_posixsubprocess.o  Modules/md5module.o  Modules/sha1module.o  Modules/sha256module.o  Modules/sha512module.o  Modules/syslogmodule.o  Modules/binascii.o  Modules/parsermodule.o  Modules/zlibmodule.o  Modules/xmlparse.o Modules/xmlrole.o Modules/xmltok.o Modules/pyexpat.o  Modules/multibytecodec.o  Modules/_codecs_cn.o  Modules/_codecs_hk.o  Modules/_codecs_iso2022.o  Modules/_codecs_jp.o  Modules/_codecs_kr.o  Modules/_codecs_tw.o  Modules/xxsubtype.o  /usr/lib/x86_64-linux-gnu/libssl.a /usr/lib/x86_64-linux-gnu/libcrypto.a -lpthread -ldl  -lutil -lreadline -ltermcap                   -L/lib -lssl -lcrypto  -lcrypt          -L/home/fluyy/python3.5/lib -lz                              -lreadline -ltermcap                   -L/lib -lssl -lcrypto  -lcrypt          -L/home/fluyy/python3.5/lib -lz    -lm

2.gcc -pthread -Wl,-no-export-dynamic -Wl,--no-as-needed -static-libgcc -static -export-dynamic -o python Programs/python.o libpython3.5m.a /usr/lib/x86_64-linux-gnu/libssl.a /usr/lib/x86_64-linux-gnu/libcrypto.a -lpthread -ldl  -lutil -lreadline -ltermcap                   -L/lib -lssl -lcrypto  -lcrypt          -L/home/fluyy/python3.5/lib -lz                              -lreadline -ltermcap                   -L/lib -lssl -lcrypto  -lcrypt          -L/home/fluyy/python3.5/lib -lz          -lm

3.gcc -pthread -Wl,-no-export-dynamic -Wl,--no-as-needed -static-libgcc -static -export-dynamic -o Programs/_testembed Programs/_testembed.o libpython3.5m.a /usr/lib/x86_64-linux-gnu/libssl.a /usr/lib/x86_64-linux-gnu/libcrypto.a -lpthread -ldl  -lutil -lreadline -ltermcap                   -L/lib -lssl -lcrypto  -lcrypt          -L/home/fluyy/python3.5/lib -lz                              -lreadline -ltermcap                   -L/lib -lssl -lcrypto  -lcrypt          -L/home/fluyy/python3.5/lib -lz          -lm


when I make test , the python is Crash!

[ 92/397/11] test_uu
[ 93/397/11] test_html
[ 94/397/11] test_sched
[ 95/397/11] test_bigmem
[ 96/397/11] test_pkgutil
[ 97/397/12] test_csv
test test_csv failed -- Traceback (most recent call last):
  File "/home/fluyy/tmp/Python-3.5.1/Lib/test/test_csv.py", line 213, in test_writerows_legacy_strings
    import _testcapi
ImportError: No module named '_testcapi'
[ 98/397/12] test_augassign
[ 99/397/12] test_httpservers
Fatal Python error: Segmentation fault

Current thread 0x00007f0f647d5700 (most recent call first):
  File "/home/fluyy/tmp/Python-3.5.1/Lib/socketserver.py", line 457 in server_bind
  File "/home/fluyy/tmp/Python-3.5.1/Lib/http/server.py", line 138 in server_bind
  File "/home/fluyy/tmp/Python-3.5.1/Lib/socketserver.py", line 443 in __init__
  File "/home/fluyy/tmp/Python-3.5.1/Lib/test/test_httpservers.py", line 42 in run
  File "/home/fluyy/tmp/Python-3.5.1/Lib/threading.py", line 914 in _bootstrap_inner
  File "/home/fluyy/tmp/Python-3.5.1/Lib/threading.py", line 882 in _bootstrap

Thread 0x0000000001b188c0 (most recent call first):
  File "/home/fluyy/tmp/Python-3.5.1/Lib/threading.py", line 293 in wait
  File "/home/fluyy/tmp/Python-3.5.1/Lib/threading.py", line 549 in wait
  File "/home/fluyy/tmp/Python-3.5.1/Lib/test/test_httpservers.py", line 62 in setUp
  File "/home/fluyy/tmp/Python-3.5.1/Lib/unittest/case.py", line 596 in run
  File "/home/fluyy/tmp/Python-3.5.1/Lib/unittest/case.py", line 648 in __call__
  File "/home/fluyy/tmp/Python-3.5.1/Lib/unittest/suite.py", line 122 in run
  File "/home/fluyy/tmp/Python-3.5.1/Lib/unittest/suite.py", line 84 in __call__
  File "/home/fluyy/tmp/Python-3.5.1/Lib/unittest/suite.py", line 122 in run
  File "/home/fluyy/tmp/Python-3.5.1/Lib/unittest/suite.py", line 84 in __call__
  File "/home/fluyy/tmp/Python-3.5.1/Lib/test/support/__init__.py", line 1677 in run
  File "/home/fluyy/tmp/Python-3.5.1/Lib/test/support/__init__.py", line 1778 in _run_suite
  File "/home/fluyy/tmp/Python-3.5.1/Lib/test/support/__init__.py", line 1812 in run_unittest
  File "/home/fluyy/tmp/Python-3.5.1/Lib/test/test_httpservers.py", line 921 in test_main
  File "/home/fluyy/tmp/Python-3.5.1/Lib/test/regrtest.py", line 1305 in runtest_inner
  File "/home/fluyy/tmp/Python-3.5.1/Lib/test/regrtest.py", line 1002 in runtest
  File "/home/fluyy/tmp/Python-3.5.1/Lib/test/regrtest.py", line 545 in main
  File "/home/fluyy/tmp/Python-3.5.1/Lib/test/regrtest.py", line 1591 in main_in_temp_cwd
  File "/home/fluyy/tmp/Python-3.5.1/Lib/test/regrtest.py", line 1616 in <module>
  File "/home/fluyy/tmp/Python-3.5.1/Lib/runpy.py", line 85 in _run_code
  File "/home/fluyy/tmp/Python-3.5.1/Lib/runpy.py", line 170 in _run_module_as_main
Traceback (most recent call last):
  File "/home/fluyy/tmp/Python-3.5.1/Lib/runpy.py", line 170, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/fluyy/tmp/Python-3.5.1/Lib/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/fluyy/tmp/Python-3.5.1/Lib/test/__main__.py", line 3, in <module>
    regrtest.main_in_temp_cwd()
  File "/home/fluyy/tmp/Python-3.5.1/Lib/test/regrtest.py", line 1591, in main_in_temp_cwd
    main()
  File "/home/fluyy/tmp/Python-3.5.1/Lib/test/regrtest.py", line 756, in main
    raise Exception("Child error on {}: {}".format(test, result[1]))
Exception: Child error on test_httpservers: Exit code -11

----------
components: Tests
messages: 256661
nosy: fluyy
priority: normal
severity: normal
status: open
title: make test crash
type: crash
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25901>
_______________________________________

From report at bugs.python.org  Fri Dec 18 07:04:44 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 18 Dec 2015 12:04:44 +0000
Subject: [New-bugs-announce] [issue25902] Fixed various refcount issues in
 ElementTree iteration
Message-ID: <1450440284.88.0.232739188714.issue25902@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

ElementTree iteration code holds borrowed references when call user code (comparison with the tag, concatenating text and tail lazy lists, testing text and tail for empty). User code can make borrowed references invalid and this can lead to a crash. One example is provided by Martin in msg256495. Other possible cases can be more hard to reproduce.

Proposed patch makes iterating code to own references that it operates.

----------
components: Extension Modules, XML
files: etree_iter_refcount.patch
keywords: patch
messages: 256673
nosy: martin.panter, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Fixed various refcount issues in ElementTree iteration
type: crash
versions: Python 2.7, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41352/etree_iter_refcount.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25902>
_______________________________________

From report at bugs.python.org  Fri Dec 18 07:18:30 2015
From: report at bugs.python.org (Devyn Johnson)
Date: Fri, 18 Dec 2015 12:18:30 +0000
Subject: [New-bugs-announce] [issue25903] SUGGESTION: Optimize code in PYO
Message-ID: <1450441110.24.0.672371380209.issue25903@psf.upfronthosting.co.za>


New submission from Devyn Johnson:

I have a suggestion. When Python code is byte-compiled to *.pyo files, what if byte-compiler were to be made to enhance some of the code. For instance, "if type(OBJECT) == int:" would be changed to "if isinstance(OBJECT, int):". Python is used in numerous software, so why not add a feature like this that could increase performance?

----------
messages: 256676
nosy: Devyn Johnson
priority: normal
severity: normal
status: open
title: SUGGESTION: Optimize code in PYO
type: enhancement
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25903>
_______________________________________

From report at bugs.python.org  Fri Dec 18 07:23:27 2015
From: report at bugs.python.org (Devyn Johnson)
Date: Fri, 18 Dec 2015 12:23:27 +0000
Subject: [New-bugs-announce] [issue25904] SUGGESTION: New Datatypes
Message-ID: <1450441407.46.0.0976006490592.issue25904@psf.upfronthosting.co.za>


New submission from Devyn Johnson:

As we all know, Python is sometimes used to computer large numbers and precise numbers (i.e. doubles) with the help of third-party modules. In my opinion, it seems that Python may benefit from gaining new data-types such as "longint" (a "long long" in C) and "quad" (a "long double" in C). Thus, Python could natively be used for processing larger numbers than Python3.6.

----------
components: Interpreter Core
messages: 256678
nosy: Devyn Johnson
priority: normal
severity: normal
status: open
title: SUGGESTION: New Datatypes
type: behavior
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25904>
_______________________________________

From report at bugs.python.org  Fri Dec 18 07:29:52 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 18 Dec 2015 12:29:52 +0000
Subject: [New-bugs-announce] [issue25905] IDLE fails to display the README
 file
Message-ID: <1450441792.4.0.635729771057.issue25905@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

When open the About IDLE dialog and press the README button on bottom line, I get the UnicodeDecodeError:

Exception in Tkinter callback
Traceback (most recent call last):
  File "/home/serhiy/py/cpython/Lib/tkinter/__init__.py", line 1548, in __call__
    return self.func(*args)
  File "/home/serhiy/py/cpython/Lib/idlelib/aboutDialog.py", line 127, in ShowIDLEAbout
    self.display_file_text('About - Readme', 'README.txt')
  File "/home/serhiy/py/cpython/Lib/idlelib/aboutDialog.py", line 139, in display_file_text
    textView.view_file(self, title, fn, encoding)
  File "/home/serhiy/py/cpython/Lib/idlelib/textView.py", line 74, in view_file
    contents = file.read()
  File "/home/serhiy/py/cpython/Lib/codecs.py", line 321, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x92 in position 72: invalid start byte

That is because IDLE opens the Lib/idlelib/README.txt file with default (locale) encoding, while it contains the RIGHT SINGLE QUOTATION MARK character encoded with the CP1252 encoding and non-decodable with UTF-8.

I think IDLE should open all distributed files with UTF-8 encoding. Lib/idlelib/CREDITS.txt and Lib/idlelib/README.txt should be recoded to UTF-8.

----------
components: IDLE
messages: 256679
nosy: Rosuav, kbk, roger.serwy, serhiy.storchaka, terry.reedy
priority: normal
severity: normal
status: open
title: IDLE fails to display the README file
type: behavior
versions: Python 2.7, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25905>
_______________________________________

From report at bugs.python.org  Fri Dec 18 09:40:44 2015
From: report at bugs.python.org (Christian Schou Oxvig)
Date: Fri, 18 Dec 2015 14:40:44 +0000
Subject: [New-bugs-announce] [issue25906] Worker stall in
 multiprocessing.Pool
Message-ID: <1450449644.82.0.612761647366.issue25906@psf.upfronthosting.co.za>


New submission from Christian Schou Oxvig:

I am experiencing some seemingly random stalls in my scientific simulations that make use of a multiprocessing.Pool for parallelization. It has been incredibly difficult for me to come up with an example that consistently reproduces the problem. It seems more or less random if and when the problem occurs. The below snippet is my best shot at something that has a good chance at hitting the problem. I know it is unfortunate to have PyTables in the mix but it is the only example I have been able to come up with that almost always hit the problem. I have been able to reproduce the problem (once!) by simply removing the with-statement (and thus PyTables) in the work function. However, by doing so (at least in my runs), the chance of hitting the problem almost vanishes. Also, judging from the output of the script, it seems that the cause of the problem is to be found in Python and not in PyTables.


import os
import multiprocessing as mp
import tables

_hdf_db_name = 'join_crash_test.hdf'
_lock = mp.Lock()


class File():

    def __init__(self, *args, **kwargs):
        self._args = args
        self._kwargs = kwargs

        if len(args) > 0:
            self._filename = args[0]
        else:
            self._filename = kwargs['filename']

    def __enter__(self):
        _lock.acquire()
        self._file = tables.open_file(*self._args, **self._kwargs)
        return self._file

    def __exit__(self, type, value, traceback):
        self._file.close()
        _lock.release()


def work(task):
    worker_num, iteration = task

    with File(_hdf_db_name, mode='a') as h5_file:
        h5_file.create_array('/', 'a{}_{}'.format(worker_num, iteration),
                             obj=task)
    print('Worker {} finished writing to HDF table at iteration {}'.format(
        worker_num, iteration))

    return (worker_num, iteration)

iterations = 10
num_workers = 24
maxtasks = 1

if os.path.exists(_hdf_db_name):
    os.remove(_hdf_db_name)

for iteration in range(iterations):
    print('Now processing iteration: {}'.format(iteration))
    tasks = zip(range(num_workers), num_workers * [iteration])
    try:
        print('Spawning worker pool')
        workers = mp.Pool(num_workers, maxtasksperchild=maxtasks)
        print('Mapping tasks')
        results = workers.map(work, tasks, chunksize=1)
    finally:
        print('Cleaning up')
        workers.close()
        print('Workers closed - joining')
        workers.join()
        print('Process terminated')


In most of my test runs, this example stalls at "Workers closed - joining" in one of the iterations. Hitting C-c and inspecting the stack shows that the main process is waiting for a single worker that never stops executing. I have tested the example on various combinations of the below listed operating systems and Python version.

Ubuntu 14.04.1 LTS
Ubuntu 14.04.3 LTS
ArchLinux (updated as of December 14, 2015)

Python 2.7.10 :: Anaconda 2.2.0 (64-bit)
Python 2.7.11 :: Anaconda 2.4.0 (64-bit)
Python 2.7.11 (Arch Linux 64-bit build)
Python 3.3.5 :: Anaconda 2.1.0 (64-bit)
Python 3.4.3 :: Anaconda 2.3.0 (64-bit)
Python 3.5.0 :: Anaconda 2.4.0 (64-bit)
Python 3.5.1 (Arch Linux 64-bit build)
Python 3.5.1 :: Anaconda 2.4.0 (64-bit)

It seems that some combinations are more likely to reproduce the problem than others. In particular, all the Python 3 builds reproduce the problem on almost every run, whereas I have not been able to reproduce the problem with the above example on any version of Python 2. I have, however, seen what appears to be the same problem in one of my simulations using Python 2.7.11. After 5 hours it stalled very close to the point of closing a Pool. Inspecting the HDF database holding the results showed that all but a single of the 4000 tasks submitted to the Pool finished. To me, this suggests that a single worker never finished executing.

The problem I am describing here might very well be related to issue9205 as well as issue22393. However, I am not sure how to verify if this is indeed the case or not.

----------
messages: 256684
nosy: chroxvi
priority: normal
severity: normal
status: open
title: Worker stall in multiprocessing.Pool
type: behavior
versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25906>
_______________________________________

From report at bugs.python.org  Fri Dec 18 11:30:35 2015
From: report at bugs.python.org (Julien)
Date: Fri, 18 Dec 2015 16:30:35 +0000
Subject: [New-bugs-announce] [issue25907] Documentation i18n: Added trans
 tags in sphinx templates
Message-ID: <1450456235.45.0.408573494248.issue25907@psf.upfronthosting.co.za>


New submission from Julien:

o/

# Context

I'm trying to resuscitate the translation of Python doc in french, [python_doc_fr](https://github.com/AFPy/python_doc_fr).

I finished the translation of `tutorial.po` (that was partially translated by the AFPY team around 2012) and now working on `glossary.po` (~60%). :-)

# Problem

The homepage (`src/Doc/tools/templates/indexcontent.html`) is not translatable as is, as it misses the translation markers.

# Solution

I attached a patch to this issue adding them, it works well so I translated the generated `sphinx.po` and rebuilt the doc you can enjoy the result here:
 
http://www.afpy.org/doc/python/3.4/

----------
assignee: docs at python
components: Documentation
files: i18n.patch
keywords: patch
messages: 256691
nosy: docs at python, sizeof
priority: normal
severity: normal
status: open
title: Documentation i18n: Added trans tags in sphinx templates
versions: Python 3.4
Added file: http://bugs.python.org/file41355/i18n.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25907>
_______________________________________

From report at bugs.python.org  Fri Dec 18 14:41:10 2015
From: report at bugs.python.org (Thomas Jackson)
Date: Fri, 18 Dec 2015 19:41:10 +0000
Subject: [New-bugs-announce] [issue25908] ProcessPoolExecutor deadlock on
 KeyboardInterrupt
Message-ID: <1450467670.78.0.386832026046.issue25908@psf.upfronthosting.co.za>


New submission from Thomas Jackson:

If a KeyboardInterrupt is received while a worker process is grabbing an item off of the queue that worker process dies with an uncaught exception. This means that the ProcessPool now has lost a process, and currently has no mechanism to recover from dead processes. This is especially noticeable if the CallItem is relatively large (as the call_queue.get() includes all the pickle time).

A simple fix is to have the worker process not do anything with the keyboard interrupt-- since it would have no idea what to do. This cannot be implemented with a regular try/except-- as the item will be partially pulled off of the queue and lost. My proposed fix is to disable the SIGINT handler in the worker process while getting items off of the queue.

An alternate approach is to actually change multiprocessing.Queue.get() to leave the item on the queue if it is interrupted with a keyboard interrupt

to this is to catch the KeyboardInterrupt and simply continue on-- then we can rely on the caller to do the cleanup.This cannot be done by simply 


Proposed patch attached

----------
files: worker_ignore_interrupt.patch
keywords: patch
messages: 256703
nosy: jacksontj
priority: normal
severity: normal
status: open
title: ProcessPoolExecutor deadlock on KeyboardInterrupt
type: behavior
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41358/worker_ignore_interrupt.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25908>
_______________________________________

From report at bugs.python.org  Sat Dec 19 06:38:05 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 19 Dec 2015 11:38:05 +0000
Subject: [New-bugs-announce] [issue25909] Incorrect documentation for
 PyMapping_Items and like
Message-ID: <1450525085.87.0.352365699992.issue25909@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

The documentation and comments for PyMapping_Items, PyMapping_Keys and PyMapping_Values are not correct about return type.

The documentation says that return type is a list. For example for PyMapping_Items:

   On success, return a list of the items in object *o*, where each item is a tuple
   containing a key-value pair.  On failure, return *NULL*. This is equivalent to
   the Python expression ``list(o.items())``.

The comment in Include/abstract.h is more correct, it mentions tuple:

     On success, return a list or tuple of the items in object o,
     where each item is a tuple containing a key-value pair.
     On failure, return NULL.

Actually PyMapping_Items in 3.x can return a list, a tuple, or a dict view (for dict).

The same for PyMapping_Keys and PyMapping_Values.

----------
assignee: docs at python
components: Documentation
messages: 256727
nosy: docs at python, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Incorrect documentation for PyMapping_Items and like
type: behavior
versions: Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25909>
_______________________________________

From report at bugs.python.org  Sat Dec 19 08:09:04 2015
From: report at bugs.python.org (SilentGhost)
Date: Sat, 19 Dec 2015 13:09:04 +0000
Subject: [New-bugs-announce] [issue25910] Fixing links in documentation
Message-ID: <1450530544.1.0.9187941337.issue25910@psf.upfronthosting.co.za>


New submission from SilentGhost:

I've run 'make linkcheck' on Doc and it highlighted a number of faulty links in documentation. I've tried fixing some of them and here is the resulting patch. It's a bit too long and touches many files, so to summarise:

* Most changes are http->https redirect (many from wikipedia and microsoft, but some from independent project)
* New domains, sometimes without redirect or any indication of how to find the same information. 
* Completely new locations, only discoverable via search engine.
* Few dead links, that I removed.

I'm going to attach output.txt that is produced after running linkcheck with this patch applied, it is about three time smaller than the original one and has this types of issues:

* Dead links in licenses
* Internal redirects to versioned text
* Many python.org links in whatsnew/ that I don't know what to do about
* Spurious bad links

----------
assignee: docs at python
components: Documentation
files: linkcheck.diff
keywords: needs review, patch
messages: 256728
nosy: SilentGhost, docs at python, r.david.murray, zach.ware
priority: normal
severity: normal
stage: needs patch
status: open
title: Fixing links in documentation
versions: Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41361/linkcheck.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25910>
_______________________________________

From report at bugs.python.org  Sat Dec 19 10:39:38 2015
From: report at bugs.python.org (Bastien Montagne)
Date: Sat, 19 Dec 2015 15:39:38 +0000
Subject: [New-bugs-announce] [issue25911] Regression: os.walk now using
 os.scandir() breaks bytes filenames on windows
Message-ID: <1450539578.39.0.976654454489.issue25911@psf.upfronthosting.co.za>


New submission from Bastien Montagne:

In py3.4 and below we used to be able to use bytes filenames with os.walk(), it?s now impossible under windows due to the limitation of os.scandir().

This issue was reported to Blender tracker (https://developer.blender.org/T47018).

I assume this should be considered as a regression? At least, this should be mentioned in the documentation?

Thanks,
Bastien

----------
components: Library (Lib), Windows
messages: 256731
nosy: mont29, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Regression: os.walk now using os.scandir() breaks bytes filenames on windows
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25911>
_______________________________________

From report at bugs.python.org  Sat Dec 19 17:39:00 2015
From: report at bugs.python.org (Antony Lee)
Date: Sat, 19 Dec 2015 22:39:00 +0000
Subject: [New-bugs-announce] [issue25912] Use __spec__.__name__ instead of
 __name__ in the docs where appropriate
Message-ID: <1450564740.33.0.258115296695.issue25912@psf.upfronthosting.co.za>


New submission from Antony Lee:

There are a couple of places in the docs where it would be appropriate to replace __name__ by __spec__.__name__ in order to support the case where the module is executed as the __main__ module:

- logging.getLogger should certainly use __spec__.__name__ so that the logger hierarchy be respected (otherwise, when running "python -mpkg.subpkg", the logger of pkg.subpkg is named "__main__" and thus not a child of the "pkg" logger).

- examples for argparse.ArgumentParser (e.g. in the docs for venv) should use __spec__.__name__ instead of __name__ for the "prog=" argument.

(not guaranteed to be exhaustive)

----------
assignee: docs at python
components: Documentation
messages: 256743
nosy: Antony.Lee, docs at python
priority: normal
severity: normal
status: open
title: Use __spec__.__name__ instead of __name__ in the docs where appropriate
versions: Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25912>
_______________________________________

From report at bugs.python.org  Sat Dec 19 18:31:53 2015
From: report at bugs.python.org (Soren Solari)
Date: Sat, 19 Dec 2015 23:31:53 +0000
Subject: [New-bugs-announce] [issue25913] base64.a85decode adobe flag
 incorrectly utilizes <~ as a marker causing error
Message-ID: <1450567913.0.0.974183293511.issue25913@psf.upfronthosting.co.za>


New submission from Soren Solari:

According to the PDF Spec http://www.adobe.com/devnet/pdf/pdf_reference.html section 7.4.3,
The ascii85decode function only utilizes ~> as an EOD 2byte character, there is no mention of leading <~.   Therefore using the base64.a85decode(data, adobe=True) does not work on valid data coming from a pdf because that data may not have a leading <~.

Solution: do not require leading <~ for adobe=True.

----------
messages: 256745
nosy: Soren Solari
priority: normal
severity: normal
status: open
title: base64.a85decode adobe flag incorrectly utilizes <~ as a marker causing error
type: behavior
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25913>
_______________________________________

From report at bugs.python.org  Sun Dec 20 03:52:19 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 20 Dec 2015 08:52:19 +0000
Subject: [New-bugs-announce] [issue25914] Fix OrderedDict.__sizeof__
Message-ID: <1450601539.87.0.13067522237.issue25914@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Proposed patch correctly calculates the size of OrderedDict (the size of an instance dict should not be counted) and adds exact tests for sizeof.

----------
components: Extension Modules
files: odict_sizeof.patch
keywords: patch
messages: 256754
nosy: serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Fix OrderedDict.__sizeof__
type: behavior
versions: Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41367/odict_sizeof.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25914>
_______________________________________

From report at bugs.python.org  Sun Dec 20 04:44:25 2015
From: report at bugs.python.org (Adam Wasik)
Date: Sun, 20 Dec 2015 09:44:25 +0000
Subject: [New-bugs-announce] [issue25915] file.write() after file.read()
 adds text to the end of the file
Message-ID: <1450604665.98.0.726380429261.issue25915@psf.upfronthosting.co.za>


New submission from Adam Wasik:

>>> file = open(r"C:\adam.txt","r+")
>>> file.read()
'TEXT TEXT TEXT TEXT TEXT TEXT TEXT\nTEXT TEXT TEXT TEXT TEXT TEXT TEXT\nTEXT TE
XT TEXT TEXT TEXT TEXT TEXT\nTEXT TEXT TEXT TEXT TEXT TEXT TEXT\nTEXT TEXT TEXT
TEXT TEXT TEXT TEXT\nTEXT TEXT TEXT TEXT TEXT TEXT TEXT'
>>> file.seek(0,0)
0
>>> file.read(1)
'T'
>>> file.tell()
1
>>> file.write("NEW")
3
>>> file.tell() # Why 217 rather than 4. Text is added at the end file
217
>>>

----------
components: IO
messages: 256756
nosy: Adam Wasik
priority: normal
severity: normal
status: open
title: file.write() after file.read() adds text to the end of the file
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25915>
_______________________________________

From report at bugs.python.org  Sun Dec 20 05:31:11 2015
From: report at bugs.python.org (Iber Parodi Siri)
Date: Sun, 20 Dec 2015 10:31:11 +0000
Subject: [New-bugs-announce] [issue25916] wave module readframes now returns
 bytes not str
Message-ID: <1450607471.45.0.396609211559.issue25916@psf.upfronthosting.co.za>


New submission from Iber Parodi Siri:

The documentation of readframes (wave module) states that readframes returns a string of bytes, just like python 2.7, but that's not the case

in python 3.4 readframes returns byte type objects

----------
assignee: docs at python
components: Documentation
messages: 256759
nosy: Iber Parodi Siri, docs at python
priority: normal
severity: normal
status: open
title: wave module readframes now returns bytes not str
versions: Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25916>
_______________________________________

From report at bugs.python.org  Sun Dec 20 06:17:27 2015
From: report at bugs.python.org (SilentGhost)
Date: Sun, 20 Dec 2015 11:17:27 +0000
Subject: [New-bugs-announce] [issue25917] Fixing howto links in docs
Message-ID: <1450610247.39.0.486318634402.issue25917@psf.upfronthosting.co.za>


New submission from SilentGhost:

This patch changes links from wiki to howto part of docs.

----------
assignee: docs at python
components: Documentation
files: howto.diff
keywords: needs review, patch
messages: 256761
nosy: SilentGhost, docs at python
priority: normal
severity: normal
stage: patch review
status: open
title: Fixing howto links in docs
type: behavior
versions: Python 3.4, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41369/howto.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25917>
_______________________________________

From report at bugs.python.org  Mon Dec 21 05:02:07 2015
From: report at bugs.python.org (Marc Schlaich)
Date: Mon, 21 Dec 2015 10:02:07 +0000
Subject: [New-bugs-announce] [issue25918] AssertionError in lib2to3 on
 2.7.11 Windows
Message-ID: <1450692127.84.0.492153161721.issue25918@psf.upfronthosting.co.za>


New submission from Marc Schlaich:

This simple test case results in a lib2to3 crash with an AssertionError in 2.7.11


source = '''

class Test(object):

    tests = []


'''

from lib2to3.refactor import RefactoringTool


def main():
    tool = RefactoringTool([])
    tool.refactor_string(source, '')

        
Exception:

Traceback (most recent call last):
  File "test.py", line 21, in <module>
    main()
  File "test.py", line 16, in main
    tool.refactor_string(source, '')
  File "c:\Python27\Lib\lib2to3\refactor.py", line 380, in refactor_string
    name, err.__class__.__name__, err)
  File "c:\Python27\Lib\lib2to3\refactor.py", line 377, in refactor_string
    tree = self.driver.parse_string(data)
  File "c:\Python27\Lib\lib2to3\pgen2\driver.py", line 106, in parse_string
    return self.parse_tokens(tokens, debug)
  File "c:\Python27\Lib\lib2to3\pgen2\driver.py", line 71, in parse_tokens
    if p.addtoken(type, value, (prefix, start)):
  File "c:\Python27\Lib\lib2to3\pgen2\parse.py", line 127, in addtoken
    assert t < 256
AssertionError

Pretty weird: A manually built Python 2.7.11 with VS 2008 doesn't show this issue.

----------
components: 2to3 (2.x to 3.x conversion tool)
messages: 256790
nosy: schlamar
priority: normal
severity: normal
status: open
title: AssertionError in lib2to3 on 2.7.11 Windows
type: crash
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25918>
_______________________________________

From report at bugs.python.org  Mon Dec 21 15:20:23 2015
From: report at bugs.python.org (Wiktor Niesiobedzki)
Date: Mon, 21 Dec 2015 20:20:23 +0000
Subject: [New-bugs-announce] [issue25919] htp.client PUT method ignores
 error responses sent immediatly after headers
Message-ID: <1450729223.96.0.301570875049.issue25919@psf.upfronthosting.co.za>


New submission from Wiktor Niesiobedzki:

It looks like, when doing PUT together with a file-like object to send, http.client will try to send the whole file before analysing the response from the server.

If you do the following:
$ dd if=/dev/zero of=/tmp/300mb.zero bs=1M count=300

And then run following code in Python 3.4 (tested 3.4.3 on Linux and FreeBSD):
import http.client
conn = http.client.HTTPSConnection('api.onedrive.com')
req = conn.request(
    method='PUT',
    url='https://api.onedrive.com/v1.0/drives/me/root:/test.file:/content',
    body=open("/tmp/300mb.zero", "rb"))
resp = conn.getresponse()

You'll notice the hang. After some time, it will aborted with BrokenPipeError: [Errno 32] Broken pipe. If you run the following code within pdb debugger, and interrupt, you'll probably interrupt somewhere within write loop. You can call self.read() and see, that HTTP 413 is waiting to be interpreted.

Doing similar action with curl:
$ $ curl -v -T /tmp/300mb.zero https://api.onedrive.com/v1.0/drives/me/root:/test.file:/content

Gives you immediate HTTP 413 error. Can we have the same behaviour in http.client library?

----------
components: IO
messages: 256808
nosy: Wiktor Niesiobedzki
priority: normal
severity: normal
status: open
title: htp.client PUT method ignores error responses sent immediatly after headers
type: behavior
versions: Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25919>
_______________________________________

From report at bugs.python.org  Mon Dec 21 18:19:32 2015
From: report at bugs.python.org (A. Jesse Jiryu Davis)
Date: Mon, 21 Dec 2015 23:19:32 +0000
Subject: [New-bugs-announce] [issue25920] PyOS_AfterFork should reset
 socketmodule's lock
Message-ID: <1450739972.22.0.163393011494.issue25920@psf.upfronthosting.co.za>


New submission from A. Jesse Jiryu Davis:

On some platforms there's an exclusive lock in socketmodule, used for getaddrinfo, gethostbyname, gethostbyaddr. A thread can hold this lock while another forks, leaving it locked forever in the child process. Calls to these functions in the child process will hang.

(I wrote some more details here: https://emptysqua.re/blog/getaddrinfo-deadlock/ )

I propose that this is a bug, and that it can be fixed in PyOS_AfterFork, where a few similar locks are already reset.

----------
messages: 256815
nosy: emptysquare
priority: normal
severity: normal
status: open
title: PyOS_AfterFork should reset socketmodule's lock

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25920>
_______________________________________

From report at bugs.python.org  Mon Dec 21 22:38:54 2015
From: report at bugs.python.org (Mark Hammond)
Date: Tue, 22 Dec 2015 03:38:54 +0000
Subject: [New-bugs-announce] [issue25921] project files for
 wininst-14.0*.exe don't exist
Message-ID: <1450755534.72.0.715551083483.issue25921@psf.upfronthosting.co.za>


New submission from Mark Hammond:

Revision 34b35aa1967d pushed new versions of wininst-14.8*.exe, but didn't include the VS project files required to build it, thus meaning it can't reasonably be built from the source tree.

----------
components: Build
messages: 256823
nosy: mhammond, steve.dower
priority: normal
severity: normal
status: open
title: project files for wininst-14.0*.exe don't exist

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25921>
_______________________________________

From report at bugs.python.org  Tue Dec 22 01:49:05 2015
From: report at bugs.python.org (Kyle S (MrStonedOne))
Date: Tue, 22 Dec 2015 06:49:05 +0000
Subject: [New-bugs-announce] [issue25922] canceling a repair install breaks
 the ability to uninstall repair or re-install
Message-ID: <1450766945.03.0.168285757659.issue25922@psf.upfronthosting.co.za>


New submission from Kyle S (MrStonedOne):

Title says all.

It refuses to install from that point on, complaining that a reboot is needed.

----------
components: Installation, Windows
messages: 256829
nosy: Kyle S (MrStonedOne), paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: canceling a repair install breaks the ability to uninstall repair or re-install
type: behavior
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25922>
_______________________________________

From report at bugs.python.org  Tue Dec 22 07:56:32 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 22 Dec 2015 12:56:32 +0000
Subject: [New-bugs-announce] [issue25923] More const char
Message-ID: <1450788992.05.0.185149174407.issue25923@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Proposed patch adds the const qualifier to char* parameter declarations and static char arrays if appropriate. This makes the code more strict and can help to catch bugs or generate more efficient code. In additional it can decrease memory consumption by avoiding copying constant data.

----------
assignee: serhiy.storchaka
components: Extension Modules, Interpreter Core
files: const_char_ptr.patch
keywords: patch
messages: 256837
nosy: serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: More const char
type: enhancement
versions: Python 3.6
Added file: http://bugs.python.org/file41384/const_char_ptr.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25923>
_______________________________________

From report at bugs.python.org  Tue Dec 22 07:57:10 2015
From: report at bugs.python.org (Ronald Oussoren)
Date: Tue, 22 Dec 2015 12:57:10 +0000
Subject: [New-bugs-announce] [issue25924] investigate if getaddrinfo(3) on
 OSX is thread-safe
Message-ID: <1450789030.99.0.515103781608.issue25924@psf.upfronthosting.co.za>


New submission from Ronald Oussoren:

https://emptysqua.re/blog/getaddrinfo-deadlock/ claims that getaddrinfo may deadlock when using threads and fork on (amongst others) OSX due to using a global lock.

That lock is used when getaddrinfo is believed to be not thread safe, see the relevant code below (from the blog post):

/* On systems on which getaddrinfo() is believed to not be thread-safe,
   (this includes the getaddrinfo emulation) protect access with a lock. */
#if defined(WITH_THREAD) && (defined(__APPLE__) || \
    (defined(__FreeBSD__) && __FreeBSD_version+0 < 503000) || \
    defined(__OpenBSD__) || defined(__NetBSD__) || \
    defined(__VMS) || !defined(HAVE_GETADDRINFO))
#define USE_GETADDRINFO_LOCK
#endif

I think it is worthwhile to investigate whether or not getaddrinfo on OSX is really not thread safe. 

Some source code for OSX can be found at the link below, I haven't checked yet which OSX release this corresponds to:

http://www.opensource.apple.com/source/Libinfo/Libinfo-278/lookup.subproj/getaddrinfo.c

----------
assignee: ronaldoussoren
components: Macintosh
messages: 256838
nosy: ned.deily, ronaldoussoren
priority: low
severity: normal
status: open
title: investigate if getaddrinfo(3) on OSX is thread-safe
type: enhancement
versions: Python 2.7, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25924>
_______________________________________

From report at bugs.python.org  Tue Dec 22 09:08:00 2015
From: report at bugs.python.org (Alecsandru Patrascu)
Date: Tue, 22 Dec 2015 14:08:00 +0000
Subject: [New-bugs-announce] [issue25925] Coverage support for CPython 2
Message-ID: <1450793280.08.0.219488007546.issue25925@psf.upfronthosting.co.za>


New submission from Alecsandru Patrascu:

Hi All,

This is Alecsandru from Server Scripting Languages Optimization team at Intel Corporation. I would like to submit a patch that adds extended support for coverage, in the same way that it is used in CPython3. Used in conjunction with the regrtests, it provides a broader view of the hot and cold zones in the interpreter.

Thank you,
Alecsandru

----------
components: Build
files: coverage-2.7-v01.patch
keywords: patch
messages: 256839
nosy: alecsandru.patrascu
priority: normal
severity: normal
status: open
title: Coverage support for CPython 2
type: enhancement
versions: Python 2.7
Added file: http://bugs.python.org/file41385/coverage-2.7-v01.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25925>
_______________________________________

From report at bugs.python.org  Tue Dec 22 12:40:36 2015
From: report at bugs.python.org (Thomas Feldmann)
Date: Tue, 22 Dec 2015 17:40:36 +0000
Subject: [New-bugs-announce] [issue25926] problems with "times" keyword in
 itertools.repeat
Message-ID: <1450806036.21.0.954073881918.issue25926@psf.upfronthosting.co.za>


New submission from Thomas Feldmann:

According to the docs `itertools.repeat(object[, times])` is equivalent to

```
def repeat(object, times=None):
    # repeat(10, 3) --> 10 10 10
    if times is None:
        while True:
            yield object
    else:
        for i in range(times):
            yield object
```

But it raises a TypeError when used this way:

```
Python 3.5.1 (default, Dec 10 2015, 10:34:07)
[GCC 4.2.1 Compatible Apple LLVM 7.0.0 (clang-700.1.76)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from itertools import repeat
>>> repeat('x', times=None)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: 'NoneType' object cannot be interpreted as an integer
```

The `times` keyword can be omitted but not explicitly set to None.
I checked with Python Versions 2.7 and 3.5.1 on Mac OS X and Windows 10.

----------
components: Interpreter Core
messages: 256847
nosy: Thomas Feldmann
priority: normal
severity: normal
status: open
title: problems with "times" keyword in itertools.repeat
type: behavior
versions: Python 2.7, Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25926>
_______________________________________

From report at bugs.python.org  Tue Dec 22 14:57:01 2015
From: report at bugs.python.org (=?utf-8?b?0JzQsNGA0Log0JrQvtGA0LXQvdCx0LXRgNCz?=)
Date: Tue, 22 Dec 2015 19:57:01 +0000
Subject: [New-bugs-announce] [issue25927] add dir_fd for mkstemp,
 and also maybe to all tempfile.*
Message-ID: <1450814221.93.0.811115775086.issue25927@psf.upfronthosting.co.za>


New submission from ???? ?????????:

dir_fd support is good in `os` module. but tempfile module lack support of that great feature. Please add.

----------
messages: 256856
nosy: mmarkk
priority: normal
severity: normal
status: open
title: add dir_fd for mkstemp, and also maybe to all tempfile.*
versions: Python 3.3, Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25927>
_______________________________________

From report at bugs.python.org  Tue Dec 22 17:18:25 2015
From: report at bugs.python.org (John Walker)
Date: Tue, 22 Dec 2015 22:18:25 +0000
Subject: [New-bugs-announce] [issue25928] Improve performance of
 statistics._decimal_to_ratio and fractions.from_decimal
Message-ID: <1450822705.24.0.946819992184.issue25928@psf.upfronthosting.co.za>


New submission from John Walker:

In statistics, there is a FIXME on Line 250 above _decimal_to_ratio that says:

# FIXME This is faster than Fraction.from_decimal, but still too slow.

Half of the time is spent in a conversion in d.as_tuple(). Decimal internally stores the digits as a string, but in d.as_tuple(), the digits are individually cast to integers and returned as a tuple of integers.

This is OK, but _decimal_to_ratio undoes the work that was done in d.as_tuple() by adding them all back into an integer. A similar, but slightly different approach is taken in Fractions.from_decimal, where the tuple is cast into a string and then parsed into an integer. We can be a lot faster if we use the _int instance variable directly.

In the case of _decimal_to_ratio, the new code seems to be twice as fast with usage _decimal_to_ratio(Decimal(str(random.random()))):


def _decimal_to_ratio(d):
    sign, exp = d._sign, d._exp
    if exp in ('F', 'n', 'N'):  # INF, NAN, sNAN
        assert not d.is_finite()
        return (d, None)
    num = int(d._int)
    if exp < 0:
        den = 10**-exp
    else:
        num *= 10**exp
        den = 1
    if sign:
        num = -num
    return (num, den)

If the performance improvement is considered worthwhile, here are a few solutions I see.

1) Use _int directly in fractions and statistics.

2) Add a digits_as_str method to Decimal. This prevents exposing _int as an implementation detail, and makes sense to me since I suspect there is a lot of code casting the tuple of int to a string anyway. 

3) Add a parameter to as_tuple for determining whether digits should be returned as a string or a tuple.

4) Deprecate _int in Decimal and add a new reference str_digits.

There are probably more solutions. I lean towards 4, because it makes usage easier and avoids cluttering Decimal with methods. 

Here is what I used for benchmarks:

========

import timeit

old_setup = """
import random
from decimal import Decimal

def _decimal_to_ratio(d):
    sign, digits, exp = d.as_tuple()
    if exp in ('F', 'n', 'N'):  # INF, NAN, sNAN
        assert not d.is_finite()
        return (d, None)
    num = 0
    for digit in digits:
        num = num*10 + digit
    if exp < 0:
        den = 10**-exp
    else:
        num *= 10**exp
        den = 1
    if sign:
        num = -num
    return (num, den)

def run_it():
    dec = Decimal(str(random.random()))
    _decimal_to_ratio(dec)
"""

new_setup = """
import random
from decimal import Decimal

def _decimal_to_ratio(d):
    sign, exp = d._sign, d._exp
    if exp in ('F', 'n', 'N'):  # INF, NAN, sNAN
        assert not d.is_finite()
        return (d, None)
    num = int(d._int)
    if exp < 0:
        den = 10**-exp
    else:
        num *= 10**exp
        den = 1
    if sign:
        num = -num
    return (num, den)

def run_it():
    dec = Decimal(str(random.random()))
    _decimal_to_ratio(dec)
"""

if __name__ == '__main__':
    print("Testing proposed implementation")
    print("number = 10000")
    print(timeit.Timer(stmt='run_it()', setup=new_setup).timeit(number=10000))
    print("number = 100000")         
    print(timeit.Timer(stmt='run_it()', setup=new_setup).timeit(number=100000))
    print("number = 1000000")     
    print(timeit.Timer(stmt='run_it()', setup=new_setup).timeit(number=1000000))

    print("Testing old implementation")
    print("number = 10000")
    print(timeit.Timer(stmt='run_it()', setup=old_setup).timeit(number=10000))
    print("number = 100000")         
    print(timeit.Timer(stmt='run_it()', setup=old_setup).timeit(number=100000))
    print("number = 1000000")     
    print(timeit.Timer(stmt='run_it()', setup=old_setup).timeit(number=1000000))

----------
components: Library (Lib)
messages: 256873
nosy: johnwalker
priority: normal
severity: normal
status: open
title: Improve performance of statistics._decimal_to_ratio and fractions.from_decimal
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25928>
_______________________________________

From report at bugs.python.org  Tue Dec 22 17:55:10 2015
From: report at bugs.python.org (Mark Cline)
Date: Tue, 22 Dec 2015 22:55:10 +0000
Subject: [New-bugs-announce] [issue25929] When doing string.replace,
 it uses the entire 'find' string and doesn't let it get reused...
Message-ID: <1450824910.44.0.997186762869.issue25929@psf.upfronthosting.co.za>


New submission from Mark Cline:

The Title might be a bit awkward but this is what I mean:

before = ',,,,'
after = before.replace(',,', ',null,')
print(after)
>,null,,null,

I suspect it is starting the second search at the start of the first find + length of the find? ie:
,,,,
0123
Starting the next search at spot 2 (the 3rd ,).

This might be expected behaviour as it is looking at the rest of the string after finding the match, as opposed to taking the updated string:
,null,,, after the first replace. (Actually, writing that out it does make sense that it would behave like this, but thought I would mention just in case I am missing something). 

[Its easy enough to work around it, but just thought I would mention it :D]

----------
components: Library (Lib)
messages: 256877
nosy: Mark Cline
priority: normal
severity: normal
status: open
title: When doing string.replace, it uses the entire 'find' string and doesn't let it get reused...
type: behavior
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25929>
_______________________________________

From report at bugs.python.org  Tue Dec 22 18:10:45 2015
From: report at bugs.python.org (Anthony Sottile)
Date: Tue, 22 Dec 2015 23:10:45 +0000
Subject: [New-bugs-announce] [issue25930] os.unlink != os.remove in python3.5
Message-ID: <1450825845.31.0.1486283683.issue25930@psf.upfronthosting.co.za>


New submission from Anthony Sottile:

I've confirmed this bug is present on both windows and linux, the outputs below are from linux however.

Compare:

```
$ python3.4 --version
Python 3.4.3
$ python3.4 -c 'import os; print(os.unlink == os.remove)'
True
```

```
$ python3.5 --version
Python 3.5.0
$ python3.5 -c 'import os; print(os.unlink == os.remove)'
False
```

The docs say: https://docs.python.org/3/library/os.html#os.remove

"This function is identical to unlink()."

To me identity means `is` but I at least expect the `==` behaviour of previous versions.

----------
messages: 256880
nosy: Anthony Sottile
priority: normal
severity: normal
status: open
title: os.unlink != os.remove in python3.5
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25930>
_______________________________________

From report at bugs.python.org  Tue Dec 22 22:10:31 2015
From: report at bugs.python.org (Sam Lobel)
Date: Wed, 23 Dec 2015 03:10:31 +0000
Subject: [New-bugs-announce] [issue25931] os.fork() command distributed in
 windows Python27 (in SocketServer module)
Message-ID: <1450840231.57.0.83917358919.issue25931@psf.upfronthosting.co.za>


New submission from Sam Lobel:

I ran into this bug while using multiprocessing in Flask, which deep down uses the SocketServer.py module.

There's a call to os.fork() in the windows version , which obviously doesn't work. So SocketServer.py can't be used on windows.

Maybe replace it with something from the multiprocessing module?

----------
components: Windows
messages: 256896
nosy: Sam Lobel, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: os.fork() command distributed in windows Python27 (in SocketServer module)
type: behavior
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25931>
_______________________________________

From report at bugs.python.org  Wed Dec 23 10:38:03 2015
From: report at bugs.python.org (Ismail Donmez)
Date: Wed, 23 Dec 2015 15:38:03 +0000
Subject: [New-bugs-announce] [issue25932] Windows installer ships an
 outdated and insecure curl.exe
Message-ID: <1450885083.97.0.29185685319.issue25932@psf.upfronthosting.co.za>


New submission from Ismail Donmez:

Installed Python 3.5.1 windows x64 version and ended up having

C:\Users\ismail\AppData\Local\Programs\Python\Python35\curl.exe

which is outdated:

C:\Users\ismail>C:\Users\ismail\AppData\Local\Programs\Python\Python35\curl.exe -V
curl 7.37.0 (Windows) libcurl/7.37.0 OpenSSL/1.0.2d zlib/1.2.8
Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp smtp smtps telnet tftp
Features: NTLM SSL libz

That is released in May 2014!

Also its insecure:

C:\Users\ismail>C:\Users\ismail\AppData\Local\Programs\Python\Python35\curl.exe -vvvv "https://www.g
oogle.com"
* Rebuilt URL to: https://www.google.com/
* timeout on name lookup is not supported
* Hostname was NOT found in DNS cache
*   Trying 173.194.32.177...
* Connected to www.google.com (173.194.32.177) port 443 (#0)
* libcurl is now using a weak random seed!
[...]

I would be happy if you don't ship curl at all, or at least use a secure, up-to-date version from https://bintray.com/vszakats/generic/curl/view

----------
components: Windows
messages: 256918
nosy: donmez, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Windows installer ships an outdated and insecure curl.exe
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25932>
_______________________________________

From report at bugs.python.org  Wed Dec 23 14:38:46 2015
From: report at bugs.python.org (Sam Adams)
Date: Wed, 23 Dec 2015 19:38:46 +0000
Subject: [New-bugs-announce] [issue25933] Unhandled exception (TypeError)
 with ftplib in function retrbinary/retrlines causes inoperable behavior
 without crashing
Message-ID: <1450899526.91.0.95420964187.issue25933@psf.upfronthosting.co.za>


New submission from Sam Adams:

Hello,

I believe that I found a bug in ftplib.py in version 3.3.6.

Whenever a user opens a file for writing in nonbinary mode and then proceeds to call the retrbinary function, or opens the file in binary mode and proceeds to call the retrlines fuction, then attempts to write to the file using the callback function, an unhandled TypeError exception is raised that does not cause the program to crash, but rather cause the last message from the server to not be "read" by the readline() function, thus causing cascading errors until the function readline() is called on its own or the connection with the server is reset.

Code to replicate:
from ftplib import FTP
ftp = FTP('your.server.here')
ftp.login()
fileTest = open('filename','w') <---- not binary
ftp.retrbinary('retr randomfilehere',fileTest.write)

Unhandled exception raised: 

File "/usr/local/lib/python3.3/ftplib.py", line 434, in retrbinary
    callback(data)
TypeError: must be str, not bytes

Likewise, if 

ftp.retrlines('retr randomfilehere', fileTest.write) 

is called when fileTest is opened for writing with binary option the following error is raised:

File "/usr/local/lib/python3.3/ftplib.py", line 464, in retrlines
    callback(line)
TypeError: 'str' does not support the buffer interface

Calling ftp.getline() clears the error and resumes normal operation


Possible Solution:

add exception handling in lines 434/464 for TypeError

----------
components: Library (Lib)
messages: 256927
nosy: Sam Adams
priority: normal
severity: normal
status: open
title: Unhandled exception (TypeError) with ftplib in function retrbinary/retrlines causes inoperable behavior without crashing
versions: Python 3.3

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25933>
_______________________________________

From report at bugs.python.org  Wed Dec 23 18:02:23 2015
From: report at bugs.python.org (Stefan Krah)
Date: Wed, 23 Dec 2015 23:02:23 +0000
Subject: [New-bugs-announce] [issue25934] ICC compiler: ICC treats denormal
 floating point numbers as 0.0
Message-ID: <1450911743.93.0.393041043786.issue25934@psf.upfronthosting.co.za>


New submission from Stefan Krah:

Zachary in #24999:

"If that's the case, would anyone (in particular, Steve, Tim or Tim) mind if we just made the default (for MSVC as well as ICC) /fp:strict?  It would be much easier to just change the global default than to try to either make it settable or to change it just when ICC is used."

----------
messages: 256943
nosy: haypo, mark.dickinson, paul.moore, pitrou, python-dev, r.david.murray, serhiy.storchaka, skrah, steve.dower, tim.golden, tim.peters, zach.ware
priority: normal
severity: normal
status: open
title: ICC compiler: ICC treats denormal floating point numbers as 0.0

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25934>
_______________________________________

From report at bugs.python.org  Wed Dec 23 18:39:59 2015
From: report at bugs.python.org (Simon Charette)
Date: Wed, 23 Dec 2015 23:39:59 +0000
Subject: [New-bugs-announce] [issue25935] OrderedDict prevents garbage
 collection if a circulary referenced class is used as key
Message-ID: <1450913999.27.0.791224065959.issue25935@psf.upfronthosting.co.za>


New submission from Simon Charette:

I attached a file with a reproduction test case that passes on Python 2.7 and 3.4 but fails on 3.5.0 and 3.5.1

This might be solved by the improvement planed in #25410.

----------
components: Extension Modules
files: test.py
messages: 256945
nosy: charettes
priority: normal
severity: normal
status: open
title: OrderedDict prevents garbage collection if a circulary referenced class is used as key
type: behavior
versions: Python 3.5
Added file: http://bugs.python.org/file41399/test.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25935>
_______________________________________

From report at bugs.python.org  Wed Dec 23 18:58:04 2015
From: report at bugs.python.org (WGH)
Date: Wed, 23 Dec 2015 23:58:04 +0000
Subject: [New-bugs-announce] [issue25936] Improve FastChildWatcher with
 WNOWAIT?
Message-ID: <1450915084.71.0.0403094885095.issue25936@psf.upfronthosting.co.za>


New submission from WGH:

The problem with FastChildWatcher lies in the fact that it can accidentally reap processes that it doesn't watch.

However, os module includes waitid function (since Python 3.3), and it has WNOWAIT flags, which means "return status, let process remain waitable (=don't reap)".

What do you think, can this feature fix the problem with FastChildWatcher?

----------
components: asyncio
messages: 256946
nosy: WGH, gvanrossum, haypo, yselivanov
priority: normal
severity: normal
status: open
title: Improve FastChildWatcher with WNOWAIT?

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25936>
_______________________________________

From report at bugs.python.org  Wed Dec 23 22:49:49 2015
From: report at bugs.python.org (=?utf-8?b?546L5p2w?=)
Date: Thu, 24 Dec 2015 03:49:49 +0000
Subject: [New-bugs-announce] [issue25937] DIfference between utf8 and utf-8
 when i define python source code encoding.
Message-ID: <1450928989.2.0.861306801503.issue25937@psf.upfronthosting.co.za>


New submission from ??:

I use CentOS 7.0 and change LANG=gbk.

I has a file "gbk-utf-8.py" and it's encoding is GBK.

# -*- coding:utf-8 -*-
import chardet
if __name__ == '__main__':
    s = '??'
    print s, chardet.detect(s) 

I execute it and everything is ok. However it raise "SyntaxError" (as I expected) after I change "encoding:utf-8" to "encoding:utf8".

  File "gbk-utf8.py", line 2
SyntaxError: 'utf8' codec can't decode byte 0xd6 in position 0: invalid continuation byte

Is this ok? Or where I wrong?

----------
messages: 256952
nosy: ??
priority: normal
severity: normal
status: open
title: DIfference between utf8 and utf-8 when i define python source code encoding.

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25937>
_______________________________________

From report at bugs.python.org  Thu Dec 24 01:58:51 2015
From: report at bugs.python.org (Kozo Oeda)
Date: Thu, 24 Dec 2015 06:58:51 +0000
Subject: [New-bugs-announce] [issue25938] if sentence doesn't work with
 input()
Message-ID: <1450940331.94.0.479446951644.issue25938@psf.upfronthosting.co.za>


New submission from Kozo Oeda:

if sentence doesn't work well with input() in Python 3(I confirmed 3.4.3 and 3.5.1 on OS X 10.10.5). I also confirmed Python 2.7.11 works well. I think the code which I wrote in the lower section explains what happened enough. 

I couldn't get the proper component so I selected Interpreter Core temporally.
Thanks 

#============Code Start=================
#Python 3.4.3 and 3.5.1 on OS X 10.10.5

def test(a):
	if a == 0:
		print("0")
	else:
		print("not 0")

a = input()
print(a)
test(a)

# Input 
# 0 
#
# Output
# 0
# 0
# not 0

# Input
# 1
#
# Output
# 1
# 1
# not 0
#============Code End=================

----------
components: Interpreter Core
messages: 256954
nosy: kozmof
priority: normal
severity: normal
status: open
title: if sentence doesn't work with input()
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25938>
_______________________________________

From report at bugs.python.org  Thu Dec 24 15:40:28 2015
From: report at bugs.python.org (Chi Hsuan Yen)
Date: Thu, 24 Dec 2015 20:40:28 +0000
Subject: [New-bugs-announce] [issue25939] _ssl.enum_certificates() fails
 with ERROR_ACCESS_DENIED if python.exe run with low integrity level
Message-ID: <1450989628.26.0.849835515988.issue25939@psf.upfronthosting.co.za>


New submission from Chi Hsuan Yen:

Originally reported at https://github.com/rg3/youtube-dl/issues/7951

Steps to reproduce:
1. Build 99665:dcf9e9ae5393 with Visual Studio 2015
2. Download and extract PsTools [1]
3. PsExec.exe -l python.exe
4. In Python, run:

    import _ssl
    _ssl.enum_certificates("CA")
    _ssl.enum_crls("CA")

Results:
Python 3.6.0a0 (default, Dec 25 2015, 02:42:42) [MSC v.1900 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import _ssl
>>> _ssl.enum_certificates("CA")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
PermissionError: [WinError 5] Access is denied
>>> _ssl.enum_crls("CA")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
PermissionError: [WinError 5] Access is denied
>>>

Windows Vista and above have a security mechanism called "Low Integrity Level". [2] With that, only some specific registry keys are writable. In the original _ssl.c, both enum_certificates() and enum_crls() calls CertOpenSystemStore(). At least on my system CertOpenSystemStore() tries to open HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\CA with read/write permissions. (Observed with Process Monitor [3]) The request fails in Low Integrity Level processes as it's not in the range of writable registry keys.

Here I propose a fix: open certificate stores with the read-only flag. There are some points I'm not sure in this patch:
1. CERT_STORE_PROV_SYSTEM_A: I guess strings are bytestrings in C level?
2. CERT_SYSTEM_STORE_LOCAL_MACHINE: In accounts of Administrators, CertOpenSystemStore() tries to open keys under HKLM only, while in restricted (standard) accounts, this function tries to open keys under HKCU with R/W permission and keys under HKLM read-only. I think open system global stores is OK here.
A different perspective: Wine developers always open keys under HKCU in CertOpenSystemStore()

Environment: Windows 7 SP1 (6.1.7601) x86, an account in Administrators group. Tested with python.exe Lib\test\test_ssl.py both in a normal shell and within `PsExec -l`

Ref: issue17134, where these codes appear the first time

[1] https://technet.microsoft.com/en-us/sysinternals/pstools.aspx
[2] https://msdn.microsoft.com/en-us/library/bb625960.aspx
[3] https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx
[4] https://github.com/wine-mirror/wine/blob/master/dlls/crypt32/store.c

----------
components: Extension Modules, Windows
files: open-system-store-readonly.patch
keywords: patch
messages: 256968
nosy: Chi Hsuan Yen, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: _ssl.enum_certificates() fails with ERROR_ACCESS_DENIED if python.exe run with low integrity level
type: crash
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41405/open-system-store-readonly.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25939>
_______________________________________

From report at bugs.python.org  Thu Dec 24 15:47:46 2015
From: report at bugs.python.org (Chi Hsuan Yen)
Date: Thu, 24 Dec 2015 20:47:46 +0000
Subject: [New-bugs-announce] [issue25940] SSL tests failed due to expired
 svn.python.org SSL certificate
Message-ID: <1450990066.48.0.77725045299.issue25940@psf.upfronthosting.co.za>


New submission from Chi Hsuan Yen:

The certificate of svn.python.org expires at Thu 24 Dec 2015 08:28:32 PM CST GMT, about 20 minutes ago. Please update its certificate or lots of tests in Lib\test\test_ssl.py fails with SSL: CERTIFICATE_VERIFY_FAILED.

----------
components: Tests
messages: 256969
nosy: Chi Hsuan Yen
priority: normal
severity: normal
status: open
title: SSL tests failed due to expired svn.python.org SSL certificate
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25940>
_______________________________________

From report at bugs.python.org  Thu Dec 24 16:20:57 2015
From: report at bugs.python.org (Camilla Montonen)
Date: Thu, 24 Dec 2015 21:20:57 +0000
Subject: [New-bugs-announce] [issue25941] Add 'How to Review a Patch'
 section to devguide
Message-ID: <1450992057.28.0.358724589512.issue25941@psf.upfronthosting.co.za>


New submission from Camilla Montonen:

This list is based on helpful tips and discussions received on the core-mentorship list and aims to help new beginners review patches in the bug tracker. The submitted patch is still in progress (the layout is a bit wonky and some details are still missing).

----------
components: Devguide
files: patchreview.patch
keywords: patch
messages: 256970
nosy: Winterflower, ezio.melotti, willingc
priority: normal
severity: normal
status: open
title: Add 'How to Review a Patch' section to devguide
Added file: http://bugs.python.org/file41406/patchreview.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25941>
_______________________________________

From report at bugs.python.org  Thu Dec 24 20:15:08 2015
From: report at bugs.python.org (Mike Pomraning)
Date: Fri, 25 Dec 2015 01:15:08 +0000
Subject: [New-bugs-announce] [issue25942] subprocess.call SIGKILLs too
 liberally
Message-ID: <1451006108.23.0.113868196098.issue25942@psf.upfronthosting.co.za>


New submission from Mike Pomraning:

Python 3.3 introduces timeout support in subprocess.call, implemented by sending a SIGKILL if the Popen.wait is interrupted by a TimeoutExpired exception.

However, the "except" clause is too broad, and will, for instance, trigger on a KeyboardInterrupt.  For practical purposes, this means that sending a Ctrl-C to a python program before 3.3 sent a SIGINT to both the parent and subprocess.call()d child, whereas under 3.3+ sends a SIGINT _and_ a SIGKILL to the child.  The child will not be able to clean up appropriately.

For a real world example of this, see http://stackoverflow.com/q/34458583/132382

The fix is, I think, simply changing the clause to "except TimeoutExpired".  At least, that works for me.  See attached patch.

----------
components: Library (Lib)
files: subprocess-call-py344-kill-only-on-timeout.patch
keywords: patch
messages: 256973
nosy: Mike Pomraning
priority: normal
severity: normal
status: open
title: subprocess.call SIGKILLs too liberally
type: behavior
versions: Python 3.3
Added file: http://bugs.python.org/file41407/subprocess-call-py344-kill-only-on-timeout.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25942>
_______________________________________

From report at bugs.python.org  Thu Dec 24 22:53:35 2015
From: report at bugs.python.org (Ned Williamson)
Date: Fri, 25 Dec 2015 03:53:35 +0000
Subject: [New-bugs-announce] [issue25943] Integer overflow in _bsddb leads
 to heap corruption
Message-ID: <1451015615.68.0.324504050935.issue25943@psf.upfronthosting.co.za>


New submission from Ned Williamson:

In function `_db_associateCallback` of the `_bsddb` module, associating two databases with a callback that returns a sufficiently large list will lead to heap corruption due an integer overflow on 32-bit Python.

>From `_bsddb.c`:
```
    else if (PyList_Check(result))
    {
        char* data;
        Py_ssize_t size;
        int i, listlen;
        DBT* dbts;

        listlen = PyList_Size(result);

1.      dbts = (DBT *)malloc(sizeof(DBT) * listlen); ///sizeof(DBT) == 28 on my system, enough to overflow

2.      for (i=0; i<listlen; i++)
        {
            if (!PyBytes_Check(PyList_GetItem(result, i)))
            {
                PyErr_SetString(
                   PyExc_TypeError,
#if (PY_VERSION_HEX < 0x03000000)
"The list returned by DB->associate callback should be a list of strings.");
#else
"The list returned by DB->associate callback should be a list of bytes.");
#endif
                PyErr_Print();
            }

            PyBytes_AsStringAndSize(
                PyList_GetItem(result, i),
3.              &data, &size);

            CLEAR_DBT(dbts[i]);
4.          dbts[i].data = malloc(size);          /* TODO, check this */

            if (dbts[i].data)
            {
5.              memcpy(dbts[i].data, data, size);
                dbts[i].size = size;
                dbts[i].ulen = dbts[i].size;
                dbts[i].flags = DB_DBT_APPMALLOC;  /* DB will free */
            }
            else
            {
                PyErr_SetString(PyExc_MemoryError,
                    "malloc failed in _db_associateCallback (list)");
                PyErr_Print();
            }
        }

        CLEAR_DBT(*secKey);

        secKey->data = dbts;
        secKey->size = listlen;
        secKey->flags = DB_DBT_APPMALLOC | DB_DBT_MULTIPLE;
        retval = 0;
    }
```

1. The multiplication in this line can overflow, allocating an undersized buffer.
2. This loop does not suffer from the overflow, so it can corrupt the heap by writing user data (see 3. and 5.).

This bug is present in Python 2.7.11.

See the result of running my attached POC script:
```
(gdb) r vuln.py
Starting program: /vagrant/Python-2.7.11/python.exe vuln.py
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
python.exe: malloc.c:2372: sysmalloc: Assertion `(old_top == (((mbinptr) (((char *) &((av)->bins[((1) - 1) * 2])) - __builtin_offsetof (struct malloc_chunk, fd)))) && old_size == 0) || ((unsigned long) (old_size) >= (unsigned long)((((__builtin_offsetof (struct malloc_chunk, fd_nextsize))+((2 *(sizeof(size_t))) - 1)) & ~((2 *(sizeof(size_t))) - 1))) && ((old_top)->size & 0x1) && ((unsigned long) old_end & pagemask) == 0)' failed.

Program received signal SIGABRT, Aborted.
0xb7fdd428 in __kernel_vsyscall ()
(gdb) bt
#0  0xb7fdd428 in __kernel_vsyscall ()
#1  0xb7de6607 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#2  0xb7de9a33 in __GI_abort () at abort.c:89
#3  0xb7e2a9dd in __malloc_assert (
    assertion=assertion at entry=0xb7f1e3c0 "(old_top == (((mbinptr) (((char *) &((av)->bins[((1) - 1) * 2])) - __builtin_offsetof (struct malloc_chunk, fd)))) && old_size == 0) || ((unsigned long) (old_size) >= (unsigned long)((((__builtin_offs"...,
    file=file at entry=0xb7f19954 "malloc.c", line=line at entry=2372,
    function=function at entry=0xb7f19ce5 <__func__.10915> "sysmalloc") at malloc.c:293
#4  0xb7e2d5eb in sysmalloc (av=0xb7f62420 <main_arena>, nb=16) at malloc.c:2369
#5  _int_malloc (av=av at entry=0xb7f62420 <main_arena>, bytes=bytes at entry=1) at malloc.c:3800
#6  0xb7e2e708 in __GI___libc_malloc (bytes=1) at malloc.c:2891
#7  0xb7b006b2 in _db_associateCallback (db=0x82a7dd0, priKey=0xbffff228, priData=0xbffff034, secKey=0x8291a80)
    at /vagrant/Python-2.7.11/Modules/_bsddb.c:1531
...
```
We can see that the `malloc` call on the line marked (4.) fails due to corrupted heap structures.
Also, running the script outside of GDB leads to a different message because of differences in heap layout:
```
vagrant at vagrant-ubuntu-trusty-32:/vagrant/Python-2.7.11$ ./python.exe vuln.py
*** Error in `python': corrupted double-linked list: 0x099e9858 ***
Aborted (core dumped)
```

This vulnerability can be fixed by checking for the overflow before the call to malloc. Also, note that the PyBytes_Check check does not exit the function, but PyBytesAsStringAndSize is called immediately afterwards. I would recommend breaking or continuing if that check fails, although I do think PyBytesAsStringAndSize performs this check as well.

----------
components: Library (Lib)
files: bsddbpoc.py
messages: 256974
nosy: Ned Williamson
priority: normal
severity: normal
status: open
title: Integer overflow in _bsddb leads to heap corruption
type: crash
versions: Python 2.7
Added file: http://bugs.python.org/file41408/bsddbpoc.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25943>
_______________________________________

From report at bugs.python.org  Thu Dec 24 23:12:40 2015
From: report at bugs.python.org (Ned Williamson)
Date: Fri, 25 Dec 2015 04:12:40 +0000
Subject: [New-bugs-announce] [issue25944] Type confusion in partial_setstate
 and partial_repr leads to control flow hijack
Message-ID: <1451016760.11.0.799942941118.issue25944@psf.upfronthosting.co.za>


New submission from Ned Williamson:

static PyObject *
partial_setstate(partialobject *pto, PyObject *state)
{
    PyObject *fn, *fnargs, *kw, *dict;
    if (!PyArg_ParseTuple(state, "OOOO",
                          &fn, &fnargs, &kw, &dict))
        return NULL;
    Py_XDECREF(pto->fn);
    Py_XDECREF(pto->args);
    Py_XDECREF(pto->kw);
    Py_XDECREF(pto->dict);
    pto->fn = fn;
    pto->args = fnargs; //we control pto->args here

`partial_setstate` performs no checks on the objects
it is passed as an argument.

static PyObject *
partial_repr(partialobject *pto)
{
    PyObject *result;
    PyObject *arglist;
    PyObject *tmp;
    Py_ssize_t i, n;
    arglist = PyUnicode_FromString("");
    if (arglist == NULL) {
        return NULL;
    }
    /* Pack positional arguments */
    assert (PyTuple_Check(pto->args)); //not compiled in release build
    n = PyTuple_GET_SIZE(pto->args);
    for (i = 0; i < n; i++) {
        tmp = PyUnicode_FromFormat("%U, %R", arglist,
                                   PyTuple_GET_ITEM(pto->args, i));

In partial_repr, `pto->args` is assumed to be a tuple and
unsafe functions `PyTuple_GET_SIZE` and `PyTuple_GET_ITEM`
are called on `pto->args`. This bug is particularly bad
because `PyUnicode_FromFormat` will call the object's repr
function. In this case, the attacker gains complete control
over the program counter.

vagrant at vagrant-ubuntu-wily-64:/vagrant/Python-3.5.1$ gdb -q ./python.exe
...
(gdb) r partialpoc.py
Starting program: /vagrant/Python-3.5.1/python.exe partialpoc.py
...
Program received signal SIGSEGV, Segmentation fault.
0x00000000004851f6 in PyObject_Repr (v=0x972c90) at Objects/object.c:482
482	    res = (*v->ob_type->tp_repr)(v);
(gdb) i r
rax            0x4141414141414141	4702111234474983745
rbx            0x972c90	9907344
rcx            0x52	82
rdx            0x7ffff7026718	140737337517848
rsi            0x0	0
rdi            0x972c90	9907344
rbp            0x6666666666666667	0x6666666666666667
rsp            0x7fffffffdb60	0x7fffffffdb60
r8             0x0	0
r9             0x6049a8	6310312
r10            0xffffffffffffffff	-1
r11            0xffffffffffffffff	-1
r12            0x7fffffffffffffff	9223372036854775807
r13            0x7fffffffdbe0	140737488346080
r14            0x6049a7	6310311
r15            0x0	0
rip            0x4851f6	0x4851f6 <PyObject_Repr+38>
eflags         0x10206	[ PF IF RF ]
cs             0x33	51
ss             0x2b	43
ds             0x0	0
es             0x0	0
fs             0x0	0
gs             0x0	0
(gdb) x/3i $pc
=> 0x4851f6 <PyObject_Repr+38>:	callq  *%rax
   0x4851f8 <PyObject_Repr+40>:	test   %rax,%rax
   0x4851fb <PyObject_Repr+43>:	mov    %rax,%rbx

Please see the attached POC.

----------
components: Library (Lib)
files: partialpoc.py
messages: 256975
nosy: Ned Williamson
priority: normal
severity: normal
status: open
title: Type confusion in partial_setstate and partial_repr leads to control flow hijack
type: crash
versions: Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41409/partialpoc.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25944>
_______________________________________

From report at bugs.python.org  Thu Dec 24 23:16:41 2015
From: report at bugs.python.org (Ned Williamson)
Date: Fri, 25 Dec 2015 04:16:41 +0000
Subject: [New-bugs-announce] [issue25945] Type confusion in partial_setstate
 and partial_call leads to memory corruption
Message-ID: <1451017001.94.0.489150526382.issue25945@psf.upfronthosting.co.za>


New submission from Ned Williamson:

static PyObject *
partial_setstate(partialobject *pto, PyObject *state)
{
    PyObject *fn, *fnargs, *kw, *dict;
    if (!PyArg_ParseTuple(state, "OOOO",
                          &fn, &fnargs, &kw, &dict))
        return NULL;
    Py_XDECREF(pto->fn);
    Py_XDECREF(pto->args);
    Py_XDECREF(pto->kw);
    Py_XDECREF(pto->dict);
    pto->fn = fn;
    pto->args = fnargs; //we control pto->args here

`partial_setstate` performs no checks on the objects
it is passed as an argument.

static PyObject *
partial_call(partialobject *pto, PyObject *args, PyObject *kw)
{
    PyObject *ret;
    PyObject *argappl = NULL, *kwappl = NULL;

    assert (PyCallable_Check(pto->fn));
    assert (PyTuple_Check(pto->args)); //assume pto->args is a tuple
                                       //assertion not present in release build
    assert (pto->kw == Py_None  ||  PyDict_Check(pto->kw));

    if (PyTuple_GET_SIZE(pto->args) == 0) {
        argappl = args;
        Py_INCREF(args);
    } else if (PyTuple_GET_SIZE(args) == 0) {
        argappl = pto->args; //partial function called with no arguments
        Py_INCREF(pto->args);
    } else {
        argappl = PySequence_Concat(pto->args, args);
        if (argappl == NULL)
            return NULL;
    }

    if (pto->kw == Py_None) {
        kwappl = kw;
        Py_XINCREF(kw);
    } else {
        kwappl = PyDict_Copy(pto->kw);
        if (kwappl == NULL) {
            Py_DECREF(argappl);
            return NULL;
        }
        if (kw != NULL) {
            if (PyDict_Merge(kwappl, kw, 1) != 0) {
                Py_DECREF(argappl);
                Py_DECREF(kwappl);
                return NULL;
            }
        }
    }
    ret = PyObject_Call(pto->fn, argappl, kwappl); //pto->fn called with non-tuple argappl

We can see that in the provided POC there is an increment on a user-controlled address (in this case, the literal refcount of a given "argument" is interpreted as a pointer), as `_PyEval_EvalCodeWithName` does not validate the type of `PyObject **args` either (I assume this is a fair assumption for `_PyEval_EvalCodeWithName`, and the bug simply lies in the unsafe partial code.

vagrant at vagrant-ubuntu-wily-64:/vagrant/Python-3.5.1$ gdb -q ./python.exe
...
(gdb) r partialpoc2.py
Starting program: /vagrant/Python-3.5.1/python.exe partialpoc2.py
...
Program received signal SIGSEGV, Segmentation fault.
_PyEval_EvalCodeWithName (_co=0x7ffff7045ae0, globals=<optimized out>, locals=locals at entry=0x0, args=args at entry=0x7ffff6fbc520, argcount=1280, kws=kws at entry=0x0, kwcount=0, defs=0x0, defcount=0,
    kwdefs=0x0, closure=0x0, name=0x0, qualname=0x0) at Python/ceval.c:3793
3793	            Py_INCREF(x);
(gdb) i r
rax            0x9b4b68	10177384
rbx            0x7ffff6fbc520	140737337083168
rcx            0x1	1
rdx            0x2	2
rsi            0x500	1280
rdi            0x0	0
rbp            0x0	0x0
rsp            0x7fffffffdb30	0x7fffffffdb30
r8             0x500	1280
r9             0x0	0
r10            0x7ffff74a6c58	140737342237784
r11            0x9b4b40	10177344
r12            0x0	0
r13            0x0	0
r14            0x7ffff6fb91e0	140737337070048
r15            0x7ffff7e1a048	140737352147016
rip            0x4fc771	0x4fc771 <_PyEval_EvalCodeWithName+961>
eflags         0x10202	[ IF RF ]
cs             0x33	51
ss             0x2b	43
ds             0x0	0
es             0x0	0
fs             0x0	0
gs             0x0	0
(gdb) x/3i $pc
=> 0x4fc771 <_PyEval_EvalCodeWithName+961>:	addq   $0x1,(%rsi)
   0x4fc775 <_PyEval_EvalCodeWithName+965>:	cmp    %edx,%r8d
   0x4fc778 <_PyEval_EvalCodeWithName+968>:	mov    %rsi,0x18(%rax,%rcx,8)

----------
files: partialpoc2.py
messages: 256976
nosy: Ned Williamson
priority: normal
severity: normal
status: open
title: Type confusion in partial_setstate and partial_call leads to memory corruption
type: crash
versions: Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41410/partialpoc2.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25945>
_______________________________________

From report at bugs.python.org  Thu Dec 24 23:26:48 2015
From: report at bugs.python.org (Karl Richter)
Date: Fri, 25 Dec 2015 04:26:48 +0000
Subject: [New-bugs-announce] [issue25946] configure should pick /usr/bin/g++
 automatically if present
Message-ID: <1451017608.26.0.200778632077.issue25946@psf.upfronthosting.co.za>


New submission from Karl Richter:

`./configure` both prints `checking for g++... no` and 

    WARNING:
    
      By default, distutils will build C++ extension modules with "g++".
      If this is not intended, then set CXX on the configure command line.

if `/usr/bin/g++` is present and executable which doesn't seem to be constructive because it's quite common that one wants to use `/usr/bin/g++` as CXX compiler if available. In case incompatibilities exists with other C++ compilers there should a check and more detailed error message.

Furthermore the error message doesn't explain if a part of distutils won't be build because the message sounds like the C++ extension is built, but does it work without a C++ compiler?

Specifying `CXX` environment variable or `--with-cxx-main=/usr/bin/g++` `configure` option works fine.

experienced with 8a2e735 (on branch 2.7)

----------
components: Build
messages: 256977
nosy: krichter
priority: normal
severity: normal
status: open
title: configure should pick /usr/bin/g++ automatically if present
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25946>
_______________________________________

From report at bugs.python.org  Fri Dec 25 05:33:43 2015
From: report at bugs.python.org (vog)
Date: Fri, 25 Dec 2015 10:33:43 +0000
Subject: [New-bugs-announce] [issue25948] email.mime creates invalid MIME
 encoding (line too long)
Message-ID: <1451039623.64.0.603876276349.issue25948@psf.upfronthosting.co.za>


New submission from vog:

The email.mime package creates invalid MIME encoding (line too long) on certain inputs. That is, by proper usage of the email.mime API it is possible to create invalid emails that will be rejected by most mail servers.


Steps to reproduce
==================

1. Create a string that has the following properties:

1.1. The string contains only US-ASCII characters
1.2. The string contains a line that is longer than ~1000 characters

(For example, this could be an english-language HTML document that contains embedded images as "data:" URIs.)

2. Create MIMEText instance with that text, don't specify a charset

(This will default to 'us-ascii'. Alternatively, specify the 'us-ascii' charset explicitly.)

3. Create Message out of that MIMEText instance

4. Serialize the message


Expected result
===============

A MIME encoded email message that conforms to RFC 5322, section 2.1.1.: "Each line of characters MUST be no more than 998 characters, and SHOULD be no more than 78 characters, excluding the CRLF."


Actual result
=============

A MIME encoded email message that contains a line with more than 998 characters.  Hence, the email is rightfully rejected by most mail servers.


Workaround
==========

Specify the UTF-8 charset explicitly.  This forces MIMEText to switch to Base64 encoding, which will generate lines no longer than 78 characters.

For example, replace the following constructions:

MIMEText('Text with very long line', 'plain')
MIMEText('HTML with very long line', 'html')

with:

MIMEText('Text with very long line', 'plain', 'utf-8')
MIMEText('HTML with very long line', 'html', 'utf-8')


References
==========

- RFC 5322, 2.1.1. Line Length Limits
  https://tools.ietf.org/html/rfc5322#section-2.1.1

- RFC 2822, 2.1.1. Line Length Limits
  https://tools.ietf.org/html/rfc2822#section-2.1.1


Related issues
==============

- Django #22561: EmailMessage should respect RFC2822 on max line length
  https://code.djangoproject.com/ticket/22561

- Python #9298: binary email attachment issue with base64 encoding
  https://bugs.python.org/issue9298

----------
components: Library (Lib), email
files: test_mime_long_line.py
messages: 256982
nosy: barry, r.david.murray, vog
priority: normal
severity: normal
status: open
title: email.mime creates invalid MIME encoding (line too long)
type: behavior
versions: Python 3.5
Added file: http://bugs.python.org/file41415/test_mime_long_line.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25948>
_______________________________________

From report at bugs.python.org  Fri Dec 25 07:48:08 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 25 Dec 2015 12:48:08 +0000
Subject: [New-bugs-announce] [issue25949] Lazy creation of __dict__ in
 OrderedDict
Message-ID: <1451047688.41.0.0988158472157.issue25949@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

For now OrderedDict always creates an empty dict for __dict__.

>>> from collections import OrderedDict
>>> import gc
>>> gc.get_referents(OrderedDict())
[{}]
>>> class OD(OrderedDict): pass
... 
>>> gc.get_referents(OD())
[<class '__main__.OD'>, {}]

But dict subclasses (as well as most other classes) create an empty dict for __dict__ only if needed.

>>> class D(dict): pass
... 
>>> d = D()
>>> gc.get_referents(d)
[<class '__main__.D'>]
>>> d.__dict__
{}
>>> gc.get_referents(d)
[{}, <class '__main__.D'>]

This allows to save CPU time for dictionary creation and a memory (144 bytes on 32-bit, twice as much on 64-bit).

Proposed patch makes __dict__ in OrderedDict to be created only if needed.

----------
components: Extension Modules
files: odict___dict__.patch
keywords: patch
messages: 256988
nosy: eric.snow, rhettinger, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Lazy creation of __dict__ in OrderedDict
type: enhancement
versions: Python 3.6
Added file: http://bugs.python.org/file41419/odict___dict__.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25949>
_______________________________________

From report at bugs.python.org  Fri Dec 25 09:10:12 2015
From: report at bugs.python.org (koobs)
Date: Fri, 25 Dec 2015 14:10:12 +0000
Subject: [New-bugs-announce] [issue25950] svn.python.org SSL certificate
 expired, causing test failures
Message-ID: <1451052612.81.0.831910500376.issue25950@psf.upfronthosting.co.za>


New submission from koobs:

It appears all HTTPS/SSL tests that use the remote host svn.python.org are failing.

All branch builds (tests) are currently broken on koobs-freebsd-current. I think it's the only bot that has run builds post 24th December so far.

http://buildbot.python.org/all/builders/AMD64%20FreeBSD%20CURRENT%203.5/builds/21/steps/test/logs/stdio

Investigation reveals:

svn.python.org uses an invalid security certificate. 

The certificate is not trusted because the issuer certificate is unknown. The server might not be sending the appropriate intermediate certificates. An additional root certificate may need to be imported. 

The certificate expired on Friday, 25 December 2015 7:28 AM. The current time is Saturday, 26 December 2015 1:01 AM. 

(Error code: sec_error_unknown_issuer)

Have poked people in #python-infra

----------
messages: 256990
nosy: koobs
priority: normal
severity: normal
status: open
title: svn.python.org SSL certificate expired, causing test failures

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25950>
_______________________________________

From report at bugs.python.org  Fri Dec 25 09:45:15 2015
From: report at bugs.python.org (ProgVal)
Date: Fri, 25 Dec 2015 14:45:15 +0000
Subject: [New-bugs-announce] [issue25951] SSLSocket.sendall() does not
 return None on success like socket.sendall()
Message-ID: <1451054715.95.0.578529633079.issue25951@psf.upfronthosting.co.za>


New submission from ProgVal:

socket.sendall() returns None if it succeeded <https://docs.python.org/3/library/socket.html#socket.socket.sendall>
SSLSocket.sendall() is said to have the same behavior as socket.sendall(), besides not allowing flags <https://docs.python.org/3/library/ssl.html#ssl.SSLSocket>

However, SSLSocket.sendall() returns the amount of bytes written on success.

----------
components: Library (Lib)
messages: 256992
nosy: ProgVal
priority: normal
severity: normal
status: open
title: SSLSocket.sendall() does not return None on success like socket.sendall()
versions: Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25951>
_______________________________________

From report at bugs.python.org  Fri Dec 25 11:14:47 2015
From: report at bugs.python.org (=?utf-8?q?Grzegorz_Kraso=C5=84?=)
Date: Fri, 25 Dec 2015 16:14:47 +0000
Subject: [New-bugs-announce] [issue25952] code_context not available in
 exec()
Message-ID: <1451060087.44.0.968939849155.issue25952@psf.upfronthosting.co.za>


New submission from Grzegorz Kraso?:

inspect.stack()[n].code_context() is empty when context is created by exec()

----------
files: issue.py
messages: 256998
nosy: Grzegorz Kraso?
priority: normal
severity: normal
status: open
title: code_context not available in exec()
type: behavior
versions: Python 3.5
Added file: http://bugs.python.org/file41421/issue.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25952>
_______________________________________

From report at bugs.python.org  Fri Dec 25 14:46:48 2015
From: report at bugs.python.org (bazwal)
Date: Fri, 25 Dec 2015 19:46:48 +0000
Subject: [New-bugs-announce] [issue25953] re fails to identify invalid
 numeric group references in replacement strings
Message-ID: <1451072808.1.0.287523380704.issue25953@psf.upfronthosting.co.za>


New submission from bazwal:

This code example:

    re.sub(r'(?P<x>[123])', r'\g<a>', '')

will correctly raise a KeyError due to the invalid group reference.

However, this very similar code example:

    re.sub(r'(?P<x>[123])', r'\g<3>', '')

fails to raise an error. It seems that the only way to check whether a numeric group reference is compatible with a given pattern is to test it against a string which happens to match. But this is obviously infeasible when checking unknown expressions (e.g. those taken from user input). And in any case: errors should be raised at the point where they occur (i.e. during compilation), not at some indeterminate point in the future.

Regular expression objects have a "groups" attribute which holds the number of capturing groups in the pattern. So there seems no good reason why the replacement string parser can't identify invalid numeric group references in exactly the same way that it does for symbolic ones.

----------
components: Regular Expressions
messages: 257008
nosy: bazwal, ezio.melotti, mrabarnett
priority: normal
severity: normal
status: open
title: re fails to identify invalid numeric group references in replacement strings
type: behavior
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25953>
_______________________________________

From report at bugs.python.org  Fri Dec 25 22:27:22 2015
From: report at bugs.python.org (Ned Batchelder)
Date: Sat, 26 Dec 2015 03:27:22 +0000
Subject: [New-bugs-announce] [issue25954] Python 3.5.1 installer fails on
 Windows 7
Message-ID: <1451100442.78.0.216176327365.issue25954@psf.upfronthosting.co.za>


New submission from Ned Batchelder:

I tried to install 3.5.1 32-bit into a fresh virtualbox image from https://dev.windows.com/en-us/microsoft-edge/tools/vms/mac/ (IE 10 on Win 7), and got this error message.  When I try to run Python with "py -3", it will not run, it only shows:

                    ---------------------------
                    python.exe - System Error
                    ---------------------------
                    The program can't start because api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem. 
                    ---------------------------
                    OK   
                    ---------------------------

I tried repairing the installation (with the control panel), which did not help.

I've attached the log files created by the installer.

----------
components: Windows
files: Python 3.5.1 logs.zip
messages: 257017
nosy: nedbat, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Python 3.5.1 installer fails on Windows 7
versions: Python 3.5
Added file: http://bugs.python.org/file41423/Python 3.5.1 logs.zip

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25954>
_______________________________________

From report at bugs.python.org  Sat Dec 26 08:17:02 2015
From: report at bugs.python.org (Sergei Maertens)
Date: Sat, 26 Dec 2015 13:17:02 +0000
Subject: [New-bugs-announce] [issue25955] email.utils.formataddr does not
 support RFC 6532
Message-ID: <1451135822.65.0.451627687424.issue25955@psf.upfronthosting.co.za>


New submission from Sergei Maertens:

The function `formataddr` in stdlib `email.utils` does not allow unicode e-mail addresses where the first part (before the @) is unicode. Python 3.5 promises support for SMTPUTF8 through `EmailPoliy.utf8` (https://docs.python.org/3/whatsnew/3.5.html#email), but this utility function doesn't respect this, as it calls `address.encode('ascii')`.

For unicode addresses, an obvious `UnicodeEncodeError` is raised.

Reproduce steps:

?  ~  python
Python 3.5.1 (default, Dec  7 2015, 12:58:09) 
[GCC 5.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from email.utils import formataddr
>>> formataddr(('dummy', 'juan.l?pez at abc.com'))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3.5/email/utils.py", line 91, in formataddr
    address.encode('ascii')
UnicodeEncodeError: 'ascii' codec can't encode character '\xf3' in position 6: ordinal not in range(128)

Interesting is that on Python 2.7 the behaviour is more naive, but it works::

?  ~  python2
Python 2.7.11 (default, Dec  6 2015, 15:43:46) 
[GCC 5.2.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from email.utils import formataddr
>>> formataddr(('dummy', u'juan.l?pez at abc.com'))
u'dummy <juan.l\xf3pez at abc.com>'

----------
components: email
messages: 257034
nosy: Sergei Maertens, barry, r.david.murray
priority: normal
severity: normal
status: open
title: email.utils.formataddr does not support RFC 6532
type: enhancement
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25955>
_______________________________________

From report at bugs.python.org  Sat Dec 26 10:03:56 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 26 Dec 2015 15:03:56 +0000
Subject: [New-bugs-announce] [issue25956] Unambiguous representation of
 recursive objects
Message-ID: <1451142236.84.0.215229457015.issue25956@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

For now repr() of recursive object replaces nested representations of self with a placeholder containing "...": "[...]" for list, "{...}" for dict, "set(...)" for set, and just "..." for Python classes that use reprlib. Unfortunately such replacements are valid expressions in Python 3.

The same replacement is used for too deeply nested objects in reprlib and pprint.

Proposed patch makes "<...>" to be always used as a placeholder. This is invalid syntax and well visually distinguishable.

Python-Ideas discussion: http://comments.gmane.org/gmane.comp.python.ideas/37555

----------
components: Interpreter Core, Library (Lib)
files: repr_recursive.patch
keywords: patch
messages: 257037
nosy: fdrake, ncoghlan, rhettinger, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Unambiguous representation of recursive objects
type: enhancement
versions: Python 3.6
Added file: http://bugs.python.org/file41426/repr_recursive.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25956>
_______________________________________

From report at bugs.python.org  Sat Dec 26 14:35:41 2015
From: report at bugs.python.org (Mike Ryan)
Date: Sat, 26 Dec 2015 19:35:41 +0000
Subject: [New-bugs-announce] [issue25957] sockaddr_l2 lacks CID,
 address type (AF_BLUETOOTH sockets)
Message-ID: <1451158541.36.0.577449474291.issue25957@psf.upfronthosting.co.za>


New submission from Mike Ryan:

The AF_BLUETOOTH socket type lacks support for specifying CID and address type in sockaddr_l2. These structure members have been present since 2009 and 2012 respectively:

https://git.kernel.org/cgit/bluetooth/bluez.git/commit/?id=3de95535
https://git.kernel.org/cgit/bluetooth/bluez.git/commit/?id=ba801fcd

The current version of the full structure can be found here:

https://git.kernel.org/cgit/bluetooth/bluez.git/tree/lib/l2cap.h?id=1b9e48f4#n40

The Python code in question can be found here:

https://github.com/python/cpython/blob/4f9794dbcaa6ee7ddc6ab175a57e7f01ebe64353/Modules/socketmodule.c#L1108

----------
components: Extension Modules
messages: 257043
nosy: mikeryan
priority: normal
severity: normal
status: open
title: sockaddr_l2 lacks CID, address type (AF_BLUETOOTH sockets)
type: behavior
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25957>
_______________________________________

From report at bugs.python.org  Sat Dec 26 17:26:42 2015
From: report at bugs.python.org (Andrew Barnert)
Date: Sat, 26 Dec 2015 22:26:42 +0000
Subject: [New-bugs-announce] [issue25958] Implicit ABCs have no means of
 "anti-registration"
Message-ID: <1451168802.83.0.911068284232.issue25958@psf.upfronthosting.co.za>


New submission from Andrew Barnert:

Serhiy Storchaka raised an issue (http://bugs.python.org/msg256910) with static type hints on #25864 (http://bugs.python.org/issue25864), which I believe also applies to runtime ABCs.

Consider this class, which uses `[]` in a way similar to generic types:

    class Thing:
        def __getitem__(self, specialization):
            return type(self)._specialize(specialization)(self)
        def __len__(self):
            return len(self._specializations)

Because this type looks like it supports the old-style sequence protocol, calling either `iter` or `reversed` on an instance will successfully return a useless iterator. (You may get an error when you start trying to iterate it, but you may not even then.) You don't want that, so you add either this:

        __iter__ = None
        __reversed__ = None

... or this:

        def __iter__(self): raise TypeError('not iterable')
        def __reversed__(self): raise TypeError('not iterable')

Unfortunately, doing either means that `issubclass(Thing, collections.abc.Iterable)` now returns true. Which is the exact opposite of the intention of that check. (The same is true for `typing.Iterable` and `typing.Reversible`.) So, fixing the problem for duck typing creates the equivalent problem for explicit typing.

There are a few possible solutions here:

1. Maybe document it, otherwise do nothing.

2. Change the ABCs to check that the dunder method exists and is not None (or is callable, or is a non-data descriptor). Then, the one way to opt out is to assign `__iter__ = __reversed__ = None`.

3. Add an `ABC.unregister` method that can be used to explicitly state that this type does not support that ABC, regardless of what its `__subclasshook__` says.

Possible argument for #1: `Iterable` rarely has a problem. (Types that use `__getitem__` for something completely un-sequence-like, like `typing`'s generic types, usually don't have `__len__`. Types that have both `__getitem__` and `__len__`, like mappings, usually have a reasonable alternative `__iter__` to offer.) `Reversible` would have a problem if there was such an ABC, but there isn't. Off the top of my head, I can't think of any of the other implicit ABCs that are susceptible to this problem.

The counter-argument is that static typehinting definitely does have this problem (https://github.com/ambv/typehinting/issues/170), and, depending on how that's solved, it may well make sense to use the same solution here.

If we do need a solution, #2 seems better than #3 (or anything else I could think up). The only problem there is that `def __iter__(self): raise TypeError('not iterable')` gives you a nicer error than `__iter__ = None`.

----------
components: Library (Lib)
messages: 257052
nosy: abarnert
priority: normal
severity: normal
status: open
title: Implicit ABCs have no means of "anti-registration"
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25958>
_______________________________________

From report at bugs.python.org  Sat Dec 26 18:16:11 2015
From: report at bugs.python.org (hcdb)
Date: Sat, 26 Dec 2015 23:16:11 +0000
Subject: [New-bugs-announce] [issue25959] tkinter - PhotoImage.zoom() causes
 segfault
Message-ID: <1451171771.79.0.252031360467.issue25959@psf.upfronthosting.co.za>


New submission from hcdb:

My 6 lines of code crash and cause a segmentation fault when using .zoom() on a PhotoImage in tkinter (run test.py)

tested and crashed in python 2.7.6, 2.7.9, 3.4.2 & 3.4.3 on linux mint 17.3 and debian jessie

ps. just learning to code python, so maybe i'm doing it wrong.

----------
components: Tkinter
files: test.py
messages: 257055
nosy: hcbd
priority: normal
severity: normal
status: open
title: tkinter - PhotoImage.zoom() causes segfault
type: crash
versions: Python 2.7, Python 3.4
Added file: http://bugs.python.org/file41427/test.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25959>
_______________________________________

From report at bugs.python.org  Sun Dec 27 05:58:02 2015
From: report at bugs.python.org (Chris Jerdonek)
Date: Sun, 27 Dec 2015 10:58:02 +0000
Subject: [New-bugs-announce] [issue25960] Popen.wait() hangs with SIGINT
 when os.waitpid() does not
Message-ID: <1451213882.47.0.471062889789.issue25960@psf.upfronthosting.co.za>


New submission from Chris Jerdonek:

I came across a situation where Popen.wait() hangs and os.waitpid() doesn't hang.  It seems like a bug, but I don't know for sure.  This is with Python 3.5.1.

To reproduce, save the following to demo.py:

    import os, signal, subprocess

    class State:
        process = None

    def handle_signal(signalnum, frame):
        print("Handling: {0}".format(signalnum))
        p = State.process
        # The following line hangs:
        p.wait()
        # However, this line does not hang:
        # os.waitpid(p.pid, 1)
        print("Done waiting")

    signal.signal(signal.SIGINT, handle_signal)
    p = subprocess.Popen("while true; do echo sleeping; sleep 2; done",
                         shell=True)
    State.process = p
    p.wait()

Then run the following, hit Control-C, and it will hang:

    $ python demo.py 
    sleeping
    sleeping
    ^CHandling: 2

It will still hang if you insert "p.terminate()" right before p.wait().

However, calling "os.waitpid(p.pid, ...)" instead of p.wait() exits immediately and does not hang.  The behavior also occurs without shell=True.

----------
components: Library (Lib)
messages: 257071
nosy: chris.jerdonek
priority: normal
severity: normal
status: open
title: Popen.wait() hangs with SIGINT when os.waitpid() does not
type: behavior
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25960>
_______________________________________

From report at bugs.python.org  Sun Dec 27 09:28:00 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 27 Dec 2015 14:28:00 +0000
Subject: [New-bugs-announce] [issue25961] Disallow the null character in
 type name
Message-ID: <1451226480.87.0.0659065914437.issue25961@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

The null character is allowed in __name__ setter (but error message is a little confusing).

>>> class A: pass
... 
>>> A.__name__ = 'B\0'
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ValueError: __name__ must not contain null bytes

But is allowed in type constructor.

>>> t = type('B\0C', (), {})
>>> t
<class '__main__.BC'>
>>> t.__name__
'B\x00C'

----------
components: Interpreter Core
messages: 257076
nosy: serhiy.storchaka
priority: normal
severity: normal
stage: needs patch
status: open
title: Disallow the null character in type name
type: behavior
versions: Python 2.7, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25961>
_______________________________________

From report at bugs.python.org  Mon Dec 28 02:48:19 2015
From: report at bugs.python.org (Meng-Yuan Huang)
Date: Mon, 28 Dec 2015 07:48:19 +0000
Subject: [New-bugs-announce] [issue25962] Ctrl+C Can't Exit Script with Pool
 on Windows
Message-ID: <1451288899.74.0.53616811767.issue25962@psf.upfronthosting.co.za>


New submission from Meng-Yuan Huang:

My OS is Windows 10 Pro 64-bit. My Python version is 3.5.1 64-bit.
I wrote a simple script (t.py, see the attached file) with multiprocessing.Pool and run it by:
python t.py
in Windows Command Prompt.
I tried to interrupt the running script by pressing Ctrl+C keys. Python showed the message:
-----------------------------------
Work Started: 21360
Process SpawnPoolWorker-1:
Traceback (most recent call last):
  File "d:\Anaconda3\lib\multiprocessing\process.py", line 254, in _bootstrap
    self.run()
  File "d:\Anaconda3\lib\multiprocessing\process.py", line 93, in run
    self._target(*self._args, **self._kwargs)
  File "d:\Anaconda3\lib\multiprocessing\pool.py", line 119, in worker
    result = (True, func(*args, **kwds))
  File "C:\Users\myh\Documents\Python Scripts\t.py", line 7, in do_work
    1
KeyboardInterrupt
-----------------------------------

However, it didn't terminate Python and come back to Windows Command Prompt. It just hang there.
Then, I pressed another Ctrl+C. Python showed:
-----------------------------------
Process SpawnPoolWorker-2:
Traceback (most recent call last):
  File "d:\Anaconda3\lib\multiprocessing\process.py", line 254, in _bootstrap
    self.run()
  File "d:\Anaconda3\lib\multiprocessing\process.py", line 93, in run
    self._target(*self._args, **self._kwargs)
  File "d:\Anaconda3\lib\multiprocessing\pool.py", line 108, in worker
    task = get()
  File "d:\Anaconda3\lib\multiprocessing\queues.py", line 343, in get
    res = self._reader.recv_bytes()
  File "d:\Anaconda3\lib\multiprocessing\connection.py", line 216, in recv_bytes
    buf = self._recv_bytes(maxlength)
  File "d:\Anaconda3\lib\multiprocessing\connection.py", line 306, in _recv_bytes
    [ov.event], False, INFINITE)
KeyboardInterrupt
-----------------------------------

Unfortunately, it still didn't terminate Python and come back to Windows Command Prompt!
However, I run the same script with Python 3.5.1 64-bit on a CetnOS 7 64-bit,
it can terminate Python and come back to the terminal.

Is this a bug on Windows?

----------
components: Windows
files: t.py
messages: 257106
nosy: Meng-Yuan Huang, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Ctrl+C Can't Exit Script with Pool on Windows
type: behavior
versions: Python 3.5
Added file: http://bugs.python.org/file41436/t.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25962>
_______________________________________

From report at bugs.python.org  Mon Dec 28 03:32:13 2015
From: report at bugs.python.org (Utkonos)
Date: Mon, 28 Dec 2015 08:32:13 +0000
Subject: [New-bugs-announce] [issue25963] strptime not parsing some timezones
Message-ID: <1451291533.28.0.979317956785.issue25963@psf.upfronthosting.co.za>


New submission from Utkonos:

I get a ValueError when running the following through strptime:

datetime.datetime.strptime('(CST)', '(%Z)')

But the following works:
datetime.datetime.strptime('(EST)', '(%Z)')

PST and MST also trigger the same exception.

----------
messages: 257108
nosy: belopolsky, brett.cannon, utkonos
priority: normal
severity: normal
status: open
title: strptime not parsing some timezones
type: behavior
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25963>
_______________________________________

From report at bugs.python.org  Mon Dec 28 05:09:18 2015
From: report at bugs.python.org (Martin Mokrejs)
Date: Mon, 28 Dec 2015 10:09:18 +0000
Subject: [New-bugs-announce] [issue25964] optparse.py:1668: (file) shadows
 builtin
Message-ID: <1451297358.11.0.762402677085.issue25964@psf.upfronthosting.co.za>


New submission from Martin Mokrejs:

I use pychecker for checking my python code. Seems optparse.py distributed with python-2.7 could be improved as well:

[system path]/optparse.py:1191: Function (__init__) has too many arguments (11)
[system path]/optparse.py:1206: Local variable (version) shadows global defined on line 10 in file my-test-code.py
[system path]/optparse.py:1400: Local variable (stop) not used
[system path]/optparse.py:1668: (file) shadows builtin


Interestingly, my version variable is overridden by one from optparse.py. But more worrisome is the 'file' variable name.

----------
messages: 257110
nosy: mmokrejs
priority: normal
severity: normal
status: open
title: optparse.py:1668: (file) shadows builtin
type: enhancement
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25964>
_______________________________________

From report at bugs.python.org  Mon Dec 28 05:14:28 2015
From: report at bugs.python.org (Martin Mokrejs)
Date: Mon, 28 Dec 2015 10:14:28 +0000
Subject: [New-bugs-announce] [issue25965] decimal.py: issues reprted by
 pychecker
Message-ID: <1451297668.35.0.148993331552.issue25965@psf.upfronthosting.co.za>


New submission from Martin Mokrejs:

I use pychecker to check my code. It complains about decimal.py from python-2.7.10 itself:

[system path]/decimal.py:1345: INTERNAL ERROR -- STOPPED PROCESSING FUNCTION --
        Traceback (most recent call last):
          File "/usr/lib64/python2.7/site-packages/pychecker/warn.py", line 242, in _checkFunction
            _checkCode(code, codeSource)
          File "/usr/lib64/python2.7/site-packages/pychecker/warn.py", line 155, in _checkCode
            raise NotImplementedError('No DISPATCH member for op %r' % op)
        NotImplementedError: No DISPATCH member for op 28

[system path]/decimal.py:1546: Invalid arguments to (__floordiv__), got 3, expected 2
[system path]/decimal.py:1574: Invalid arguments to (__rfloordiv__), got 3, expected 2
[system path]/decimal.py:1997: INTERNAL ERROR -- STOPPED PROCESSING FUNCTION --
        Traceback (most recent call last):
          File "/usr/lib64/python2.7/site-packages/pychecker/warn.py", line 242, in _checkFunction
            _checkCode(code, codeSource)
          File "/usr/lib64/python2.7/site-packages/pychecker/warn.py", line 155, in _checkCode
            raise NotImplementedError('No DISPATCH member for op %r' % op)
        NotImplementedError: No DISPATCH member for op 28

[system path]/decimal.py:2173: Invalid arguments to (__pow__), got 4, expected 3
[system path]/decimal.py:2389: Invalid arguments to (__rpow__), got 3, expected 2
[system path]/decimal.py:2692: INTERNAL ERROR -- STOPPED PROCESSING FUNCTION --
        Traceback (most recent call last):
          File "/usr/lib64/python2.7/site-packages/pychecker/warn.py", line 242, in _checkFunction
            _checkCode(code, codeSource)
          File "/usr/lib64/python2.7/site-packages/pychecker/warn.py", line 155, in _checkCode
            raise NotImplementedError('No DISPATCH member for op %r' % op)
        NotImplementedError: No DISPATCH member for op 28

----------
components: Library (Lib)
messages: 257111
nosy: mmokrejs
priority: normal
severity: normal
status: open
title: decimal.py: issues reprted by pychecker
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25965>
_______________________________________

From report at bugs.python.org  Mon Dec 28 11:58:36 2015
From: report at bugs.python.org (Brett Rosen)
Date: Mon, 28 Dec 2015 16:58:36 +0000
Subject: [New-bugs-announce] [issue25966] Bug in
 asyncio.corotuines._format_coroutine
Message-ID: <1451321916.38.0.909641421844.issue25966@psf.upfronthosting.co.za>


New submission from Brett Rosen:

When running some test cases via py.test and using a coroutine created inside of cythonized code, I get the following:

   def _format_coroutine(coro):
        assert iscoroutine(coro)
        coro_name = getattr(coro, '__qualname__', coro.__name__)
    
        filename = coro.gi_code.co_filename
        if (isinstance(coro, CoroWrapper)
        and not inspect.isgeneratorfunction(coro.func)):
>           filename, lineno = events._get_function_source(coro.func)
E           TypeError: 'NoneType' object is not iterable


This appears to be because this line:

https://github.com/python/asyncio/blob/2a19f9329f4ee710fef7728b316aa4fe1d07dbef/asyncio/coroutines.py#L289

Is expecting to get back two values, but because of:

https://github.com/python/asyncio/blob/master/asyncio/events.py#L35

This it only gets back None.


> /usr/local/lib/python3.4/asyncio/events.py(25)_get_function_source()
-> if _PY34:
(Pdb) func
<cyfunction ProgressTracker._do_report at 0x7fdd2fc46498>

----------
components: asyncio
messages: 257119
nosy: Brett Rosen, gvanrossum, haypo, yselivanov
priority: normal
severity: normal
status: open
title: Bug in  asyncio.corotuines._format_coroutine
versions: Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25966>
_______________________________________

From report at bugs.python.org  Mon Dec 28 17:09:14 2015
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 28 Dec 2015 22:09:14 +0000
Subject: [New-bugs-announce] [issue25967] Devguide: add 2to3 to the
 "Changing CPython's Grammar" checklist
Message-ID: <1451340554.37.0.242024647268.issue25967@psf.upfronthosting.co.za>


New submission from Ezio Melotti:

If Python grammar is changed, lib2to3 should be updated accordingly.
This is currently missing from https://docs.python.org/devguide/grammar.html#checklist

See also #19511.

----------
components: Devguide
keywords: easy
messages: 257134
nosy: ezio.melotti, willingc
priority: normal
severity: normal
stage: needs patch
status: open
title: Devguide: add 2to3 to the "Changing CPython's Grammar" checklist
type: enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25967>
_______________________________________

From report at bugs.python.org  Mon Dec 28 17:12:42 2015
From: report at bugs.python.org (Chris Moore)
Date: Mon, 28 Dec 2015 22:12:42 +0000
Subject: [New-bugs-announce] [issue25968] Cannot import modules out of zip
 file with extended-length path on windows
Message-ID: <1451340762.79.0.618621999098.issue25968@psf.upfronthosting.co.za>


New submission from Chris Moore:

To reproduce, put a python module in a zip file (I have been using wheels but I assume any module in a zip file will have the same error?) , add the absolute extended-length path to sys.path (add '\\\\?\\' to the front of the normal absolute path, so '\\\\?\\c:\\Users\\cc\\test.zip' instead of 'c:\\Users\\cc\\test.zip'), then attempt to import a module that is contained in the zip file.

I have seen this issue so far on 3.4.3 and 3.5.1.  I have not tested 3.4.4 yet.

Adding directories that are extended-length paths to sys.path does allow importing modules contained in those directories, and of course using a non extended-length path to a zip file works as long as that path contains less than 260 characters.

----------
components: Interpreter Core, Windows
messages: 257136
nosy: Chris Moore, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Cannot import modules out of zip file with extended-length path on windows
type: behavior
versions: Python 3.4, Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25968>
_______________________________________

From report at bugs.python.org  Mon Dec 28 17:16:18 2015
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 28 Dec 2015 22:16:18 +0000
Subject: [New-bugs-announce] [issue25969] Update lib2to3 grammar to include
 missing unpacking generalizations.
Message-ID: <1451340978.99.0.13064674256.issue25969@psf.upfronthosting.co.za>


New submission from Ezio Melotti:

The new unpacking generalizations added in #2292 should be added to the lib2to3 grammar (see msg248019 and msg248025).

See also #25967.

----------
components: Library (Lib)
messages: 257138
nosy: benjamin.peterson, ezio.melotti, yselivanov
priority: normal
severity: normal
stage: needs patch
status: open
title: Update lib2to3 grammar to include missing unpacking generalizations.
type: behavior
versions: Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25969>
_______________________________________

From report at bugs.python.org  Mon Dec 28 17:39:26 2015
From: report at bugs.python.org (Robert Byrnes)
Date: Mon, 28 Dec 2015 22:39:26 +0000
Subject: [New-bugs-announce] [issue25970] py_compile.compile fails if
 existing bytecode file is unwritable
Message-ID: <1451342366.02.0.359815374422.issue25970@psf.upfronthosting.co.za>


New submission from Robert Byrnes:

In Python/import.c, open_exclusive unlinks any existing bytecode file before opening to create a new one.

However, py_compile.compile doesn't unlink before opening, and therefore fails if an existing bytecode file is unwritable.  It would be nice to unlink first in this case too.

----------
components: Library (Lib)
messages: 257142
nosy: byrnes
priority: normal
severity: normal
status: open
title: py_compile.compile fails if existing bytecode file is unwritable
type: behavior
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25970>
_______________________________________

From report at bugs.python.org  Mon Dec 28 17:48:18 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 Dec 2015 22:48:18 +0000
Subject: [New-bugs-announce] [issue25971] Optimize converting float and
 Decimal to Fraction
Message-ID: <1451342898.0.0.236832633563.issue25971@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Proposed patch makes following things:

1. Rewrite error messages in float.as_integer_ratio() and Python implementation of Decimal.as_integer_ratio() in more general form, not mentioning as_integer_ratio(), as in C implementation of Decimal.as_integer_ratio().

2. Use Decimal.as_integer_ratio() to convert Decimal to Fraction.

3. Get rid of additional checks in Fraction constructor that raise errors with appropriate messages, since new error messages from as_integer_ratio() are appropriate enough.

This speeds up creating a Fraction from float and Decimal 2 to 3 times.

----------
components: Interpreter Core, Library (Lib)
files: fraction_from_floating.patch
keywords: patch
messages: 257145
nosy: facundobatista, mark.dickinson, rhettinger, serhiy.storchaka, skrah
priority: normal
severity: normal
stage: patch review
status: open
title: Optimize converting float and Decimal to Fraction
type: enhancement
versions: Python 3.6
Added file: http://bugs.python.org/file41442/fraction_from_floating.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25971>
_______________________________________

From report at bugs.python.org  Mon Dec 28 20:57:43 2015
From: report at bugs.python.org (Stefan Krah)
Date: Tue, 29 Dec 2015 01:57:43 +0000
Subject: [New-bugs-announce] [issue25972] All Windows buildbots fail
 compile/clean
Message-ID: <1451354263.92.0.304872607754.issue25972@psf.upfronthosting.co.za>


New submission from Stefan Krah:

Not sure what is happening, but all Windows buildbots fail compile/clean.

----------
messages: 257161
nosy: skrah, zach.ware
priority: normal
severity: normal
status: open
title: All Windows buildbots fail compile/clean

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25972>
_______________________________________

From report at bugs.python.org  Tue Dec 29 06:40:04 2015
From: report at bugs.python.org (Konstantin Enchant)
Date: Tue, 29 Dec 2015 11:40:04 +0000
Subject: [New-bugs-announce] [issue25973] Segmentation fault with nonlocal
 and two underscores
Message-ID: <1451389204.03.0.825789428132.issue25973@psf.upfronthosting.co.za>


New submission from Konstantin Enchant:

Code:
# -------------------------------
__obj = object()

class Foo:
    def f1(self):
        nonlocal __obj

f = Foo()
f.f1()  # <-- segmentation fault
# -------------------------------

----------
messages: 257174
nosy: Konstantin Enchant
priority: normal
severity: normal
status: open
title: Segmentation fault with nonlocal and two underscores
type: crash
versions: Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25973>
_______________________________________

From report at bugs.python.org  Tue Dec 29 07:49:31 2015
From: report at bugs.python.org (Stefan Krah)
Date: Tue, 29 Dec 2015 12:49:31 +0000
Subject: [New-bugs-announce] [issue25974] Fix statistics.py after the
 Decimal.as_integer_ratio() change
Message-ID: <1451393371.35.0.476117922354.issue25974@psf.upfronthosting.co.za>


New submission from Stefan Krah:

Here's a fix for the fallout from #25928.  I've set it to
release blocker to make sure we don't forget.

----------
assignee: steven.daprano
components: Library (Lib)
files: statistics_as_integer_ratio.diff
keywords: 3.5regression, patch
messages: 257178
nosy: belopolsky, johnwalker, mark.dickinson, python-dev, rhettinger, serhiy.storchaka, skrah, steven.daprano, terry.reedy
priority: release blocker
severity: normal
status: open
title: Fix statistics.py after the Decimal.as_integer_ratio() change
type: behavior
versions: Python 3.6
Added file: http://bugs.python.org/file41446/statistics_as_integer_ratio.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25974>
_______________________________________

From report at bugs.python.org  Tue Dec 29 09:07:58 2015
From: report at bugs.python.org (Alex)
Date: Tue, 29 Dec 2015 14:07:58 +0000
Subject: [New-bugs-announce] [issue25975] Weird multiplication
Message-ID: <1451398078.33.0.133330943524.issue25975@psf.upfronthosting.co.za>


New submission from Alex:

Hi!
I'm nube and just learning, but found weird thing
50000 * 1.1 equals 55000.00000000001, but that's not wright.
I'm using 3.5.1 Shell. My friend checked - his got the same result.
So is it a bug or a feature?

----------
components: IDLE, Windows
messages: 257187
nosy: LCK, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Weird multiplication
type: behavior
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25975>
_______________________________________

From report at bugs.python.org  Tue Dec 29 10:18:00 2015
From: report at bugs.python.org (Mark McDonnell)
Date: Tue, 29 Dec 2015 15:18:00 +0000
Subject: [New-bugs-announce] [issue25976] telnetlib SyntaxError: invalid
 syntax
Message-ID: <1451402280.42.0.827762458184.issue25976@psf.upfronthosting.co.za>


New submission from Mark McDonnell:

I'm trying to use telnetlib in a simple script similar to the example show in the documentation. I get an error saying SyntaxError: invalid syntax. This is true with Windows 10, and XP, both using Python 2.7.11 32 bit.

Here's what happens in IDLE:
>>> import sys
>>> import telnetlib
>>> tn = telnetlib.Telnet(host=192.168.1.15, port=3490, timeout=5)
SyntaxError: invalid syntax
>>> tn = telnetlib.Telnet(192.168.1.15, 3490, 5)
SyntaxError: invalid syntax
>>> tn = telnetlib.Telnet(192.168.1.15)
SyntaxError: invalid syntax
>>> tn = telnetlib.Telnet(host=192.168.1.15, port=3490, timeout=5)

----------
components: Windows
messages: 257193
nosy: Mark McDonnell, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: telnetlib SyntaxError: invalid syntax
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25976>
_______________________________________

From report at bugs.python.org  Tue Dec 29 18:10:40 2015
From: report at bugs.python.org (John Walker)
Date: Tue, 29 Dec 2015 23:10:40 +0000
Subject: [New-bugs-announce] [issue25977] Typo fixes in Lib/tokenize.py
Message-ID: <1451430640.35.0.717826644288.issue25977@psf.upfronthosting.co.za>


New submission from John Walker:

Minor fixes to comments and a docstring in Lib/tokenize.py I found while looking for more important bugs.

afer -> after
alternately -> alternatively
intput -> input
argment -> argument

----------
assignee: docs at python
components: Documentation
files: tokenize-fixes.patch
keywords: patch
messages: 257217
nosy: docs at python, johnwalker
priority: normal
severity: normal
status: open
title: Typo fixes in Lib/tokenize.py
type: enhancement
versions: Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41449/tokenize-fixes.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25977>
_______________________________________

From report at bugs.python.org  Tue Dec 29 20:37:40 2015
From: report at bugs.python.org (Kiran Kotari)
Date: Wed, 30 Dec 2015 01:37:40 +0000
Subject: [New-bugs-announce] [issue25978] escape sequence r'\' giving
 compilation error
Message-ID: <1451439460.18.0.677316524926.issue25978@psf.upfronthosting.co.za>


New submission from Kiran Kotari:

>>> '\test'.lstrip(r'\')
	       
SyntaxError: EOL while scanning string literal

----------
components: 2to3 (2.x to 3.x conversion tool)
messages: 257221
nosy: Kiran Kotari
priority: normal
severity: normal
status: open
title: escape sequence r'\' giving compilation error
type: compile error
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25978>
_______________________________________

From report at bugs.python.org  Tue Dec 29 21:11:39 2015
From: report at bugs.python.org (Kiran Kotari)
Date: Wed, 30 Dec 2015 02:11:39 +0000
Subject: [New-bugs-announce] [issue25979] String functions lstrip are not
 working properly when you have escape sequence
Message-ID: <1451441499.87.0.305114938652.issue25979@psf.upfronthosting.co.za>


New submission from Kiran Kotari:

In this python code I am collecting list of folders present in the given location path with parent folder and print the folder names (output went wrong due to escape sequence values with lstrip.)
Note :
"\a \b \f \r \v \0 \1" are working fine. 
"\c \e \n \ne \t \te" went wrong.

Folder Structure : 
parent ->
      cat
      eat
      east
      next
      nest
      test

Wrong Output :
Path: .\parent\, List:  ['cat', 'st', '', 'st', 'xt', 'st']

----------
components: 2to3 (2.x to 3.x conversion tool)
files: string_fun_error.py
messages: 257223
nosy: Kiran Kotari
priority: normal
severity: normal
status: open
title: String functions lstrip are not working properly when you have escape sequence
type: behavior
versions: Python 3.5
Added file: http://bugs.python.org/file41450/string_fun_error.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25979>
_______________________________________

From report at bugs.python.org  Wed Dec 30 05:15:37 2015
From: report at bugs.python.org (Kiran Kotari)
Date: Wed, 30 Dec 2015 10:15:37 +0000
Subject: [New-bugs-announce] [issue25980] not able to find module request in
 lib urllib - Python35-32
Message-ID: <1451470537.42.0.459983444208.issue25980@psf.upfronthosting.co.za>


New submission from Kiran Kotari:

Python 3.5.1 documentation code giving following error:

Error: 
Traceback (most recent call last):
  File ".\urllib1.py", line 5, in <module>
    with urllib.request.urlopen('http://www.py4inf.com/code/romeo.txt') as f:
AttributeError: module 'urllib' has no attribute 'request'

Python Code:

import urllib
with urllib.request.urlopen('http://www.py4inf.com/code/romeo.txt') as f:
    print(f.read())

----------
components: Library (Lib)
messages: 257230
nosy: Kiran Kotari
priority: normal
severity: normal
status: open
title: not able to find module request in lib urllib - Python35-32
type: behavior
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25980>
_______________________________________

From report at bugs.python.org  Wed Dec 30 15:05:39 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Dec 2015 20:05:39 +0000
Subject: [New-bugs-announce] [issue25981] Intern namedtuple field names
Message-ID: <1451505939.05.0.983054710729.issue25981@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

If intern field names in namedtuple, this will speed up the access to them, because names could be compared just by identity in dict lookup. This can also make pickles containing namedtuples more compact.

----------
assignee: rhettinger
components: Library (Lib)
files: namedtuple_intern_field_names.patch
keywords: patch
messages: 257238
nosy: rhettinger, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Intern namedtuple field names
type: enhancement
versions: Python 3.6
Added file: http://bugs.python.org/file41452/namedtuple_intern_field_names.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25981>
_______________________________________

From report at bugs.python.org  Wed Dec 30 19:54:56 2015
From: report at bugs.python.org (Davin Potts)
Date: Thu, 31 Dec 2015 00:54:56 +0000
Subject: [New-bugs-announce] [issue25982] multiprocessing docs for Namespace
 lacks class definition
Message-ID: <1451523296.03.0.873921755549.issue25982@psf.upfronthosting.co.za>


New submission from Davin Potts:

In the docs, references to :class:`Namespace` can not be matched by Sphinx to any class definition because there isn't one in the doc.  It should be placed in the "Namespace objects" subsection and the initial descriptive para moved inside to describe it.

This is mostly a reminder to myself to make this quick fix.

----------
assignee: davin
messages: 257245
nosy: davin
priority: low
severity: normal
stage: needs patch
status: open
title: multiprocessing docs for Namespace lacks class definition
type: enhancement
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25982>
_______________________________________

From report at bugs.python.org  Thu Dec 31 10:32:24 2015
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 31 Dec 2015 15:32:24 +0000
Subject: [New-bugs-announce] [issue25983] Add tests for multi-argument type()
Message-ID: <1451575944.98.0.12158451128.issue25983@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

I had not added tests for issue25961 because couldn't find a good place for adding new tests. It looks that there are no special tests for creating new type with type() at all.

Proposed patch adds separate class with tests in test_builtin (may be this is not the best place, I'm not sure). They test type() with valid and invalid arguments, and also test setting some attributes, because error handling should be consistent for constructor and setters. There are some of setting tests in test_descr, but this doesn't look a good place for testing the constructor.

----------
components: Tests
files: type_tests.patch
keywords: patch
messages: 257257
nosy: serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Add tests for multi-argument type()
type: enhancement
versions: Python 2.7, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41461/type_tests.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25983>
_______________________________________

From report at bugs.python.org  Thu Dec 31 15:59:50 2015
From: report at bugs.python.org (random832)
Date: Thu, 31 Dec 2015 20:59:50 +0000
Subject: [New-bugs-announce] [issue25984] Expose a simple "is IEEE 754" flag
 in sys.float_info
Message-ID: <1451595590.68.0.197113034584.issue25984@psf.upfronthosting.co.za>


New submission from random832:

I think it would be useful for programs to be able to detect whether a system uses IEEE-754 double-precision values for the 'float' type. There is lots of detailed information about the float type in sys.float_info, but no simple "is IEEE" flag. On some C implementations, this is exposed as __STDC_IEC_559__.

----------
messages: 257260
nosy: random832
priority: normal
severity: normal
status: open
title: Expose a simple "is IEEE 754" flag in sys.float_info

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25984>
_______________________________________