[issue26638] Avoid warnings about missing CLI options when building documentation

[Roundup Robot]

Roundup Robot added the comment:

New changeset 23a884c32a39 by Martin Panter in branch '3.5':
Issue #26638: Fix links to some CLI options and section headings
https://hg.python.org/cpython/rev/23a884c32a39

New changeset 68b84643dffd by Martin Panter in branch 'default':
Issue #26638: Merge link fixes from 3.5
https://hg.python.org/cpython/rev/68b84643dffd

New changeset 3e0321584f23 by Martin Panter in branch '2.7':
Issue #26638: Fix links to some CLI options
https://hg.python.org/cpython/rev/3e0321584f23

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26776] Determining the failure of C API call is ambiguous

[Serhiy Storchaka]

New submission from Serhiy Storchaka:

C API functions returns a special value unambiguously signaling about a raised 
exception (NULL or -1). But in some cases this is ambiguous, because the 
special value is a legitimate value (e.g. -1 for PyLong_AsLong() or NULL for 
PyDict_GetItem()). Needed to use PyErr_Occurred() to distinguish between 
successful and failed call.

The problem is that if PyLong_AsLong() is called when the exception is set, 
successful call returned -1 is interpreted as failed. Since it is happen in 
very rare case, this bug is usually unnoticed.

Attached experimental patch makes some functions like PyLong_AsLong() always 
failing if called with an exception set. Some tests are failed with it applied: 
test_compile test_datetime test_io test_os test_symtable test_syntax 
test_xml_etree_c.

--
components: Interpreter Core
files: check_error_occurred.patch
keywords: patch
messages: 263540
nosy: haypo, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Determining the failure of C API call is ambiguous
Added file: http://bugs.python.org/file42478/check_error_occurred.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26764] SystemError in bytes.__rmod__

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
resolution:  -> fixed
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26753] Obmalloc lock LOCK_INIT and LOCK_FINI are never used

[Larry Hastings]

Larry Hastings added the comment:

Patch attached.  The basics were okay; however, there was no locking around 
access to a static variable (_Py_AllocatedBlocks) so I added some.  The way the 
code managed _Py_AllocatedBlocks was a bit odd; this approach resulted in fewer 
lines, but it was hard to follow, and adding locking support would have muddied 
it even further, so I simplified it.  I also simplified the locking support a 
great deal ("SIMPLELOCK": YAGNI) and touched up the relevant comment.

Finally, I noticed a minor bug wrt added _Py_AllocatedBlocks: if you call 
PyMem_Realloc(NULL, 5), that's really a new allocation, so 
_Py_AllocatedBlocks needs to be incremented, but it wasn't.  Since Antoine is 
the father of _Py_AllocatedBlocks I added him to the nosy list.

--
nosy: +pitrou

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26753] Obmalloc lock LOCK_INIT and LOCK_FINI are never used

[Larry Hastings]

Larry Hastings added the comment:

Oy veh, in editing the issue I dropped the attached file.  Here it is.

--
keywords: +patch
Added file: 
http://bugs.python.org/file42479/larry.refresh.lock.macros.for.obmalloc.diff

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26774] Elide Py_atomic fences when WITH_THREAD is disabled?

[STINNER Victor]

STINNER Victor added the comment:

I never liked the option to disable thread support. I don't think that
anyone uses it but it requires many #ifdef in the code. I would prefer to
drop the option.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26776] Determining the failure of C API call is ambiguous

[STINNER Victor]

STINNER Victor added the comment:

Ah yes. Some months (years?) ago, i started to add assertions to fail if
some functions are called with an exception set.

Checking if an exception is set at runtime adds a low overhead. Maybe it's
better to fail with a fatal error (like an assertion error) in debug mode
(and do nothing in release mode).

But I'm not sure that developers of C extensions are all able to get a
Python compiled in debug mode :-/ That's also why I added a check a
runtime: raise a SystemError if a function with an exception set. I also
added PYTHONMALLOC=debug to make some debug checks easily available on
release builds.

The bug also reminds me my PEP 490 to chain exceptions. It would be
yet another option...

So well, I don't know what is the best option.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26470] Make OpenSSL module compatible with OpenSSL 1.1.0

[Bernard Spil]

Bernard Spil added the comment:

Testing this patch on HardenedBSD/LibreSSL (base SSL libs replaced with 
LibreSSL)

--
nosy: +spil

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26470] Make OpenSSL module compatible with OpenSSL 1.1.0

[Bernard Spil]

Bernard Spil added the comment:

Checking version numbers to see if a feature is available is a bad practice. 
How can features ever be removed this way! Would be better to check for the 
feature itself (using autoconf).

The patch was mostly OK but any check for OPENSSL_VERSION_NUMBER for now also 
requires a negative check for LIBRESSL_VERSION_NUMBER as LibreSSL froze 
features at 1.0.1g.

Next to that, anything requiring compression (CRIME attack) should be guarded 
using and #infdef OPENSSL_NO_COMP.

This patch allowed me to build Python 3.5 with LibreSSL 2.3 (i.e. without 
SSLv3, Compression, RC4, SHA-0, etc)

--
Added file: 
http://bugs.python.org/file42480/patch-lang_python35-OpenSSL-1.1.0+LibreSSL

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26638] Avoid warnings about missing CLI options when building documentation

[Martin Panter]

