[issue24421] Race condition compiling Modules/_math.c

[Tal Einat]

Tal Einat added the comment:

Confirmed on OSX 10.10. Here's my output:

running build
running build_ext
building 'cmath' extension
./slow-cc.py -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g 
-fwrapv -O3 -Wall -Wstrict-prototypes -Werror=declaration-after-statement 
-I./Include -I. -IInclude -I/usr/local/include 
-I/Users/taleinat/dev/cpython/Include -I/Users/taleinat/dev/cpython -c 
/Users/taleinat/dev/cpython/Modules/cmathmodule.c -o 
build/temp.macosx-10.10-x86_64-3.6/Users/taleinat/dev/cpython/Modules/cmathmodule.o
building 'math' extension
./slow-cc.py -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g 
-fwrapv -O3 -Wall -Wstrict-prototypes -Werror=declaration-after-statement 
-I./Include -I. -IInclude -I/usr/local/include 
-I/Users/taleinat/dev/cpython/Include -I/Users/taleinat/dev/cpython -c 
/Users/taleinat/dev/cpython/Modules/mathmodule.c -o 
build/temp.macosx-10.10-x86_64-3.6/Users/taleinat/dev/cpython/Modules/mathmodule.o
./slow-cc.py -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g 
-fwrapv -O3 -Wall -Wstrict-prototypes -Werror=declaration-after-statement 
-I./Include -I. -IInclude -I/usr/local/include 
-I/Users/taleinat/dev/cpython/Include -I/Users/taleinat/dev/cpython -c 
/Users/taleinat/dev/cpython/Modules/_math.c -o 
build/temp.macosx-10.10-x86_64-3.6/Users/taleinat/dev/cpython/Modules/_math.o
./slow-cc.py -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g 
-fwrapv -O3 -Wall -Wstrict-prototypes -Werror=declaration-after-statement 
-I./Include -I. -IInclude -I/usr/local/include 
-I/Users/taleinat/dev/cpython/Include -I/Users/taleinat/dev/cpython -c 
/Users/taleinat/dev/cpython/Modules/_math.c -o 
build/temp.macosx-10.10-x86_64-3.6/Users/taleinat/dev/cpython/Modules/_math.o
INITIAL COMPILE
RECOMPILE
RECOMPIILE TRUNCATING
INITIAL COMPILE FINISHED
./slow-cc.py -bundle -undefined dynamic_lookup 
build/temp.macosx-10.10-x86_64-3.6/Users/taleinat/dev/cpython/Modules/mathmodule.o
 build/temp.macosx-10.10-x86_64-3.6/Users/taleinat/dev/cpython/Modules/_math.o 
-L/usr/local/lib -o build/lib.macosx-10.10-x86_64-3.6/math.cpython-36m-darwin.so
ld: file too small (length=0) file 
'build/temp.macosx-10.10-x86_64-3.6/Users/taleinat/dev/cpython/Modules/_math.o' 
for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
RECOMPILE FINISHED
./slow-cc.py -bundle -undefined dynamic_lookup 
build/temp.macosx-10.10-x86_64-3.6/Users/taleinat/dev/cpython/Modules/cmathmodule.o
 build/temp.macosx-10.10-x86_64-3.6/Users/taleinat/dev/cpython/Modules/_math.o 
-L/usr/local/lib -o 
build/lib.macosx-10.10-x86_64-3.6/cmath.cpython-36m-darwin.so

--
nosy: +taleinat

___
Python tracker 

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

[issue24444] In argparse empty choices cannot be printed in the help

[py.user]

New submission from py.user:

>>> import argparse
>>> 
>>> parser = argparse.ArgumentParser()
>>> _ = parser.add_argument('foo', choices=[], help='%(choices)s')
>>> parser.print_help()
Traceback (most recent call last):
  File "", line 1, in 
  File "/home/guest/tmp/tests/misc/git/example/cpython/main/Lib/argparse.py", 
line 2358, in print_help
self._print_message(self.format_help(), file)
  File "/home/guest/tmp/tests/misc/git/example/cpython/main/Lib/argparse.py", 
line 2342, in format_help
return formatter.format_help()
  File "/home/guest/tmp/tests/misc/git/example/cpython/main/Lib/argparse.py", 