Martin Panter added the comment:

I committed the parts of my patch that improve real links in the end result.

doc-warnings.v2.patch has the remaining changes which add exclamation marks to 
mask undefined options.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26638] Avoid warnings about missing CLI options when building documentation

[Martin Panter]

Changes by Martin Panter :


Added file: http://bugs.python.org/file42481/doc-warnings.v2.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26638] Avoid warnings about missing CLI options when building documentation

[Martin Panter]

Martin Panter added the comment:

This patch disables the warning, but I tend to think it is not a good long-term 
solution.

--
Added file: http://bugs.python.org/file42482/disable-warning.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10838] subprocess __all__ is incomplete

[Roundup Robot]

Roundup Robot added the comment:

New changeset cb38866e4c13 by Martin Panter in branch '3.5':
Issue #10838: Run test__all__() everywhere, even if poll() is not available
https://hg.python.org/cpython/rev/cb38866e4c13

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26777] test_asyncio: test_timeout_disable() fails randomly

[STINNER Victor]

New submission from STINNER Victor:

On the "AMD64 FreeBSD 9.x 3.5" buildbot, test_timeout_disable() fails randomly.

http://buildbot.python.org/all/builders/AMD64%20FreeBSD%209.x%203.5/builds/701/steps/test/logs/stdio

==
FAIL: test_timeout_disable (test.test_asyncio.test_tasks.TimeoutTests)
--
Traceback (most recent call last):
  File 
"/usr/home/buildbot/python/3.5.koobs-freebsd9/build/Lib/test/test_asyncio/test_tasks.py",
 line 2399, in test_timeout_disable
self.loop.run_until_complete(go())
  File 
"/usr/home/buildbot/python/3.5.koobs-freebsd9/build/Lib/asyncio/base_events.py",
 line 379, in run_until_complete
return future.result()
  File 
"/usr/home/buildbot/python/3.5.koobs-freebsd9/build/Lib/asyncio/futures.py", 
line 274, in result
raise self._exception
  File 
"/usr/home/buildbot/python/3.5.koobs-freebsd9/build/Lib/asyncio/tasks.py", line 
240, in _step
result = coro.send(None)
  File 
"/usr/home/buildbot/python/3.5.koobs-freebsd9/build/Lib/test/test_asyncio/test_tasks.py",
 line 2398, in go
self.assertTrue(0.09 < dt < 0.11, dt)
AssertionError: False is not true : 0.11916078114882112

--
components: Tests, asyncio
keywords: buildbot
messages: 263550
nosy: gvanrossum, haypo, yselivanov
priority: normal
severity: normal
status: open
title: test_asyncio: test_timeout_disable() fails randomly
versions: Python 3.5, Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25942] subprocess.call SIGKILLs too liberally

[Martin Panter]

Martin Panter added the comment:

I don’t think Victor likes #2 because of the zombie. I would be interested in 
#4 (one of the documented purposes of subprocess is to replace os.system), but 
it might need careful consideration and discussion. Ignoring signals is such a 
significant change I think it would have to be a new feature for 3.6+ only.

Mike/Victor, what do you think of my proposal (call it #6) about waiting a 
second time before resorting to SIGKILL? Posting a patch which implements this.

--
Added file: http://bugs.python.org/file42483/second-wait.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26778] More typo fixes

[Serhiy Storchaka]

New submission from Serhiy Storchaka:

Proposed patch fixes a number of typos (mainly about misusing "a/an") in the 
docs, docstrings, comments and error messages.

--
files: typos.patch
keywords: patch
messages: 263552
nosy: martin.panter, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: More typo fixes
type: enhancement
versions: Python 2.7, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file42484/typos.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26778] More typo fixes

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


Removed file: http://bugs.python.org/file42484/typos.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26778] More typo fixes

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


Added file: http://bugs.python.org/file42485/typos.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26779] pdb continue followed by an exception in the same frame shows incorrect frame linenumber

[Sriram Rajagopalan]

New submission from Sriram Rajagopalan:

Consider this simple python program - 

  1 #!/usr/bin/python
  2
  3 import pdb
  4 import sys
  5 import traceback
  6
  7 def trace_exception( type, value, tb ):
  8 traceback.print_tb( tb )
  9 pdb.post_mortem( tb )
 10
 11 sys.excepthook = trace_exception
 12
 13 def func():
 14 print ( "Am here in func" )
 15 pdb.set_trace()
 16 print ( "Am here after pdb" )
 17 print ( "Am going to assert now" )
 18 assert False
 19 print ( "Am here after exception" )
 20
 21 def main():
 22 func()
 23
 24 if __name__ == "__main__":
 25 main()


On running this program - 

% ./python /tmp/test.py
Am here in func
> /tmp/test.py(16)func()
-> print ( "Am here after pdb" )
(Pdb) c
Am here after pdb
Am going to assert now
  File "/tmp/test.py", line 25, in 
main()
  File "/tmp/test.py", line 22, in main
func()
  File "/tmp/test.py", line 16, in func
print ( "Am here after pdb" )
> /tmp/test.py(16)func()
-> print ( "Am here after pdb" )  This should have been at the line 
corresponding to "Am going to assert now"
(Pdb)


This seems to be an bug ( due to a performance consideration ) with the way 
python bdb's set_continue() has been implemented -

https://hg.python.org/cpython/file/2.7/Lib/bdb.py#l227

def set_continue(self):
# Don't stop except at breakpoints or when finished
self._set_stopinfo(self.botframe, None, -1)
if not self.breaks:
# no breakpoints; run without debugger overhead
sys.settrace(None)
frame = sys._getframe().f_back
while frame and frame is not self.botframe:
del frame.f_trace
frame = frame.f_back

Basically what happens after "c" in a "(Pdb)" prompt is that bdb optimizes for 
the case where there are no more break points found by cleaning up the trace 
callback from all the frames.

However, all of this happens in the context of tracing itself and hence the 
trace_dispatch function in 
https://hg.python.org/cpython/file/2.7/Lib/bdb.py#l45 still returns back the 
trace_dispatch as the new system trace function. For more details on 
sys.settrace(), check https://docs.python.org/2/library/sys.html#sys.settrace

Check, the function trace_trampoline at 
https://hg.python.org/cpython/file/2.7/Python/sysmodule.c#l353
which sets f->f_trace back to result at 
https://hg.python.org/cpython/file/2.7/Python/sysmodule.c#l377

This seems to be an bug ( due to a performance consideration ) with the way 
python bdb's set_continue() has been implemented -

https://hg.python.org/cpython/file/2.7/Lib/bdb.py#l227

def set_continue(self):
# Don't stop except at breakpoints or when finished
self._set_stopinfo(self.botframe, None, -1)
if not self.breaks:
# no breakpoints; run without debugger overhead
sys.settrace(None)
frame = sys._getframe().f_back
while frame and frame is not self.botframe:
del frame.f_trace
frame = frame.f_back

Basically what happens after "c" in a "(Pdb)" prompt is that bdb optimizes for 
the case where there are no more break points found by cleaning up the trace 
callback from all the frames.

However, all of this happens in the context of tracing itself and hence the 
trace_dispatch function in 
https://hg.python.org/cpython/file/2.7/Lib/bdb.py#l45 still returns back the 
trace_dispatch as the new system trace function. For more details on 
sys.settrace(), check https://docs.python.org/2/library/sys.html#sys.settrace

Check, the function trace_trampoline at 
https://hg.python.org/cpython/file/2.7/Python/sysmodule.c#l353
which sets f->f_trace back to result at 
https://hg.python.org/cpython/file/2.7/Python/sysmodule.c#l377

Now, check the function PyFrame_GetLineNumber() which is used by the traceback 
to get the frame line number 
https://hg.python.org/cpython/file/2.7/Objects/frameobject.c#l63

int
PyFrame_GetLineNumber(PyFrameObject *f)
{
if (f->f_trace)
return f->f_lineno;
else
return PyCode_Addr2Line(f->f_code, f->f_lasti);
}

Basically this function returns back the stored f->f_lineno in case the 
f->f_trace is enabled.

The fix is fortunately simple - 

Just set self.trace_dispatch to None if pdb set_continue decides to run without 
debugger overhead.

--
components: Library (Lib)
files: bdbfix.patch
keywords: patch
messages: 263553
nosy: Sriram Rajagopalan
priority: normal
severity: normal
status: open
title: pdb continue followed by an exception in the same frame shows incorrect 
frame linenumber
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/file42486/bdbfix.patch

___
Python tracker 

___
___
Python-bugs-list mailing l

[issue26779] pdb continue followed by an exception in the same frame shows incorrect frame linenumber

[SilentGhost]

Changes by SilentGhost :


--
nosy: +georg.brandl
versions:  -Python 3.2, Python 3.3, Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26779] pdb continue followed by an exception in the same frame shows incorrect frame linenumber

[Senthil Kumaran]

Changes by Senthil Kumaran :


--
nosy: +orsenthil

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26780] Illustrate both binary operator conventions in PEP-8

[Brandon Rhodes]

New submission from Brandon Rhodes:

I am delighted to see that PEP-8 has pivoted to breaking long formulae before, 
rather than after, each binary operator! But I would like to pivot the PEP away 
from citing my own PyCon Canada talk as the authority on the matter, and toward 
citing Knuth himself. It would also be an enhancement for the PEP to show both 
options and make an argument for the practice, instead of simply asserting that 
one is better than the other. I therefore propose the attached patch.

--
assignee: docs@python
components: Documentation
files: pep8-knuth.patch
keywords: patch
messages: 263554
nosy: barry, brandon-rhodes, docs@python, gvanrossum
priority: normal
severity: normal
status: open
title: Illustrate both binary operator conventions in PEP-8
Added file: http://bugs.python.org/file42487/pep8-knuth.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26778] More typo fixes

[Martin Panter]

Martin Panter added the comment:

Should exception messages be corrected in old versions, or just 3.6?

Apart from the few changes with comments, the rest look good to me.

I found some more cases (my patch is independent of Serhiy’s).

--
Added file: http://bugs.python.org/file42488/an-consonant.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26780] Illustrate both binary operator conventions in PEP-8

[Brandon Rhodes]

Changes by Brandon Rhodes :


Removed file: http://bugs.python.org/file42487/pep8-knuth.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26780] Illustrate both binary operator conventions in PEP-8

[Brandon Rhodes]

Changes by Brandon Rhodes :


Added file: http://bugs.python.org/file42489/pep8-knuth.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26781] os.walk max_depth