line 278, in format_help
help = self._root_section.format_help()
  File "/home/guest/tmp/tests/misc/git/example/cpython/main/Lib/argparse.py", 
line 208, in format_help
func(*args)
  File "/home/guest/tmp/tests/misc/git/example/cpython/main/Lib/argparse.py", 
line 208, in format_help
func(*args)
  File "/home/guest/tmp/tests/misc/git/example/cpython/main/Lib/argparse.py", 
line 517, in _format_action
parts.append('%*s%s\n' % (indent_first, '', help_lines[0]))
IndexError: list index out of range
>>>

It's not very useful to print empty choices, but the choices list could be 
formed dynamically. So the command-line user can't figure out what's happen.

--
components: Library (Lib)
messages: 245297
nosy: py.user
priority: normal
severity: normal
status: open
title: In argparse empty choices cannot be printed in the help
type: behavior
versions: Python 3.6

___
Python tracker 

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

[issue24403] Missing fixer for changed round() behavior

[Tal Einat]

Tal Einat added the comment:

See the existing issue and discussion about this on the six library's issue 
tracker (opened nearly a year ago):

https://bitbucket.org/gutworth/six/issue/94/introduce-sixround

--
nosy: +taleinat

___
Python tracker 

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

[issue24412] setUpClass equivalent for addCleanup

[Robert Collins]

Robert Collins added the comment:

It would be nice for symmetry. I mean, setUpClass isn't needed either, and we 
have it ;).

however, we actually have two contexts this would be called from - setUpClass 
and setUpModule; both share their internals. So we probably need a decoupled 
cleanups implementation, and two new binding points to it.

--

___
Python tracker 

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

[issue24443] Link for clear and wait missing in EventObjects

[Jaivish Kothari]

New submission from Jaivish Kothari:

https://docs.python.org/2/library/threading.html#threading.Event.set

links missing for wait and clear .
set() is linked though.

Line: "

An event object manages an internal flag that can be set to true with the set() 
method and reset to false with the clear() method. The wait() method blocks 
until the flag is true.

"

--
assignee: docs@python
components: Documentation
files: Fix_link.patch
keywords: patch
messages: 245294
nosy: berker.peksag, docs@python, georg.brandl, janonymous, janonymous, 
tim.golden, willingc
priority: normal
severity: normal
status: open
title: Link for clear and wait missing in EventObjects
type: enhancement
versions: Python 2.7
Added file: http://bugs.python.org/file39702/Fix_link.patch

___
Python tracker 

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

[issue24412] setUpClass equivalent for addCleanup

[Tal Einat]

Tal Einat added the comment:

Is this really needed? One can use try/except/raise, and since 
addClassCleanup() would only be called from setUpClass(), I don't quite see the 
utility of it.

--
nosy: +taleinat

___
Python tracker 

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

[issue795081] email.Message param parsing problem II

[Milan Oberkirch]

Milan Oberkirch added the comment:

Is this still relevant? I just made a patch based on the suggestions discussed 
and it does not change the behavior of the original bug report (but fixed the 
bug regarding '' mentioned by tony_nelson). Maybe I'm missing something?

--
keywords: +patch
nosy: +zvyn
Added file: http://bugs.python.org/file39701/issue795081.patch

___
Python tracker 

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

[issue22872] multiprocessing.Queue raises AssertionError

[Milan Oberkirch]

Milan Oberkirch added the comment:

Here is the trivial patch for that :)

--
keywords: +patch
nosy: +zvyn
Added file: http://bugs.python.org/file39700/issue22872.patch

___
Python tracker 

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

[issue24442] Readline Bindings Don't Report Any Error On Completer Function Exception

[Martin Panter]

Changes by Martin Panter :


--
nosy: +vadmium

___
Python tracker 

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

[issue21783] smtpd.py does not allow multiple helo/ehlo commands

[Milan Oberkirch]

Milan Oberkirch added the comment:

Here is the patch how it should look like at some point. Question being: How 
should we handle backwards-compatibility?

--
keywords: +patch
Added file: http://bugs.python.org/file39699/issue21783.patch

___
Python tracker 

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

[issue24175] Consistent test_utime() failures on FreeBSD

[Zachary Ware]