[Aviv Palivoda]

New submission from Aviv Palivoda:

I am suggesting to add max_depth argument to os.walk. I think this is very 
useful for two cases. The trivial one is when someone wants to walk on a 
directory tree up to specific depth. The second one is when you follow symlinks 
and wish to avoid infinite loop.

The patch add the max_depth both to os.walk and os.fwalk.

--
components: Library (Lib)
files: os-walk-max-depth.patch
keywords: patch
messages: 263556
nosy: loewis, palaviv
priority: normal
severity: normal
status: open
title: os.walk max_depth
type: enhancement
versions: Python 3.6
Added file: http://bugs.python.org/file42490/os-walk-max-depth.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26782] subprocess.__all__ incomplete on Windows

[Martin Panter]

New submission from Martin Panter:

After enabling test__all__() in test_subprocess on Windows (see Issue 10838), I 
find that STARTUPINFO is missing from __all__, and there is a class Handle that 
is ambiguous. Handle doesn’t seem to be documented, so I propose to add it to 
the intentionally-excluded list.

In Python 3.5 I will fix the test to exclude STARTUPINFO from __all__.

--
components: Windows
files: subprocess-all.patch
keywords: patch
messages: 263557
nosy: martin.panter, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
stage: patch review
status: open
title: subprocess.__all__ incomplete on Windows
versions: Python 3.6
Added file: http://bugs.python.org/file42491/subprocess-all.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26783] test_os.WalkTests.test_walk_topdown don't test fwalk and Bytes

[Aviv Palivoda]

New submission from Aviv Palivoda:

test_walk_topdown call os.walk directly instead of using self.walk. This test 
currently run 3 time's while checking the same thing. The test should use 
self.walk to check fwalk and Bytes as well.

--
components: Tests
files: os-test-walk-topdown-use-self-walk.patch
keywords: patch
messages: 263558
nosy: loewis, palaviv
priority: normal
severity: normal
status: open
title: test_os.WalkTests.test_walk_topdown don't test fwalk and Bytes
versions: Python 3.6
Added file: 
http://bugs.python.org/file42492/os-test-walk-topdown-use-self-walk.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26775] Improve test coverage on urllib.parse

[Roundup Robot]

Roundup Robot added the comment:

New changeset 8f02747ff908 by Senthil Kumaran in branch '3.5':
issue26775 - Improve test coverage for urllib.parse
https://hg.python.org/cpython/rev/8f02747ff908

New changeset 401dca6ac084 by Senthil Kumaran in branch 'default':
merge 3.5
https://hg.python.org/cpython/rev/401dca6ac084

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26778] More typo fixes

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Thank you all for your reviews. Martin's patch LGTM.

I agree that it would be safer to not change error messages in bugfix releases. 
Here is consolidated patch with fixed errors.

--
Added file: http://bugs.python.org/file42493/typos2.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26775] Improve test coverage on urllib.parse

[Senthil Kumaran]

Senthil Kumaran added the comment:

Thanks for your contribution, Luiz. It's a useful improvement.
Committed to all active branches.

2.7 changeset: 101012:e3ed950ad728

--
nosy: +orsenthil
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
versions: +Python 2.7, Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10838] subprocess __all__ is incomplete

[Martin Panter]

Martin Panter added the comment:

See Issue 26782 for a follow-up with Windows.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26783] test_os.WalkTests.test_walk_topdown don't test fwalk and Bytes

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

The patch LGTM. Thank you Aviv.

--
assignee:  -> serhiy.storchaka
nosy: +serhiy.storchaka
stage:  -> commit review
type:  -> behavior
versions: +Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26783] test_os.WalkTests.test_walk_topdown don't test fwalk and Bytes

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
resolution:  -> fixed
stage: commit review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26783] test_os.WalkTests.test_walk_topdown don't test fwalk and Bytes

[Roundup Robot]

Roundup Robot added the comment:

New changeset e44a2dc62c11 by Serhiy Storchaka in branch '3.5':
Issue #26783: test_os.WalkTests.test_walk_topdown did't test fwalk and bytes.
https://hg.python.org/cpython/rev/e44a2dc62c11

New changeset be96434b8777 by Serhiy Storchaka in branch 'default':
Issue #26783: test_os.WalkTests.test_walk_topdown did't test fwalk and bytes.
https://hg.python.org/cpython/rev/be96434b8777

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26781] os.walk max_depth

[random832]

random832 added the comment:

Wouldn't the "symlink infinite loop" case be better handled by making it track 
where it's already been? This can be done by inode and dev number on Unix; I'm 
not sure what equivalent exists on Windows (though symlinks are uncommon on 
Windows) but you could fall back on realpath.

--
nosy: +random832

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue17859] improve error message for saving ints to file

[random832]

random832 added the comment:

This bug should be closed since #16518 was accepted and the error is now 
"TypeError: a bytes-like object is required, not 'int'"

--
nosy: +random832

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue17859] improve error message for saving ints to file

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
resolution:  -> duplicate
stage: needs patch -> resolved
status: open -> closed
superseder:  -> add "buffer protocol" to glossary

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24922] assertWarnsRegex doesn't allow multiple warning messages

[Berker Peksag]

Changes by Berker Peksag :


--
components: +Library (Lib) -Interpreter Core
type: behavior -> enhancement
versions:  -Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26784] regular expression problem at umlaut handling

[Marcus]

New submission from Marcus:

Working with this example string "E-112233-555-11 | Bläh - Bläh" with the 
following code leeds under python 2.7.10 (OSX) to an exception whereas the same 
code works under python 3.5.1 (OSX).

s = "E-112233-555-11 | Bläh - Bläh"

expr = re.compile(r"(?P[A-Z]{1}-[0-9]{0,}(-[0-9]{0,}(-[0-9]{0,})?)?)?(( [|] 
)?(?P[\s\w]*)?)? - (?P[\s\w]*)?",re.UNICODE)
res = re.match(expr,s)
a = (res.group('p'), res.group('a'), res.group('j'))
print(a)


When I change the first umlaut in "Bläh" from ä to ü it works as expected on 
python 2 and 3. A change from ä to ö however leeds to a crash again.

Ideas?

--
messages: 263567
nosy: arbyter
priority: normal
severity: normal
status: open
title: regular expression problem at umlaut handling
type: behavior
versions: Python 2.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26784] regular expression problem at umlaut handling

[SilentGhost]

Changes by SilentGhost :


--
components: +Regular Expressions
nosy: +ezio.melotti, mrabarnett, pitrou, serhiy.storchaka

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue20739] PEP 463 (except expression) implementation

[Berker Peksag]

Changes by Berker Peksag :


--
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21274] define PATH_MAX for GNU/Hurd in Python/pythonrun.c

[Berker Peksag]

Berker Peksag added the comment:

Python 3.4 is in security-fix-only mode so we can close this now.

--
nosy: +berker.peksag
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26784] regular expression problem at umlaut handling

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

First, in the context of Python a crash means a core dump or an analogue on 
Windows. In this case the code just works not as you expected.

The short answer: s should be a unicode.

In your code "ä" is encoded as 8-bit string '\xc3\xa4'. When matched, every 
bytes is independently expanded to Unicode range. The first byte becomes 
u'\xc3' = u'Ã', the second byte becomes u'¤', non-alphanumeric. '[\s\w]*' 
doesn't match u'ä'.

"ü" is encoded as 8-bit string '\xc3\xbc'. The second byte becomes u'¼', 
numeric. '[\s\w]*' matches u'ü'.

--
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26784] regular expression problem at umlaut handling

[Marcus]

Marcus added the comment:

Thx for your explanation. You explained why [\s\w] didn't match for "ä". In my 
situation it didn't matches for the first "ä" but the second time I used [\s\w] 
in the same regex it matched at the second "ä". What's the explanation for this?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24922] assertWarnsRegex doesn't allow multiple warning messages

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

I think there is a little need for this feature. On other hand, its use looks 
complicated, and it will likely complicate the implementation.

If tested types are same, but messages differ, messages can be combined in on 
regex: 'msg1|msg2'.

If tested types differ, but messages are same, this case is already supported.

If tested types and messages differ, you can test with combined regex, and then 
check a context manager object that the message matches the type. But this is 
very rare case.

--
nosy: +serhiy.storchaka

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26784] regular expression problem at umlaut handling

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Sorry, I don't understand you. If the regex failed to match the first "ä", it 
can't match the second "ä". Do you have an example?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26780] Illustrate both binary operator conventions in PEP-8

[Brandon Rhodes]

Brandon Rhodes added the comment:

Another important objection against the current text is that it stacks a series 
of `and` and `or` operators at the same level of indentation, as though they 
naturally evaluate in the order the programmer writes them. In fact, they have 
different levels of precedence, and the code example violates the other 
sections of PEP-8 that ask for the creation of a visual distinction in code 
between different precedence levels.

The example needs to pivot towards a series of operators which belong at the 
same precedence level. I have used `+` and `-` because they seemed more natural 
to form an example from than something like division and multiplication.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26780] Illustrate both binary operator conventions in PEP-8

[Brandon Rhodes]

Changes by Brandon Rhodes :


--
type:  -> enhancement

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24922] assertWarnsRegex doesn't allow multiple warning messages

[Berker Peksag]

Berker Peksag added the comment:

Agreed. Let's close this then.

--
nosy: +berker.peksag
resolution:  -> rejected
stage: needs patch -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26784] regular expression problem at umlaut handling

[Marcus]

Marcus added the comment:

When I replace the first "ä" with a random letter the untouched expression has 
not problems to match the second word which contains also an "ä"

s = "E-112233-555-11 | Bläh - Bläh" #untuched string
s = "E-112233-555-11 | Bloh - Bläh" #string where the first ä is replaced by an 
"o"

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26781] os.walk max_depth

[Aviv Palivoda]

Changes by Aviv Palivoda :


Added file: http://bugs.python.org/file42494/os-walk-max-depth-2.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26785] repr of -nan value should contain the sign

[Hrvoje Abraham]

New submission from Hrvoje Abraham:

repr of -nan value should contain the sign so the round-trip could be assured. 
NaN value sign (bit) could be seen as not relevant or even uninterpretable 
information, but it is actually used in real-life situations, the fact 
substantiated by section 6.3 of IEEE-754 2008 standard.

>>> from math import copysign
>>> x = float("-nan")
>>> copysign(1.0, x)
-1.0

This is correct. Also proves the value contains the sign information.

>>> repr(x)
nan

Not correct. Should be '-nan'.