Zachary Ware added the comment:

This appears to have been fixed in #15745.

--
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
superseder:  -> Numerous utime ns tests fail on FreeBSD w/ ZFS (update: and 
NetBSD w/ FFS, Solaris w/ UFS)
type:  -> behavior

___
Python tracker 

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

[issue24442] Readline Bindings Don't Report Any Error On Completer Function Exception

[R. David Murray]

Changes by R. David Murray :


--
assignee:  -> docs@python
components: +Documentation -Interpreter Core
nosy: +docs@python
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

[issue22158] RFC 6531 (SMTPUTF8) support in smtpd.PureProxy

[Milan Oberkirch]

Milan Oberkirch added the comment:

After looking at this patch and how we implemented SMTPUTF8 in the parent class 
again, I think we can come up with a more generic solution. Haven't it figured 
out quite yet.

--

___
Python tracker 

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

[issue24442] Readline Bindings Don't Report Any Error On Completer Function Exception

[Perry Randall]

Perry Randall added the comment:

Ah yeah you're correct, on second thought I think an addition to the readline 
documentation is warranted, not a code change.

--

___
Python tracker 

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

[issue24442] Readline Bindings Don't Report Any Error On Completer Function Exception

[Steven D'Aprano]

Steven D'Aprano added the comment:

I disagree that it "should not be the case", I think Python's current behaviour 
is correct. Although it makes debugging completer functions harder, it would 
not be good for a bug in the completer to raise an exception and break line 
editing. This is one case where errors should be silenced.

Instead, my completion functions log errors to a file, and I watch the log file 
in another terminal window.

--
nosy: +steven.daprano

___
Python tracker 

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

[issue24442] Readline Bindings Don't Report Any Error On Completer Function Exception

[Perry Randall]

New submission from Perry Randall:

Noticed this while writing a non-trivial completion function for 
readline.set_completer. When an exception is thrown in the completion function 
readline doesnt do anything, squashes the error, this should not be the case.

--
components: Interpreter Core
files: readline_exception.patch
keywords: patch
messages: 245285
nosy: Perry Randall
priority: normal
severity: normal
status: open
title: Readline Bindings Don't Report Any Error On Completer Function Exception
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/file39698/readline_exception.patch

___
Python tracker 

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

[issue11245] Implementation of IMAP IDLE in imaplib?

[Piers Lauder]

Piers Lauder added the comment:

Hi, apologies for not responding to the "pierslauder" pings, but i don't own 
that login, or at least have forgotten all about it, and its email address is 
invalid (or there is another pierslauder out there).

I maintain imaplib2 on sourceforge (as piersrlauder) at 
https://sourceforge.net/projects/imaplib2/
and that version has just been modified to incorporate the CRAM_MD5_AUTH change 
from python3.6. It is regularly updated with bug fixes and it also has built-in 
tests for the IDLE function.

I originally intended for imaplib2 to be incorporated into pythonlib, leaving 
the original module in place (a la urllib/2). Then people wouldn't be forced 
into a switch using threads except by choice.

Anyway, happy to help.

--

___
Python tracker 

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

[issue24432] Upgrade windows builds to use OpenSSL 1.0.2b

[Ned Deily]

Ned Deily added the comment:

Make that OpenSSL 1.0.2c now.

--

___
Python tracker 

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

[issue24429] msvcrt error when embedded

[erik flister]

erik flister added the comment:

well i can confirm @eryksun's method works, so it's not a problem with how the 
manifest is included in the dll.  to me, the real issue is that 
ctypes.cdll.msvcrt and find_library('c') aren't correct.  the first returns 
something "old and unsupported," or "officially off-limits" (depending who you 
ask), and the second doesn't work when running embedded.  imho, both of them 
should use @eryksun's method to activate the dll's context, look in the 
included manifest, and return the msvcr* found there.  why isn't this the 
correct design?  why should every library have to reimplement the method just 
to allow running embedded, which they can't be responsible for knowing about?

--

___
Python tracker 

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

[issue24405] Missing code markup in "Expressions" documentation

[Berker Peksag]

Changes by Berker Peksag :


--
status: open -> closed

___
Python tracker 

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

[issue22158] RFC 6531 (SMTPUTF8) support in smtpd.PureProxy

[Milan Oberkirch]

Milan Oberkirch added the comment:

I just wanted to note that this patch works with the current default repo as 
expected. I will try to come up with some tests now (PureProxy is not tested at 
all right now).

--

___
Python tracker 

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

[issue24402] input() uses sys.__stdout__ instead of sys.stdout for prompt

[Tal Einat]

Tal Einat added the comment:

Here's a patch with just the required fix (no tests).

--
keywords: +patch
Added file: http://bugs.python.org/file39697/issue24402.fix_only.patch

___
Python tracker 

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

[issue24402] input() uses sys.__stdout__ instead of sys.stdout for prompt

[Tal Einat]

Tal Einat added the comment:

Okay, so the change is straightforward. With this change the entire test suite 
passes on my machine.

We'll need a test for this for the test suite, and that's far less 
straightforward. It seems that test.test_builtin.BuiltinTest.check_input_tty() 
could be a starting point. Could someone come up with a working test for this?

--
nosy: +taleinat

___
Python tracker 

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

[issue24441] In argparse add_argument() allows the empty choices argument

[R. David Murray]

R. David Murray added the comment:

There's no real reason to throw an error here, and to do so would break 
backward compatibility and, arguably, functionality: someone autogenerating a 
choices list might depend on the empty list working.

--
nosy: +r.david.murray
resolution:  -> rejected
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

[issue24441] In argparse add_argument() allows the empty choices argument

[py.user]

New submission from py.user:

A script, configuring argparse to have no choices:

#!/usr/bin/env python3

import argparse

parser = argparse.ArgumentParser()
parser.add_argument('foo', choices=[])

args = parser.parse_args()
print(args)


Running it:

[guest@localhost args]$ ./t.py
usage: t.py [-h] {}
t.py: error: too few arguments
[guest@localhost args]$ ./t.py a
usage: t.py [-h] {}
t.py: error: argument foo: invalid choice: 'a' (choose from )
[guest@localhost args]$ ./t.py ""
usage: t.py [-h] {}
t.py: error: argument foo: invalid choice: '' (choose from )
[guest@localhost args]$

[guest@localhost args]$ ./t.py -h
usage: t.py [-h] {}

positional arguments:
  {}

optional arguments:
  -h, --help  show this help message and exit
[guest@localhost args]$


ISTM, it should throw an exception about empty choices rather than show help 
with empty choices.

--
components: Library (Lib)
messages: 245277
nosy: py.user
priority: normal
severity: normal
status: open
title: In argparse add_argument() allows the empty choices argument
type: behavior
versions: Python 3.3, Python 3.6

___
Python tracker 

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

[issue20186] Derby #18: Convert 31 sites to Argument Clinic across 23 files

[Tal Einat]

Tal Einat added the comment:

Attached is a revised patch for Modules/mathmodule.c incorporating changes 
suggested by Serhiy in his review.

The major change is the reformatting of the doc-strings of most of the 
functions in the module to use the same format as doc-strings generated by AC.

--
Added file: http://bugs.python.org/file39696/issue20186.mathmodule.v2.patch

___
Python tracker 

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

[issue24406] "Built-in Types" doc doesn't explain dict comparison.

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
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

[issue24406] "Built-in Types" doc doesn't explain dict comparison.

[Roundup Robot]

Roundup Robot added the comment:

New changeset d775fad1db43 by Terry Jan Reedy in branch '2.7':
Issue #24406: Add sentences on dict comparisons, similar to those for Sequence
https://hg.python.org/cpython/rev/d775fad1db43

New changeset 4e816c324846 by Terry Jan Reedy in branch '3.4':
Issue #24406: Add sentences on dict comparisons, similar to those for Sequence
https://hg.python.org/cpython/rev/4e816c324846

--
nosy: +python-dev

___
Python tracker 

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

[issue24406] "Built-in Types" doc doesn't explain dict comparison.

[Terry J. Reedy]

Terry J. Reedy added the comment:

The 3.4 sequence section also has this: "Sequences of the same type also 
support comparisons. In particular, tuples and lists are compared 
lexicographically by comparing corresponding elements."  I agree that dicts 
should have a similar sentence or two. Neither the sequence or (frozen)set 
sections reference the language manual, so I will leave that out.

--
nosy: +terry.reedy
title: "Built-in Types" documentation doesn't explain how dictionaries are 
compared for equality -> "Built-in Types" doc doesn't explain dict comparison.
versions: +Python 2.7, 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

[issue15745] Numerous utime ns tests fail on FreeBSD w/ ZFS (update: and NetBSD w/ FFS, Solaris w/ UFS)

[STINNER Victor]

STINNER Victor added the comment:

I applied the fix to Python 3.4 and 3.5 too.

Python 2.7 doesn't look to be affected by the issue, I don't see any test 
copying the timestamp of a file to another, nor test on timestamp using 
nanosecond resolution.

--
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

[issue15745] Numerous utime ns tests fail on FreeBSD w/ ZFS (update: and NetBSD w/ FFS, Solaris w/ UFS)

[Roundup Robot]

Roundup Robot added the comment:

New changeset 50ec3fb126dd by Victor Stinner in branch '3.4':
Issue #15745: Rewrite os.utime() tests in test_os
https://hg.python.org/cpython/rev/50ec3fb126dd

New changeset 744c96cd57da by Victor Stinner in branch '3.5':
(Merge 3.4) Issue #15745: Rewrite os.utime() tests in test_os
https://hg.python.org/cpython/rev/744c96cd57da

--

___
Python tracker 

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

[issue24405] Missing code markup in "Expressions" documentation

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
resolution:  -> fixed
stage: needs patch -> resolved
type: enhancement -> behavior

___
Python tracker 

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

[issue24405] Missing code markup in "Expressions" documentation

[Roundup Robot]

Roundup Robot added the comment:

New changeset ccb0f43964e0 by Terry Jan Reedy in branch '3.4':
Closes issue #24405: mark set display as code.
https://hg.python.org/cpython/rev/ccb0f43964e0

--
nosy: +python-dev

___
Python tracker 

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

[issue24405] Missing code markup in "Expressions" documentation

[Terry J. Reedy]

Terry J. Reedy added the comment:

This is Py3 only (Py 2 has no set displays) in Reference Manual, 6.9. 
Comparisons.  (Please provide such info with reports.)  Will fix.

--
nosy: +terry.reedy
stage:  -> needs patch
versions: +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

[issue24431] StreamWriter.drain is not callable concurrently

[Guido van Rossum]

Guido van Rossum added the comment:

See mailing list discussion.

--
resolution:  -> rejected
status: open -> closed

___
Python tracker 

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

[issue24403] Missing fixer for changed round() behavior

[Terry J. Reedy]

Terry J. Reedy added the comment:

The fix would be to add a 'round' function at the top of a module, after the 
imports.  This is more the provenance of 2 & 3 compatibility modules, such as 
6, which might have both round2 and round3 functions.

--
nosy: +terry.reedy

___
Python tracker 

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

[issue11245] Implementation of IMAP IDLE in imaplib?

[Piers Lauder]

Changes by Piers Lauder :


--
nosy: +piers

___
Python tracker 

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

[issue24391] Better repr for threading objects

[Terry J. Reedy]

Terry J. Reedy added the comment:

The Semaphore and BoundedSemphore examples show why including the module is 
helpful.  I prefer the function-call syntax, as long as it is accurate, even 
though the string as a whole cannot be eval()-ed.  In any case, threading and 
multiprocessing are somewhat 'parallel' modules, so their reps should follow 
the same pattern.

--
nosy: +terry.reedy

___
Python tracker 

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

[issue24438] Strange behaviour when multiplying imaginary inf by 1

[Mark Dickinson]

Mark Dickinson added the comment:

Closing as not a bug;  for the suggestion of changing the mixed-type arithmetic 
behaviour, I think that's something that should be discussed on the 
python-ideas mailing list.

--
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

[issue24438] Strange behaviour when multiplying imaginary inf by 1

[Mark Dickinson]

Mark Dickinson added the comment:

There's no bug here:  as Steven explained, this is simply the result of the 
usual arithmetic conversions when performing a mixed-type operation.

> Python should multiply a complex by a non-complex in the "simple" way

I think this would just be adding unnecessary complication.  -1 from me.

--

___
Python tracker 

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

[issue24440] Move the buildslave setup information from the wiki to the devguide

[Carol Willing]

Carol Willing added the comment:

R. David, this will be an excellent addition to the devguide. Great clarity in 
the text. I particularly like your discussion of what are buildbots and who 
provides and maintains them. It also encourages those interested in a 
particular os to consider maintaining a buildbot suitable for their needs. 

I can see this being helpful to those individuals on the core mentorship list 
looking for testing issues to resolve. Nicely done :)

I will do a more thorough grammar/style review later. I will defer to others on 
the technical review.

--

___
Python tracker 

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

[issue24437] Add information about the buildbot console view and irc notices to devguide

[R. David Murray]

R. David Murray added the comment:

Oops, forgot to put the issue number in the commit message:

bff43c5c8c4f

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

___
Python tracker 

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

[issue24440] Move the buildslave setup information from the wiki to the devguide

[R. David Murray]

Changes by R. David Murray :


--
keywords: +patch
Added file: http://bugs.python.org/file39695/buildslave.patch

___
Python tracker 

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

[issue24440] Move the buildslave setup information from the wiki to the devguide

[R. David Murray]

New submission from R. David Murray:

I propose that we move the information on setting up a buildslave from the wiki 
to the devguide.  The attached patch is my rewrite (hopefully an improvement) 
of the information from the wiki.  Note that there are a couple of TBD pieces 
(setup on Windows, restart at boot on windows and mac).  I'll be filling in the 
mac stuff as I set up the Intel ICC mac buildbot and figure out what all is 
missing from the docs.

--
components: Devguide
messages: 245262
nosy: ezio.melotti, ncoghlan, pitrou, r.david.murray, willingc, zach.ware
priority: normal
severity: normal
stage: patch review
status: open
title: Move the buildslave setup information from the wiki to the devguide
type: enhancement