--
components: Interpreter Core
messages: 263576
nosy: ahrvoje
priority: normal
severity: normal
status: open
title: repr of -nan value should contain the sign
type: behavior
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26784] regular expression problem at umlaut handling

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Because "[\s\w]*" matches only a part of "Bläh": "Bl\xc3".

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26785] repr of -nan value should contain the sign

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
nosy: +mark.dickinson

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue23029] test_warnings produces extra output in quiet mode

[Roundup Robot]

Roundup Robot added the comment:

New changeset 009e36e6d16d by Berker Peksag in branch '2.7':
Issue #23029: Fix catch_warnings() in test_filename_none
https://hg.python.org/cpython/rev/009e36e6d16d

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue23029] test_warnings produces extra output in quiet mode

[Berker Peksag]

Changes by Berker Peksag :


--
nosy: +berker.peksag
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26781] os.walk max_depth

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

os.walk() allows more flexible control.

for root, dirs, files in os.walk(top):
if is_too_deep(root):
dirs.clear()
continue
...

You can even walk up to different depth on different parts of the tree. You can 
limit walking not by the directory depth, but by the length of the path, or the 
number of links in the path, or what-you-need. Adding separate parameters for 
all this particular cases is not practical.

I think there is a little need in this feature.

--
nosy: +serhiy.storchaka

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25731] Assigning and deleting __new__ attr on the class does not allow to create instances of this class

[Benjamin Peterson]

Benjamin Peterson added the comment:

I believe the correct behavior is actually

Traceback (most recent call last):
  File "", line 1, in 
  File "bar.py", line 7, in 
C()
TypeError: foo.A.__new__(C) is not safe, use foo.B.__new__()

This is because A comes before B in the mro, and, indeed, constructing C with 
A.__new__ is unsafe. In fact, reordering A and B in the definition of C fixes 
everything.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25989] documentation version switcher is broken fro 2.6, 3.2, 3.3

[Berker Peksag]

Berker Peksag added the comment:

Thanks for the report, but as I said in the GitHub issue, the version switcher 
works as expected (we don't build docs of security-only-fix branches).

--
nosy: +berker.peksag
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue13340] list.index does not accept None as start or stop

[Berker Peksag]

Berker Peksag added the comment:

See http://thread.gmane.org/gmane.comp.python.devel/127502 for the python-dev 
thread.

--
nosy: +berker.peksag
versions: +Python 3.6 -Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26785] repr of -nan value should contain the sign

[Hrvoje Abraham]

Hrvoje Abraham added the comment:

Reported issue was created in 64-bit Python 3.5.1 (v3.5.1:37a07cee5969, Dec  6 
2015, 01:54:25) [MSC v.1900 64 bit (AMD64)] on win32.

Now I noticed that in Py 2.7 even copysign part does not work as expected.

Python 2.7.11 (v2.7.11:6d1b6a68f775, Dec  5 2015, 20:40:30) [MSC v.1500 64 bit 
(AMD64)] on win32:

>>> from math import copysign
>>> x = float("-nan")
>>> copysign(1.0, x)
1.0

Not correct.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue15933] flaky test in test_datetime

[Berker Peksag]

Berker Peksag added the comment:

The assert was changed (somewhat similar to issue15933.diff) in bc67e8d39164. 
I've checked last 18 builds (from 800 to 818) on 
http://buildbot.python.org/all/builders/x86%20OpenIndiana%203.5 and test_today 
wasn't one of the failed tests. I'm closing this as outdated.

--
nosy: +berker.peksag
resolution:  -> out of date
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24173] curses HOWTO/implementation disagreement

[Roundup Robot]

Roundup Robot added the comment:

New changeset 5c9cda2bdfd2 by Berker Peksag in branch '2.7':
Issue #24173: Fix curses.wrapper link in curses HOWTO
https://hg.python.org/cpython/rev/5c9cda2bdfd2

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24173] curses HOWTO/implementation disagreement

[Berker Peksag]

Berker Peksag added the comment:

Thanks for the report! 3.x docs have already been updated.

--
nosy: +berker.peksag
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
type:  -> behavior

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7694] DeprecationWarnings in distutils are pointless

[Berker Peksag]

Berker Peksag added the comment:

> [...] I think the DeprecationWarnings in distutils should just be removed, as 
> they serve no useful purpose.

There are no DeprecationWarning warnings (only four PendingDeprecationWarning 
warnings -- two of them are for 'check_metadata') in distutils codebase in both 
2.7 and 3.x anymore.

Closing this as out of date.

--
nosy: +berker.peksag
resolution:  -> out of date
stage: needs patch -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25642] Setting maxsize breaks asyncio.JoinableQueue/Queue

[Berker Peksag]

Changes by Berker Peksag :


--
stage:  -> resolved
status: open -> closed
type: crash -> behavior

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19791] test_pathlib should use can_symlink or skip_unless_symlink from test.support

[Berker Peksag]

Changes by Berker Peksag :


--
nosy: +berker.peksag
stage:  -> patch review
type: behavior -> enhancement
versions: +Python 3.6 -Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26780] Illustrate both binary operator conventions in PEP-8

[Guido van Rossum]

Guido van Rossum added the comment:

Patch LGTM.

Note that the and/or example was in the PEP before this discussion broke out.