___
Python tracker 

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

[issue15745] Numerous utime ns tests fail on FreeBSD w/ ZFS (update: and NetBSD w/ FFS, Solaris w/ UFS)

[STINNER Victor]

STINNER Victor added the comment:

I pushed test_utime.patch with minor updates:

* _test_utime_current() now also checks if the FS supports subsecond
* use a delta of 20 ms in _test_utime_current(), instead of 10 ms, for Windows

I will wait for FreeBSD and Solaris buildbots to see if my changes fixes 
failures on os.utime() tests. If it's a success, I will backport the change to 
Python 3.4.

--

___
Python tracker 

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

[issue15745] Numerous utime ns tests fail on FreeBSD w/ ZFS (update: and NetBSD w/ FFS, Solaris w/ UFS)

[Roundup Robot]

Roundup Robot added the comment:

New changeset 4335d898be59 by Victor Stinner in branch 'default':
Issue #15745: Rewrite os.utime() tests in test_os
https://hg.python.org/cpython/rev/4335d898be59

--
nosy: +python-dev

___
Python tracker 

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

[issue24437] Add information about the buildbot console view and irc notices to devguide

[Carol Willing]

Carol Willing added the comment:

Thank you R. David and Zach. The patch looks good to me too, and the info will 
be helpful to others.