The discussion also at some point (before your Knuth quote was discovered) 
veered in the direction of making and/or a special case, perhaps because it's 
more likely that a long expression must be broken around and/or operators. And 
there were already examples of breaking after binary arithmetic operators 
elsewhere in the PEP (I think).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26571] turtle regression in 3.5

[Ellison Marks]

Ellison Marks added the comment:

Just as an update, I've been working around this by manually setting 
TurtleScreen._RUNNING to True before calling Turtle() again, which produces the 
desired behaviour in both 3.4 and 3.5. Haven't noticed any bad effects so far.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26751] Possible bug in sorting algorithm

[Benjamin Peterson]

Changes by Benjamin Peterson :


--
resolution:  -> not a bug
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26659] slice() leaks memory when part of a cycle

[Roundup Robot]

Roundup Robot added the comment:

New changeset 879da9400529 by Benjamin Peterson in branch '2.7':
add gc support to slice (closes #26659)
https://hg.python.org/cpython/rev/879da9400529

New changeset 9e2176d18965 by Benjamin Peterson in branch '3.5':
add gc support to slice (closes #26659)
https://hg.python.org/cpython/rev/9e2176d18965

New changeset 870fcc50f1bd by Benjamin Peterson in branch 'default':
merge 3.5 (#26659)
https://hg.python.org/cpython/rev/870fcc50f1bd

--
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26786] bdist_msi duplicates directories with names in ALL CAPS to a bogus location

[Ivan Pozdeev]

New submission from Ivan Pozdeev:

If a package has directories with names in APP CAPS, 
distutils.commands.bdist_msi creates properties for them that are also in all 
caps.

Such properties are handled specially by MSI and are called "public properties 
(http://www.advancedinstaller.com/user-guide/properties.html).

Due to the way bdist_msi-produced .msi's work, this ultimately results in 
subtrees of these directories being duplicated to a bogus location (the root 
directory of the drive on which the .msi being installed is).

E.g. in the attached example, all 
\Lib\mercurial\locale\\LC_MESSAGES subtrees got duplicated to 
D:\Lib\.

See https://bz.mercurial-scm.org/show_bug.cgi?id=5192 for details (including a 
high-level description of how bdist_msi packages work).

--
components: Distutils, Library (Lib), Windows
files: mercurial-3.3.2.log.gz
messages: 263591
nosy: Ivan.Pozdeev, dstufft, eric.araujo, paul.moore, steve.dower, tim.golden, 
zach.ware
priority: normal
severity: normal
status: open
title: bdist_msi duplicates directories with names in ALL CAPS to a bogus 
location
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/file42495/mercurial-3.3.2.log.gz

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26659] slice() leaks memory when part of a cycle

[Martin Panter]

Changes by Martin Panter :


--
versions: +Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26782] subprocess.__all__ incomplete on Windows

[Roundup Robot]

Roundup Robot added the comment:

New changeset 386712b16c74 by Martin Panter in branch '3.5':
Issue #26782: Acknowledge the incomplete status of __all__ in 3.5
https://hg.python.org/cpython/rev/386712b16c74

New changeset 728370e7a29d by Martin Panter in branch 'default':
Issue #26782: Merge test_subprocess from 3.5
https://hg.python.org/cpython/rev/728370e7a29d

New changeset 3e93ac5a7afa by Martin Panter in branch 'default':
Issue #26782: Add STARTUPINFO to subprocess.__all__ on Windows
https://hg.python.org/cpython/rev/3e93ac5a7afa

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26785] repr of -nan value should contain the sign

[Eric V. Smith]

Changes by Eric V. Smith :


--
nosy: +eric.smith

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26785] repr of -nan value should contain the sign

[Eric V. Smith]

Eric V. Smith added the comment:

Changing versions.

I left in 2.7, but I doubt we'd make any changes to 2.7 with regards to this.

--
versions:  -Python 3.2, Python 3.3

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26778] More typo fixes

[Martin Panter]

Martin Panter added the comment:

I think there are two outstanding problems; see Lib/tkinter/tix.py and 
Misc/HISTORY.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue23883] __all__ lists are incomplete

[Martin Panter]

Changes by Martin Panter :


--
dependencies: +subprocess.__all__ incomplete on Windows

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4806] Function calls taking a generator as star argument can mask TypeErrors in the generator

[Roundup Robot]

Roundup Robot added the comment:

New changeset eef8f72ddb00 by Martin Panter in branch '2.7':
Issue #4806: Avoid masking TypeError when *-unpacking a generator
https://hg.python.org/cpython/rev/eef8f72ddb00

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26717] wsgiref.simple_server: mojibake with cp1252 bytes in PATH_INFO

[Roundup Robot]

Roundup Robot added the comment:

New changeset 1f2cfcd5a83f by Martin Panter in branch '3.5':
Issue #26717: Stop encoding Latin-1-ized WSGI paths with UTF-8
https://hg.python.org/cpython/rev/1f2cfcd5a83f

New changeset 815a4ac67e68 by Martin Panter in branch 'default':
Issue #26717: Merge wsgiref fix from 3.5
https://hg.python.org/cpython/rev/815a4ac67e68

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26554] PC\bdist_wininst\install.c: Missing call to fclose()

[Josh Snider]

Josh Snider added the comment:

I suggested some changes to your patch. Your patch should also add your name to 
the Misc/ACKS file as I don't currently see an Aatish listed there.