Please commit and let's get this good info out to others :)
(I don't have privileges or I would do so.)

--
stage: patch review -> commit review

___
Python tracker 

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

[issue24437] Add information about the buildbot console view and irc notices to devguide

[Zachary Ware]

Zachary Ware added the comment:

LGTM.

--

___
Python tracker 

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

[issue24438] Strange behaviour when multiplying imaginary inf by 1

[Steven D'Aprano]

Steven D'Aprano added the comment:

I've found the same behaviour going back to Python 1.5.

I think what happens here is that (0+∞j)*1 evaluates the multiplication by 
implicitly coercing the int to a complex:

(0+∞j)*(1+0j)
=> (0*1 + ∞j*1 + 0*0j + ∞j*0j)
=> (0-NAN + ∞j+0j)
=> (NAN + ∞j)

rather than using the "simple" way (1*0 + 1*∞j) => (0+∞j).

The problem here is that while there is no mathematical difference between 
multiplying by 1 or (1+0j), once you involve NANs and INFs, it does. So even 
though they give different answers, both methods are correct, for some value of 
"correct".

I don't see that this is necessarily a bug to be fixed, it might count as a 
change in behaviour needing to go through a deprecation period first. Perhaps 
it should be discussed on python-ideas first?

My personal feeling is that Python should multiply a complex by a non-complex 
in the "simple" way, rather than implicitly converting the int to a complex. 
Anyone who wants the old behaviour can easily get it by explicitly converting 1 
to a complex first.

So I guess this is a +1 to "fixing" this.

(Oh, the same applies to the / operator.)

--
nosy: +steven.daprano

___
Python tracker 

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

[issue24439] Feedback for awaitable coroutine documentation

[Martin Panter]

New submission from Martin Panter:

Today I tried playing with the new “async def” functionality in the interactive 
interpreter, based on reading the documentation. Here are some bits that 
surprised me, so could be the focus of further documentation. (Initial 
documentation added in Issue 24180.)

1. Confusion between coroutine and generator terms


AttributeError: 'generator' object has no attribute '__await__'

TypeError: coroutine-objects do not support iteration
TypeError: can't send non-None value to a just-started generator

Is it a coroutine object, or a generator object? The error messages etc seem to 
be split between the two terms. I guess the underlying implementation is 
closely shared between the two types, so old error messages still say 
“generator”, while new ones say “coroutine”. So there may not be an easy fix, 
but it was initially disconcerting. Perhaps a statement somewhere explaining 
coroutine instances are (based on / modified / a kind of / evolved from) 
generator instance objects, as appropriate.

2. Properties of a coroutine instance object

 
suggests that a coroutine instance should implement __await__(), but it 
apparently does not.

How to drive through the coroutine’s await points? This should be documented, 
and linked from relevant places in the documentation; perhaps the “coroutine” 
glossary entry, “async” statement, and “await” expression. The best clue that I 
found in the current documentation was 
,
 suggesting to use send().

Without having studied the PEP recently, I was expecting __await__() to be 
implemented, and invoking it would be similar to calling next() on an old-skool 
generator-iterator. Instead I see that calling __await__() is semantically more 
like __iter__(): it is only invoked once per “await” expression, and the return 
value is iterated over.

3. Allergic reaction to “await” on the same line as “async def”

>>> async def f(): await A(())
SyntaxError: invalid syntax

I see this is mentioned in the PEP that this is necessary so that “await” 
doesn’t have to be made a strict language keyword. But it should also be in the 
documentation.

4. Coroutine instances don’t implement the Coroutine ABC

>>> isinstance(c, Coroutine)
True
>>> hasattr(Coroutine, "__await__")
True
>>> hasattr(c, "__await__")
False

Reading closely, the documentation says “coroutine compatible classes”, but 
given the liberal use of “coroutine” everywhere, I think there should be a more 
obvious warning of how much a coroutine is a Coroutine.

--
assignee: docs@python
components: Documentation
messages: 245256
nosy: docs@python, vadmium, yselivanov
priority: normal
severity: normal
status: open
title: Feedback for awaitable coroutine documentation
type: enhancement
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

[issue11245] Implementation of IMAP IDLE in imaplib?

[F Malina]

F Malina added the comment:

I don’t have a test for it, neither has stdlib imaplib. We just need to port 
over the encode fix.

Copy over the fixed version of _CRAM_MD5_AUTH.
from line 599 in python3.5 imaplib
https://github.com/python/cpython/blob/master/Lib/imaplib.py#L599 

corresponding to line 884 in imaplib2
https://github.com/bcoe/imaplib2/blob/master/imaplib2/imaplib2.py#L884 


--

___
Python tracker 

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

[issue24087] Documentation doesn't explain the term "coroutine" (PEP 342)

[Martin Panter]

Martin Panter added the comment:

I suspect the patch is out of date due to PEP 492 and Issue 24180 (“await” 
syntax for coroutines). But maybe the current glossary entry could be refined 
to also mention generators.

--
nosy: +vadmium

___
Python tracker 

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

[issue11245] Implementation of IMAP IDLE in imaplib?

[R. David Murray]

R. David Murray added the comment:

Do you have any tests that use non-ascii passwords?  I think that was the most 
significant bug.

--

___
Python tracker 

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

[issue11245] Implementation of IMAP IDLE in imaplib?

[F Malina]

F Malina added the comment:

I just wen’t through my repo looking at relevant commits to double check and I 
didn’t have to change a line in my user level code when upgrading from python2 
to 3. There was only one way to do it.

--

___
Python tracker 

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

[issue23760] Tkinter in Python 3.4 on Windows don't post internal clipboard data to the Windows clipboard on exit

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Here is minimal reproducer on Tcl/Tk. I don't have a workaround.

--
status: pending -> open
Added file: http://bugs.python.org/file39694/issue23760.tcl

___
Python tracker 

___wm withdraw .
clipboard clear
clipboard append Result
exit___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue23996] _PyGen_FetchStopIterationValue() crashes on unnormalised exceptions

[Antoine Pitrou]

Antoine Pitrou added the comment:

Have you tried benchmarking the "slow" solution?

--

___
Python tracker 

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

[issue11245] Implementation of IMAP IDLE in imaplib?

[R. David Murray]

R. David Murray added the comment:

This is great.

When you say it is fully compatible, though, is that testing against imaplib in 
python2 or python3?  It is the python3 decisions about string/bytes handling 
where the discrepancies are most likely to arise, unless the python3 port was 
modeled on the stdlib version.

--

___
Python tracker 

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

[issue24438] Strange behaviour when multiplying imaginary inf by 1

[R. David Murray]

Changes by R. David Murray :


--
nosy: +mark.dickinson

___
Python tracker 

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

[issue24437] Add information about the buildbot console view and irc notices to devguide

[R. David Murray]

R. David Murray added the comment:

Thanks for the review.  Here is an updated patch.

--
Added file: http://bugs.python.org/file39693/buildbot-console-irc.patch

___
Python tracker 

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

[issue24438] Strange behaviour when multiplying imaginary inf by 1

[Alex Monk]

New submission from Alex Monk:

alex@alex-laptop:~$ python3
Python 3.4.3 (default, Mar 26 2015, 22:03:40) 
[GCC 4.9.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> infj = complex(0, float("inf"))
>>> infj
infj
>>> infj*1
(nan+infj)
>>> infj*1*1
(nan+nanj)

--
messages: 245247
nosy: Alex Monk
priority: normal
severity: normal
status: open
title: Strange behaviour when multiplying imaginary inf by 1
type: behavior

___
Python tracker 

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

[issue11245] Implementation of IMAP IDLE in imaplib?

[F Malina]

F Malina added the comment:

I am in for my part and I emailed Piers to come and join us and he surely
will when the bug tracker is responsive again.

Imaplib2 does have an up to date test suite and compatibility wise imaplib2
can be substituted for imaplib in existing clients with no changes in the
code.

On top of that I have a private IDLE test suite for common tasks such as
- instant bounce processing,
- email photo upload to web service,
- unsubscribe processing via list-unsubscribe headers and feedback loops of
major email providers.

I am looking to make it part of an external project
https://github.com/fmalina/emails, but need to extract much of the recipes
first out of a working application in a reusable manner as I need it in
other projects and will do for years to come.

--
nosy: +F.Malina

___
Python tracker 

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

[issue24431] StreamWriter.drain is not callable concurrently

[Guido van Rossum]

Guido van Rossum added the comment:

Note that Glyph recommends against this fix (see mailing list).

On Thu, Jun 11, 2015 at 7:59 AM, Martin Teichmann 
wrote:

>
> New submission from Martin Teichmann:
>
> Currently there is an assert statement asserting that no two
> tasks (asyncio tasks, that is) can use StreamWriter.drain at
> the same time. This is a weird limitiation, if there are two
> tasks writing to the same network socket, there is no reason
> why not both of them should drain the socket after (or before)
> writing to it.
>
> A simple bug fix is attached.
>
> --
> components: asyncio
> files: patch
> messages: 245172
> nosy: Martin.Teichmann, gvanrossum, haypo, yselivanov
> priority: normal
> severity: normal
> status: open
> title: StreamWriter.drain is not callable concurrently
> type: behavior
> versions: Python 3.4, Python 3.5, Python 3.6
> Added file: http://bugs.python.org/file39681/patch
>
> ___
> Python tracker 
> 
> ___
>

--

___
Python tracker 

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