--
nosy: +Josh Snider

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26782] subprocess.__all__ incomplete on Windows

[Martin Panter]

Changes by Martin Panter :


--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4806] Function calls taking a generator as star argument can mask TypeErrors in the generator

[Martin Panter]

Changes by Martin Panter :


--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26787] test_distutils fails when configured --with-lto

[Gregory P. Smith]

New submission from Gregory P. Smith:

When configured using './configure --with-lto' (added in issue25702) and doing 
a 'make profile-opt' build, test_distutils fails:

==
FAIL: test_sysconfig_compiler_vars 
(distutils.tests.test_sysconfig.SysconfigTestCase)
--
Traceback (most recent call last):
  File 
"/home/greg/sandbox/python/cpython/3.5/Lib/distutils/tests/test_sysconfig.py", 
line 156, in test_sysconfig_compiler_vars
sysconfig.get_config_var('LDSHARED'))
AssertionError: 'gcc -pthread -shared -flto -fuse-linker-plugin 
-ffat-lto-obje[20 chars]none' != 'gcc -pthread -shared'
- gcc -pthread -shared -flto -fuse-linker-plugin -ffat-lto-objects 
-flto-partition=none
+ gcc -pthread -shared


==
FAIL: test_sysconfig_module (distutils.tests.test_sysconfig.SysconfigTestCase)
--
Traceback (most recent call last):
  File 
"/home/greg/sandbox/python/cpython/3.5/Lib/distutils/tests/test_sysconfig.py", 
line 133, in test_sysconfig_module
sysconfig.get_config_var('LDFLAGS'))
AssertionError: '-flto -fuse-linker-plugin -ffat-lto-objects 
-flto-partition=none' != ''
- -flto -fuse-linker-plugin -ffat-lto-objects -flto-partition=none
+

--
components: Build
messages: 263598
nosy: alecsandru.patrascu, gregory.p.smith
priority: normal
severity: normal
status: open
title: test_distutils fails when configured --with-lto
versions: Python 3.5, Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25702] Link Time Optimizations support for GCC and CLANG

[Gregory P. Smith]

Changes by Gregory P. Smith :


--
dependencies: +test_distutils fails when configured --with-lto

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26788] test_gdb fails all tests on a profile-opt build configured --with-lto

[Gregory P. Smith]

New submission from Gregory P. Smith:

cpython/build35.lto$ ./python ../3.5/Lib/test/test_gdb.py
GDB version 7.10:
GNU gdb (Ubuntu 7.10-1ubuntu2) 7.10
...
==
FAIL: test_tuples (__main__.PrettyPrintTests)
Verify the pretty-printing of tuples
--
Traceback (most recent call last):
  File "../3.5/Lib/test/test_gdb.py", line 359, in test_tuples
self.assertGdbRepr(tuple(), '()')
  File "../3.5/Lib/test/test_gdb.py", line 279, in assertGdbRepr
gdb_repr, gdb_output = self.get_gdb_repr('id(' + ascii(val) + ')')
  File "../3.5/Lib/test/test_gdb.py", line 255, in get_gdb_repr
self.fail('Unexpected gdb output: %r\n%s' % (gdb_output, gdb_output))
AssertionError: Unexpected gdb output: 'Breakpoint 1 at 0x4cc310\n[Thread 
debugging using libthread_db enabled]\nUsing host libthread_db library 
"/lib/x86_64-linux-gnu/libthread_db.so.1".\n\nBreakpoint 1, builtin_id ()\n#0  
builtin_id ()\n'
Breakpoint 1 at 0x4cc310
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Breakpoint 1, builtin_id ()
#0  builtin_id ()

I don't know the right thing to do here.  This might depend on compiler, 
linker, arch and gdb version?  Are it's LTO executables debuggable?  It's not 
clear to me that we can do anything about this.  We may just want to skip the 
test when configured --with-lto.  Or perhaps this is an indication that this 
specific toolchain's LTO build (x86_64, ubuntu wily gcc 5.2.1 and gdb 7.1.0) 
has issues and shouldn't be used?

--
components: Build
messages: 263599
nosy: alecsandru.patrascu, gregory.p.smith
priority: normal
severity: normal
status: open
title: test_gdb fails all tests on a profile-opt build configured --with-lto
versions: Python 3.5, Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25702] Link Time Optimizations support for GCC and CLANG

[Gregory P. Smith]

Changes by Gregory P. Smith :


--
dependencies: +test_gdb fails all tests on a profile-opt build configured 
--with-lto

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26778] More typo fixes

[Roundup Robot]

Roundup Robot added the comment:

New changeset 395dd5630e6c by Serhiy Storchaka in branch '3.5':
Issue #26778: Fixed "a/an/and" typos in code comment and documentation.
https://hg.python.org/cpython/rev/395dd5630e6c

New changeset bbcde8db4dc4 by Serhiy Storchaka in branch '2.7':
Issue #26778: Fixed "a/an/and" typos in code comment and documentation.
https://hg.python.org/cpython/rev/bbcde8db4dc4

New changeset 932b330e22d8 by Serhiy Storchaka in branch 'default':
Issue #26778: Fixed "a/an/and" typos in code comment, documentation and error
https://hg.python.org/cpython/rev/932b330e22d8

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26778] More typo fixes

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com