[issue28806] Improve the netrc library

[Xiang Zhang]

Changes by Xiang Zhang :


--
nosy: +r.david.murray -haypo

___
Python tracker 

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

[issue26867] test_ssl test_options fails on ubuntu 16.04

[Xiang Zhang]

Xiang Zhang added the comment:

This test still fails with lastest Py2.7 on Ubuntu 16.10. Could we backport the 
patch to silence the failure?

./python -m test.regrtest test_ssl
[1/1] test_ssl
test test_ssl failed -- Traceback (most recent call last):
  File "/home/angwer/py2.7/Lib/test/test_ssl.py", line 780, in test_options
self.assertEqual(0, ctx.options)
AssertionError: 0 != 33554432L

1 test failed:
test_ssl

--
nosy: +benjamin.peterson

___
Python tracker 

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

[issue29147] registry value to be cleared when python is uninstalled

[jha.amit6666]

jha.amit added the comment:

Before I read your comment, I ran disk clean up which deleted everything.

--

___
Python tracker 

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

[issue29166] Spam

[Zachary Ware]

Changes by Zachary Ware :


--
components:  -asyncio
nosy:  -Mama Mama
title: AT tech email support number <1 855 338 0710 Spam
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

[issue29166] AT tech email support number <1 855 338 0710<AT tech email support phone number

[Xiang Zhang]

Changes by Xiang Zhang :


Removed file: http://bugs.python.org/file46152/1 855 338 0710 AT tech email 
support phone number AT email support number.jpg

___
Python tracker 

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

[issue29166] AT tech email support number <1 855 338 0710<AT tech email support phone number

[Xiang Zhang]

Changes by Xiang Zhang :


--
nosy:  -gvanrossum, yselivanov
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

[issue29166] AT tech email support number <1 855 338 0710<AT tech email support phone number

[Xiang Zhang]

Changes by Xiang Zhang :


--
Removed message: http://bugs.python.org/msg284711

___
Python tracker 

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

[issue29096] unicode_concatenate() optimization is not signal-safe (not atomic)

[Armin Rigo]

Changes by Armin Rigo :


Added file: http://bugs.python.org/file46153/patch1.diff

___
Python tracker 

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

[issue29166] AT tech email support number <1 855 338 0710<AT tech email support phone number

[Mama Mama]

New submission from Mama Mama:

AT tech email support number <1 855 338 0710$$$>>>1 855 338 0710 <<$<$_)_)AT 
tech email support phone number AT email support number
&$$$>>>1 855 338 0710 <<$<$_)_)AT tech 
email support phone number AT email support number
1 855 338 0710  moto khama wla AT tech email support number AT email 
support number  AT tech email support phone number at email technical 
support number

--
components: asyncio
files: 1 855 338 0710 AT tech email support phone number AT email support 
number.jpg
messages: 284711
nosy: Mama Mama, gvanrossum, yselivanov
priority: normal
severity: normal
status: open
title: AT tech email support number <1 855 338 0710

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

[issue29096] unicode_concatenate() optimization is not signal-safe (not atomic)

[Armin Rigo]

Changes by Armin Rigo :


Removed file: http://bugs.python.org/file46150/patch1.diff

___
Python tracker 

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

[issue29096] unicode_concatenate() optimization is not signal-safe (not atomic)

[Armin Rigo]

Changes by Armin Rigo :


Added file: http://bugs.python.org/file46151/patch2.diff

___
Python tracker 

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

[issue29096] unicode_concatenate() optimization is not signal-safe (not atomic)

[Armin Rigo]

Armin Rigo added the comment:

The signal handler is called between the INPLACE_ADD and the following 
STORE_FAST opcode, never from string_concatenate() itself.  A fix would be to 
make sure signal handlers are not called between these two opcodes.  See the 
minimal, proof-of-concept patch #1.  A possibly better fix, which at least 
should match the SETUP_FINALLY handling in the ticker handler, is attached as 
patch #2.  (Patches against 2.7.13)

--
keywords: +patch
Added file: http://bugs.python.org/file46150/patch1.diff

___
Python tracker 

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

[issue29165] Use forward compatible macro in example code for creating new type

[INADA Naoki]

New submission from INADA Naoki:

https://docs.python.org/2.7/extending/newtypes.html#the-basics uses 
PyObject_HEAD_INIT for type object header.

static PyTypeObject noddy_NoddyType = {
PyObject_HEAD_INIT(NULL)
0, /*ob_size*/

This code isn't compatible with Python 3.  In Python 3, PyVarObject_HEAD_INIT 
is used instead.
https://docs.python.org/3.6/extending/newtypes.html#the-basics

static PyTypeObject noddy_NoddyType = {
PyVarObject_HEAD_INIT(NULL, 0)

This code is compatible with Python 2.


This example code can be copy and pasted when creating new extension.
If people start writing Python 2 extension, and forward port it to Python 3,
this small incompatibility cause compile error.

Let's use more forward compatible and short code for example.

--
assignee: docs@python
components: Documentation
messages: 284709
nosy: docs@python, inada.naoki
priority: normal
severity: normal
status: open
title: Use forward compatible macro in example code for creating new type
type: enhancement
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

[issue29145] failing overflow checks in replace_*

[Xiang Zhang]

Xiang Zhang added the comment:

> It would be better to write the code in the same form as in 3.x. This could 
> help backporting other patches if needed.

Yes, it is. :-) I only had a fast glance at at 3.x codes and thought they 
didn't share much. :-( But apparently I was wrong. The new patch backports 3.x 
code.

--
Added file: http://bugs.python.org/file46149/replace-overflow-check-v2.patch

___
Python tracker 

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

[issue29164] make test always fail at 218/405 ( AssertionError: ', ' not found in '1234.5' )

[Xiang Zhang]

Xiang Zhang added the comment:

Could you provide your default locale setting, the result of 
`locale.setlocale(locale.LC_ALL, '')`?

--
nosy: +xiang.zhang

___
Python tracker 

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

[issue29096] unicode_concatenate() optimization is not signal-safe (not atomic)

[Raymond Hettinger]

Changes by Raymond Hettinger :


--
nosy: +arigo

___
Python tracker 

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

[issue29162] pyshell.py: name 'sys' is not defined

[Terry J. Reedy]

Terry J. Reedy added the comment:

I agree that depending on the incidental import is a bug.  Tkinter could 
change, or I might change 'from tkinter import *' to 'from tkinter import Tk, 
...' or 'import tkinter as tk'.

Serhiy, tkinter/__init__.py imports enum, sys, and re under their own names, so 
that * imports incidentally import them into other programs.  I believe it is 
customary for library modules to underscore stdlib imports to prevent this: 
"import enum as _enum", etc.  But I don't remember is this is in the devguide.  
Do you think we should make the change to tkinter?

--
nosy: +serhiy.storchaka
resolution:  -> fixed
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

[issue29142] urllib: no_proxy variable values with leading dot not properly handled

[Berker Peksag]

Berker Peksag added the comment:

Note: We don't officially use pull requests yet. Current way of contributing to 
Python is documented at https://docs.python.org/devguide/patch.html

--
nosy: +berker.peksag

___
Python tracker 

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

[issue29162] pyshell.py: name 'sys' is not defined

[Roundup Robot]

Roundup Robot added the comment:

New changeset 52d671684342 by Terry Jan Reedy in branch '3.6':
Issue #29162: Don't depend on 'from tkinter import *' importing sys.
https://hg.python.org/cpython/rev/52d671684342

--
nosy: +python-dev

___
Python tracker 

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

[issue29162] pyshell.py: name 'sys' is not defined

[Berker Peksag]

Berker Peksag added the comment:

I misread your comment. I think we need to add "import sys" to that file so I'm 
reopening this.

--
keywords: +easy
resolution: not a bug -> 
stage: resolved -> needs patch
status: closed -> open
versions: +Python 3.7

___
Python tracker 

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

[issue29142] urllib: no_proxy variable values with leading dot not properly handled

[Milan Oberkirch]

Milan Oberkirch added the comment:

I added a line stripping dots from name, I think it makes sense to strip at the 
end as well (`example.com` is the same domain as `example.com.`).

--
nosy: +zvyn
pull_requests: +8

___
Python tracker 

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

[issue29162] pyshell.py: name 'sys' is not defined

[Berker Peksag]

Berker Peksag added the comment:

Great, thanks for following up with us.

--
resolution:  -> not a bug
stage:  -> resolved

___
Python tracker 

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

[issue29021] Custom functions in sqlite receive None on invalid UTF-8

[Berker Peksag]

Berker Peksag added the comment:

We can just fallback to the current behavior (i.e. return None) if the return 
type of text_factory(val_str) is not str, bytes or bytearray. I think this is 
also somewhat similar to what we do for the return values of 
sqlite3_column_text().

--
nosy: +berker.peksag
stage:  -> needs patch
versions: +Python 3.7

___
Python tracker 

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

[issue29159] Regression in bytes constructor

[INADA Naoki]

INADA Naoki added the comment:

@belopolsky
It is backported behavior from Python 3.5, to fix regression.

See code review discussion in #27704.
The first patch kept the behavior, but we simplified it in second patch.
That cause this regression.

--

___
Python tracker 

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

[issue29162] pyshell.py: name 'sys' is not defined

[OO O]

OO O added the comment:

to msg284696 - (view):

OK~ 
Sorry I found i forget to install tkinter before I run make.
so the "from tkinter import *" failed. ( sys not import ).

--
status: open -> closed

___
Python tracker 

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

[issue28180] sys.getfilesystemencoding() should default to utf-8

[INADA Naoki]

INADA Naoki added the comment:

On Linux, I think most people wants UTF-8:surrogateescape by default, without 
fighting against locale and environment variables.

There are already `#if defined(__APPLE__) || defined(__ANDROID__)` path for it.
How about adding configure option to use same logic? (say 
`--with-encoding=(locale|utf-8)`, preferred encoding is changed in same way).

It may help many people building Python themselves without having root 
privilege for generating C.UTF-8 locale.

--

___
Python tracker 

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

[issue29162] pyshell.py: name 'sys' is not defined

[Berker Peksag]

Berker Peksag added the comment:

I think the OP is talking about Lib/idlelib/pyshell.py. The relevant changeset 
is 76f831e4b806. "from tkinter import *" imports the sys module as a 
side-effect. OO O, did you notice this by reading the code or by using a tool 
like flake8?

--
nosy: +berker.peksag
type: crash -> behavior

___
Python tracker 

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

[issue29162] pyshell.py: name 'sys' is not defined

[Milan Oberkirch]

Milan Oberkirch added the comment:

pyshell.py is not part of CPython, this is the wrong place to report a bug like 
this.

--
nosy: +zvyn

___
Python tracker 

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

[issue29160] pow with three int arguments works like it had two arguments

[Pavel Chuvakhov]

Pavel Chuvakhov added the comment:

Sorry about script, n1 should be n, and n2 should be m. Updated script is 
attached.

Ofc mpz is a way out. One also could cast int( np.int32 ) explicitly. I just 
wanted to underline that the best way is to hide all this stuff from a user and 
not make the user think what kind of int subtypes he should use. Python is a 
pretty language, isn't it? =)

Ones this is bug/limitation of numpy, shall we make a report for 'numpy guys' 
directly?

--
components: +Distutils -Interpreter Core
Added file: http://bugs.python.org/file46148/pow-bug_repor-upd.py

___
Python tracker 

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

[issue29161] random.SystemRandom(seed) documentation issue

[Gary E. Miller]

Gary E. Miller added the comment:

> The docs are clear that System Random uses os.urandom() for creating random 
> numbers, that there is not state, that sequences aren't reproducible, and 
> that seed method has no effect and is ignored.  

Agreed, but not relevant. I have anecdotal proof that the docs are not clear to 
a number of talented Python programmers that the seed parameter is not used.  
Or that the seed parameter is passed to the seed() method (and thus unused).

Disappointing...

--

___
Python tracker 

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

[issue29164] make test always fail at 218/405 ( AssertionError: ', ' not found in '1234.5' )

[OO O]

New submission from OO O:

make test always fail at 218/405
at test_format.py line 426

message:

[218/405/1] test test_format failed -- Traceback (most recent call last):
  File "/home/vm00/Downloads/Python-3.6.0/Lib/test/test_format.py", line 426, 
in test_locale
self.assertIn(sep, text)
AssertionError: ',' not found in '1234.5'

--
components: Installation
messages: 284692
nosy: OO O
priority: normal
severity: normal
status: open
title: make test always fail at 218/405 ( AssertionError: ',' not found in 
'1234.5' )
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

[issue29152] unittest subTest does not call addFailure

[Berker Peksag]

Berker Peksag added the comment:

Thanks for the report. That's because TestResult.addSubTest() updates 
TestResult.errors and TestResult.failures itself instead of calling the 
addError() and addFailure() methods respectively:

if issubclass(err[0], test.failureException):
errors = self.failures
else:
errors = self.errors
errors.append((subtest, self._exc_info_to_string(err, test)))

I don't know whether it was intentional or not so I'm adding Antoine to nosy 
list.

(I removed 3.4 from the versions field because it's in security-fix-only mode.)

--
components: +Library (Lib) -Tests
nosy: +berker.peksag, pitrou
stage:  -> test needed
type:  -> behavior
versions: +Python 3.6, Python 3.7 -Python 3.4

___
Python tracker 

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

[issue29161] random.SystemRandom(seed) documentation issue

[Raymond Hettinger]

Raymond Hettinger added the comment:

Thank you for the submission.  I respect what you're trying to do, but disagree 
that there is any issue here.   The docs are clear that System Random uses 
os.urandom() for creating random numbers, that there is not state, that 
sequences aren't reproducible, and that seed method has no effect and is 
ignored.  Also, the square brackets on the seed argument is our traditional way 
of saying that an argument is optional.

Apologies, but I'm going to close this.  IMO, the proposed wording is less 
clear and doesn't really help if someone is already misunderstanding what 
SystemRandom is all about and is imagining that the "seed" argument has some 
effect when the seed method is documented as being ignored.

--
status: open -> closed

___
Python tracker 

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

[issue29159] Regression in bytes constructor

[Alexander Belopolsky]

Alexander Belopolsky added the comment:

Inada,

Can you explain what your patch does?  I don't understand why you single out 
the OverflowError.  When is __index__ expected to raise it?

>>> (2**300).__index__()
2037035976334486086268445688409378161051468393665936250636140449354381299763336706183397376

--

___
Python tracker 

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

[issue29161] random.SystemRandom(seed) documentation issue

[Gary E. Miller]

Gary E. Miller added the comment:

Is there a better place to submit documentation problems to?  After my 
programming team spends a lot of valuable time figuring what the Python doc 
failed to mention I would like this knowledge to be put to good use by others.  
Paying it forward if you will.

--

___
Python tracker 

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

[issue29157] random.c: Prefer getrandom() over getentropy(), handle ENOSYS in py_getentropy()

[Nick Coghlan]

Nick Coghlan added the comment:

Aside from a couple of outdated comments and the EPERM question, the attached 
patch looks good to me.

Regarding EPERM, I think it would make sense to make py_getrandom and 
py_getentropy handle that consistently, otherwise I can see future maintainers 
readily getting confused by the discrepancy.

--

___
Python tracker 

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

[issue29161] random.SystemRandom(seed) documentation issue

[Gary E. Miller]

Gary E. Miller added the comment:

> > why have an ignored parameter that is not plainly documented as ignored.

> Because it improves the substitutability of one RNG for another (i.e. the 
> same reason that we even have a seed() method).

I understand why it the parameter it there.  I think the parameter should stay 
there.  I am all for orthogonal functions.  It just needs to be documented that 
the parameter is ignored by SystemRandom().

Programmers are being misled by the online documentation and adding a seed 
parameter when it does nothing.

I should not have to read the library code to find out that a parameter is 
ignored.

--

___
Python tracker 

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

[issue29157] random.c: Prefer getrandom() over getentropy(), handle ENOSYS in py_getentropy()

[Nick Coghlan]

Changes by Nick Coghlan :


--
nosy: +ncoghlan

___
Python tracker 

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

[issue29163] shlex error in posix mode and empty quotes

[Michal Ostrowski]

Changes by Michal Ostrowski :


--
components: +Library (Lib)
type:  -> behavior
versions: +Python 2.7, Python 3.4

___
Python tracker 

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

[issue29163] shlex error in posix mode and empty quotes

[Michal Ostrowski]

New submission from Michal Ostrowski:

Three examples below.  I believe the second is wrong, because it reorders
the "echo" and "," tokens.

>>> list(shlex.shlex('echo b="a",echo bar', posix=True))
['echo', 'b', '=', 'a', ',', 'echo', 'bar']
>>> list(shlex.shlex('echo b="",echo bar', posix=True))
['echo', 'b', '=', 'echo', ',', 'bar']
>>> list(shlex.shlex('echo b="",echo bar'))
['echo', 'b', '=', '""', ',', 'echo', 'bar']

--
messages: 284685
nosy: Michal Ostrowski
priority: normal
severity: normal
status: open
title: shlex error in posix mode and empty quotes

___
Python tracker 

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

[issue29162] pyshell.py: name 'sys' is not defined

[OO O]

New submission from OO O:

Sorry for my bad English.

line 7, 13 at pyshell.py.
Call sys befor import sys.
Cause name 'sys' is not defined

--
assignee: terry.reedy
components: IDLE
messages: 284684
nosy: OO O, terry.reedy
priority: normal
severity: normal
status: open
title: pyshell.py: name 'sys' is not defined
type: crash
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

[issue29161] random.SystemRandom(seed) documentation issue

[Raymond Hettinger]

Raymond Hettinger added the comment:

> why have an ignored parameter that is not plainly documented as ignored.

Because it improves the substitutability of one RNG for another (i.e. the same 
reason that we even have a seed() method).

--
priority: normal -> low
resolution:  -> not a bug

___
Python tracker 

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

[issue29148] Inheritance behaviour ambiguos

[Berker Peksag]

Berker Peksag added the comment:

You may find Raymond Hettinger's "super() considered super" article helpful to 
understand how Python's super() works: 
https://rhettinger.wordpress.com/2011/05/26/super-considered-super/

--
nosy: +berker.peksag

___
Python tracker 

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

[issue29161] random.SystemRandom(seed) documentation issue

[Gary E. Miller]

Gary E. Miller added the comment:

I would change:

"Accordingly, the seed() method has no effect and is ignored."

To:

"Accordingly, the optional seed parameter and the seed() method have no effect 
and are ignored."

It was not obvious to me that the seed paramrter got passed to the seed() 
method and was then ignored.  After all, why have an ignored parameter that is 
not plainly documented as ignored.

--

___
Python tracker 

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

[issue29159] Regression in bytes constructor

[INADA Naoki]

Changes by INADA Naoki :


--
keywords: +patch
Added file: http://bugs.python.org/file46147/29159-index-fallback.patch

___
Python tracker 

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

[issue29161] random.SystemRandom(seed) documentation issue

[Raymond Hettinger]

Raymond Hettinger added the comment:

>From the docs at 
>https://docs.python.org/3/library/random.html#alternative-generator :

"""
class random.SystemRandom([seed])
Class that uses the os.urandom() function for generating random numbers from 
sources provided by the operating system. Not available on all systems. Does 
not rely on software state, and sequences are not reproducible. Accordingly, 
the seed() method has no effect and is ignored. The getstate() and setstate() 
methods raise NotImplementedError if called.
"""

What is it that you think needs to be added or changed?

--

___
Python tracker 

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

[issue29161] random.SystemRandom(seed) documentation issue

[Raymond Hettinger]

Changes by Raymond Hettinger :


--
assignee:  -> rhettinger
nosy: +rhettinger

___
Python tracker 

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

[issue29160] pow with three int arguments works like it had two arguments

[Case Van Horsen]

Case Van Horsen added the comment:

This is a bug/limitation in numpy. If x and y are Python integers, and type(z) 
is of another numeric type, pow calls the nb_power slot of the underlying type. 
Here a quick example using numpy.int32 and gmpy2.mpz:

>>> import numpy, gmpy2
>>> pow(11,13,7)
4
>>> pow(11,13,numpy.int32(7))
34522712143931
>>> pow(11,13,gmpy2.mpz(7))
mpz(4)


>>> (11).__pow__(13,7)
4
>>> numpy.int32(11).__pow__(13,7)
34522712143931
>>> gmpy2.mpz(11).__pow__(13,7)
mpz(4)


casevh

--
nosy: +casevh

___
Python tracker 

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

[issue29161] random.SystemRandom(seed) documentation issue

[Gary E. Miller]

New submission from Gary E. Miller:

The man page for random.SystemRandom([seed]]) fails to mention that the 
parameter 'seed' is never used.  This should be prominent in the documentation. 
 I have found several cases where a seed was provided to SystemRandom().

https://docs.python.org/2.7/library/random.html?highlight=systemrandom

Present in all versions of Python docs that I could find.

--
components: Library (Lib)
messages: 284678
nosy: gem
priority: normal
severity: normal
status: open
title: random.SystemRandom(seed) documentation issue
type: behavior
versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7

___
Python tracker 

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

[issue29023] Results of random.seed() call with integer argument should be claimed deterministic.

[Raymond Hettinger]

Raymond Hettinger added the comment:

The wording can perhaps be made more precise.  However, this needs to be the 
end of this series of tracker items which are turning into time wasters.

--
assignee: docs@python -> rhettinger
nosy: +rhettinger
priority: normal -> low

___
Python tracker 

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

[issue29160] pow with three int arguments works like it had two arguments

[Jim Fasarakis-Hilliard]

Changes by Jim Fasarakis-Hilliard :


--
components: +Interpreter Core -Distutils
title: `pow` with three int arguments works like it had two arguments -> pow 
with three int arguments works like it had two arguments

___
Python tracker 

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

[issue29160] `pow` with three int arguments works like it had two arguments

[Benjamin Pollak]

Benjamin Pollak added the comment:

I tried running your script, but it crashes on the last two lines (variables n2 
and n1 appear to be undefined). Could you please update that script so we can 
have a better idea of the behavior of your bug?

Thanks,
BP

--
nosy: +Benjamin Pollak

___
Python tracker 

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

[issue29160] `pow` with three int arguments works like it had two arguments

[Pavel Chuvakhov]

New submission from Pavel Chuvakhov:

Standard `pow` function of three integer arguments should result in a reminder 
`(x**y) % z`. It seems that `pow(x,y,z)` ignores `%z` operation if type(z) is 
not `int`. This happens also in the cases when `z` has type numpy.int32, 
numpy.int64, etc. I consider such a behavior of `pow` as a bug to be fixed.

Thank you for your attantion, guys!
Best wishes, Pavel.

--
components: Distutils
files: pow-bug_report.py
messages: 284675
nosy: dstufft, eric.araujo, pch
priority: normal
severity: normal
status: open
title: `pow` with three int arguments works like it had two arguments
type: behavior
versions: Python 2.7
Added file: http://bugs.python.org/file46146/pow-bug_report.py

___
Python tracker 

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

[issue29158] Possible glitch in the interaction of a thread and a multiprocessing manager

[Davin Potts]

Davin Potts added the comment:

There are too many things going on in this example -- it would be far easier to 
digest if the example could be simplified.

The general programming rule of thumb (completely unrelated to but still just 
as relevant to Python) that I think David might have been invoking is:  create 
processes first then create threads inside of them.  Otherwise, if you fork a 
process that has multiple threads going inside it, you should expect problems.  
Assuming you're on a unix platform, it looks like you're creating threads then 
forking a process as well as doing it the other way around in another part of 
your code.

Different topic:  you mention killing the main process for server.py... which 
would likely kill the manager process referred to by shared_objects_manager... 
but you're creating a different manager process in bridge.py that is told to 
listen on the same port...


Without pulling apart your code further, I suspect confusion over how to use a 
Manager to share objects / data / information across processes.  If it helps, 
generally one process creates a manager instance (which itself results in the 
creation of a new process) and then other processes / threads created are 
created by that first process and given a handle on the manager instance or the 
objects managed by that manager.  I am a bit confused by your example but I 
hope that explanation helps provide some clarity?

--
nosy: +davin

___
Python tracker 

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

[issue29021] Custom functions in sqlite receive None on invalid UTF-8

[Aviv Palivoda]

Aviv Palivoda added the comment:

The problem is in _pysqlite_build_py_params function at connection.c. In case 
we have text we do the following code:

case SQLITE_TEXT:
  val_str = (const char*)sqlite3_value_text(cur_value);
  cur_py_value = PyUnicode_FromString(val_str);
  /* TODO: have a way to show errors here */
  if (!cur_py_value) {
 PyErr_Clear();
 Py_INCREF(Py_None);
 cur_py_value = Py_None;
  }
  break;

As you can see we call PyUnicode_FromString instead of text_factory.

I started making a patch to fix this by passing the text_factory to 
_pysqlite_build_py_params function but I currently have a problem with setting 
the result to the sqlite. User text_factory may return any type of object and I 
can't see how to handle that...

--
nosy: +palaviv

___
Python tracker 

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

[issue29159] Regression in bytes constructor

[Alexander Belopolsky]

Alexander Belopolsky added the comment:

Also relevant:

  * #20895 - Add bytes.empty_buffer and deprecate bytes(17) for the same purpose
  * PEP 467 - Minor API improvements for binary sequences

--

___
Python tracker 

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

[issue29159] Regression in bytes constructor

[Alexander Belopolsky]

Changes by Alexander Belopolsky :


--
nosy: +ncoghlan

___
Python tracker 

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

[issue29159] Regression in bytes constructor

[Alexander Belopolsky]

Alexander Belopolsky added the comment:

I don't think we should put too much effort into preserving numpy behavior.  
Consider this python 3.5 session:

>>> import numpy
>>> a = numpy.array([1])
>>> bytes(a)
__main__:1: VisibleDeprecationWarning: converting an array with ndim > 0 to an 
index will result in an error in the future
b'\x00'
>>> a = numpy.array([2, 2])
>>> bytes(a)
b'\x02\x00\x00\x00\x02\x00\x00\x00'

It looks like this behavior is just an artifact of ndarray providing both 
__index__ and buffer protocol and not something thought out by numpy developers.

I wonder if we could check for buffer protocol support before detecting an 
integer argument?  I also recall a discussion of deprecating bytes(int) 
altogether.  See 
.

--

___
Python tracker 

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

[issue29070] Integration tests for pty.spawn on Linux and all other platforms

[Martin Panter]

Martin Panter added the comment:

Ignore my comment about contrib agreement, that must have come through recently 
:)

--

___
Python tracker 

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

[issue29070] Integration tests for pty.spawn on Linux and all other platforms

[Martin Panter]

Martin Panter added the comment:

Hi Cornelius and thanks for the work. Since the patch adds a significant amount 
of code, I think you might have to sign the contributor agreement: 
. You can do it in a web 
browser.

I would like to review your tests, but because there is a lot of code to 
understand and I don’t have much time, it might take me a while. If you can 
find any way to simplify it, that would be great.

I have some comments on the code review, and will probably post more as I begin 
to understand what you are proposing.

It looks like you depend on fixing Issue 26228, but the patch there will 
conflict with your changes. Maybe merge with the other patch, or propose an 
alternative fix.

The documentation currently mentions the code is only tested on Linux, so it 
would be nice to update that.

The patch does introduce behavioural changes, if you consider abuse like 
monkey-patching os.exec() after importing the pty module. It is best not to 
make unnecessary changes in a bug fix.

Why does the patch slow the tests down so much? Ideally, it is nice to keep the 
tests as fast as possible.

What is the problem with using a genuine exec() call? Why do we need 
PtyMockingExecTestBase?

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

[issue26851] android compilation and link flags

[Xavier de Gaye]

Xavier de Gaye added the comment:

Latest patch committed with the following simplification: BASECFLAGS and 
LDFLAGS are now set for armv7 at the same place, as suggested by Martin in 
msg271518.

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

[issue26851] android compilation and link flags

[Roundup Robot]

Roundup Robot added the comment:

New changeset fa2bc63e64c6 by Xavier de Gaye in branch '3.6':
Issue #26851: Set Android compilation and link flags.
https://hg.python.org/cpython/rev/fa2bc63e64c6

New changeset af363b5200ff by Xavier de Gaye in branch 'default':
Issue #26851: Merge 3.6.
https://hg.python.org/cpython/rev/af363b5200ff

--
nosy: +python-dev

___
Python tracker 

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

[issue26851] android compilation and link flags

[Xavier de Gaye]

Changes by Xavier de Gaye :


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

[issue29159] Regression in bytes constructor

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Ah, if numpy arrays are affected, this should be restored. But swallowing an 
arbitrary exception doesn't look good to me.

--

___
Python tracker 

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

[issue29159] Regression in bytes constructor

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
nosy: +inada.naoki

___
Python tracker 

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

[issue29159] Regression in bytes constructor

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Indeed, there is behavior change. It is easy to revert the old behavior. But 
was the old behavior designed? It looks as a side effect of the implementation.

What is a reason of making an array an integer type?

--

___
Python tracker 

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

[issue29159] Regression in bytes constructor

[Alexander Belopolsky]

Alexander Belopolsky added the comment:

My test code may seem contrived, but numpy arrays exhibit similar behavior:

>>> a = numpy.array([2, 2])
>>> bytes(a)
Traceback (most recent call last):
  File "", line 1, in 
TypeError: only integer arrays with one element can be converted to an index

Under python 3.5, the result was

>>> bytes(a)
b'\x02\x00\x00\x00\x02\x00\x00\x00'

--

___
Python tracker 

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

[issue29159] Regression in bytes constructor

[Alexander Belopolsky]

New submission from Alexander Belopolsky:

Consider the following code:

$ cat bug.py
from array import array
class C(array):
def __new__(cls):
return array.__new__(cls, 'B', b'abc')
def __index__(self):
raise TypeError
x = C()
print(bytes(x))

It works under python 3.5:

$ python3.5 bug.py
b'abc'

but raises a TypeError under python 3.6:

$ python3.6 bug.py
Traceback (most recent call last):
  File "bug.py", line 8, in 
print(bytes(x))
  File "bug.py", line 6, in __index__
raise TypeError
TypeError

It looks like this was introduced in issue #27704.

(Ref: e/pyq#827)

--
keywords: 3.6regression
messages: 284663
nosy: belopolsky, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Regression in bytes constructor
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

[issue29158] Possible glitch in the interaction of a thread and a multiprocessing manager

[R. David Murray]

R. David Murray added the comment:

My understanding is that the basic rule of thumb is: don't mix threads and 
multiprocessing.  You may find that if you use spawn, it won't ever work.  But 
I haven't used multiprocessing myself.

--
nosy: +r.david.murray
type: crash -> behavior

___
Python tracker 

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

[issue29158] Possible glitch in the interaction of a thread and a multiprocessing manager

[Luciano Dionisio]

New submission from Luciano Dionisio:

After spending a lot of time trying to understand why my code will not execute 
as expected and after not getting any help from StackOverflow:

http://stackoverflow.com/questions/41444081/python-multiprocessing-manager-delegate-client-connection-and-dont-wait

I assumed that it may be a possible glitch in the interaction of a thread and a 
multiprocessing manager.

I have tried this in Python 2.7.13 and Python 3.6.0 and assume the problem 
still exists in between and beyond.

The problem appears when I try to delegate the connect() method of a 
multiprocessing manager client to a thread. The first time the procedure takes 
place, everything works fine and there is no problem of shared memory or 
anything. The problem arises on the second and forth trials of connect, when 
there seems to be a memory sharing problem. To reproduce the problem you have 
to run the server.py and client.py modules. You can see that the client is 
capable of populating the server's queue. If you terminate the server.py 
process and start it again, the client can no longer reassign the remote queue. 
Actually, reconnecting to the server always take place, as well as the correct 
linkage to the remote queue on line 53 of bridge.py:

self.items_buffer = self.remote_manager.items_buffer()

but the problem is that this procedure no longer works after the first time. 
Even though the connection is re-established, and at the moment of reconnection 
it is possible to send info to the server, whenever the thread dies, the pipe 
gets somehow broken.

--
components: Interpreter Core
files: case.zip
messages: 284661
nosy: Luciano Dionisio
priority: normal
severity: normal
status: open
title: Possible glitch in the interaction of a thread and a multiprocessing 
manager
type: crash
versions: Python 2.7, Python 3.6
Added file: http://bugs.python.org/file46145/case.zip

___
Python tracker 

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

[issue29157] random.c: Prefer getrandom() over getentropy(), handle ENOSYS in py_getentropy()

[STINNER Victor]

STINNER Victor added the comment:

Python 2.7, 3.5, 3.6 and 3.7 are impacted: they should fail on Linux if 
compiled with a recent glibc which has getentropy().

--

___
Python tracker 

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

[issue29157] random.c: Prefer getrandom() over getentropy(), handle ENOSYS in py_getentropy()

[STINNER Victor]

New submission from STINNER Victor:

A new getentropy() function was recently added to the glibc:
https://sourceware.org/bugzilla/show_bug.cgi?id=17252

When the Python/random.c file was written (by me), the getentropy() function 
was only supported on OpenBSD. Later, random.c was modified to *not* use 
getentropy() on Solaris (Issue #25003).

The problem is that py_getentropy() doesn't handle ENOSYS, and so Python fails 
at startup with a fatal error (Python 3.6):
   Fatal Python error: failed to get random numbers to initialize Python
or (Python 3.5):
   Fatal Python error: getentropy() failed

The bug was first reported in Fedora 26 (rawhide):
https://bugzilla.redhat.com/show_bug.cgi?id=1410175

Attached patch (written for the default branch) should fix these issues:

* Prefer getrandom() syscall over getentropy() function: getrandom() supports 
blocking and non-blocking mode on Linux, whereas getentropy() doesn't
* Enhance py_getentropy() to handle ENOSYS: fallback on reading from 
/dev/urandom and remember that the function doesn't work

I'm not sure that handling ENOSYS is required, since it's no more used on 
Linux, but it shouldn't hurt. I don't know if py_getentropy() should also 
handle EPERM?

py_getrandom() catchs errors: EAGAIN, EINTR, EPERM and ENOSYS.

With the patch, py_getentropy() catchs ENOSYS error.

--
files: getentropy.patch
keywords: patch
messages: 284659
nosy: christian.heimes, haypo
priority: normal
severity: normal
status: open
title: random.c: Prefer getrandom() over getentropy(), handle ENOSYS in 
py_getentropy()
type: security
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7
Added file: http://bugs.python.org/file46144/getentropy.patch

___
Python tracker 

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

[issue29145] failing overflow checks in replace_*

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

It would be better to write the code in the same form as in 3.x. This could 
help backporting other patches if needed.

--
nosy: +serhiy.storchaka

___
Python tracker 

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

[issue29155] test.test_spwd.TestSpwdNonRoot failure with FileNotFoundError:

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

It is easy to add FileNotFoundError to the list of expected exceptions. But it 
seems to me that the only error that gespname() can return on Linux is EACCES. 
[1] May be this is a bug of your platform.

[1] http://man7.org/linux/man-pages/man3/getspnam.3.html

--
nosy: +serhiy.storchaka

___
Python tracker 

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

[issue29155] test.test_spwd.TestSpwdNonRoot failure with FileNotFoundError:

[R. David Murray]

R. David Murray added the comment:

Since you are seeing errors on your platform that we are not seeing, and we do 
not have access to your platform, you are going to have to track down the 
cause, I'm afraid.

--
nosy: +r.david.murray

___
Python tracker 

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

[issue29156] remove superfluous pow test for (nonexistent) long

[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

[issue29156] remove superfluous pow test for (nonexistent) long

[Roundup Robot]

Roundup Robot added the comment:

New changeset f159ab8a9360 by Serhiy Storchaka in branch '3.5':
Issue #29156: Remove superfluous pow test.
https://hg.python.org/cpython/rev/f159ab8a9360

New changeset ef3440585a17 by Serhiy Storchaka in branch '3.6':
Issue #29156: Remove superfluous pow test.
https://hg.python.org/cpython/rev/ef3440585a17

New changeset 29d28f1bdc7c by Serhiy Storchaka in branch 'default':
Issue #29156: Remove superfluous pow test.
https://hg.python.org/cpython/rev/29d28f1bdc7c

--
nosy: +python-dev

___
Python tracker 

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

[issue29156] remove superfluous pow test for (nonexistent) long

[STINNER Victor]

STINNER Victor added the comment:

LGTM.

--
nosy: +haypo

___
Python tracker 

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

[issue29156] remove superfluous pow test for (nonexistent) long

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

LGTM. Thank you for your patch Lukas.

--
assignee:  -> serhiy.storchaka
nosy: +serhiy.storchaka
stage:  -> commit review

___
Python tracker 

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

[issue29156] remove superfluous pow test for (nonexistent) long

[Lukas Schwaighofer]

New submission from Lukas Schwaighofer:

Since python 3 there is no longer a type long. There is still a legacy test 
formerly used for longs present in test_pow.py. As the same test is already 
present (as also visible at the beginning of the patch) the test can safely be 
removed.

--
components: Tests
files: test_pow.patch
keywords: patch
messages: 284652
nosy: lukas.schwaighofer
priority: normal
severity: normal
status: open
title: remove superfluous pow test for (nonexistent) long
type: enhancement
versions: Python 3.7
Added file: http://bugs.python.org/file46143/test_pow.patch

___
Python tracker 

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

[issue29155] test.test_spwd.TestSpwdNonRoot failure with FileNotFoundError:

[Gerrit Holl]

New submission from Gerrit Holl:

I am building and testing Python 3.6 on the JASMIN Analysis Platform 
, which runs Red 
Hat Enterprise Linux Server release 6.8 on a machine with 48 × Intel(R) Xeon(R) 
CPU E7-4860 v2 @ 2.60GHz, 2 TiB RAM, and a PanFSⓇ 
 distributed file system.  
test.test_spwd.TestSpwdNonRoot is failing with FileNotFoundError.  Below is the 
full verbose output of `./python -m test -v test_spwd`:

== CPython 3.6.0 (default, Jan 4 2017, 14:11:04) [GCC 4.4.7 20120313 (Red Hat 
4.4.7-17)]
==   Linux-2.6.32-642.6.2.el6.x86_64-x86_64-with-redhat-6.8-Santiago 
little-endian
==   hash algorithm: siphash24 64bit
==  cwd: /home/users/gholl/src/Python-3.6.0/build/test_python_40357
==  encodings: locale=UTF-8, FS=utf-8
Testing with flags: sys.flags(debug=0, inspect=0, interactive=0, optimize=0, 
dont_write_bytecode=0, no_user_site=0, no_site=0, ignore_environment=0, 
verbose=0, bytes_warning=0, quiet=0, hash_randomization=1, isolated=0)
Run tests sequentially
0:00:00 [1/1] test_spwd
test_getspnam_exception (test.test_spwd.TestSpwdNonRoot) ... ERROR
test_getspall (test.test_spwd.TestSpwdRoot) ... skipped 'root privileges 
required'
test_getspnam (test.test_spwd.TestSpwdRoot) ... skipped 'root privileges 
required'

==
ERROR: test_getspnam_exception (test.test_spwd.TestSpwdNonRoot)
--
Traceback (most recent call last):
  File "/home/users/gholl/src/Python-3.6.0/Lib/test/test_spwd.py", line 67, in 
test_getspnam_exception
spwd.getspnam(name)
FileNotFoundError: [Errno 2] No such file or directory

--
Ran 3 tests in 0.002s

FAILED (errors=1, skipped=2)
test_spwd failed

1 test failed:
test_spwd

Total duration: 66 ms
Tests result: FAILURE

--
messages: 284651
nosy: Gerrit.Holl
priority: normal
severity: normal
status: open
title: test.test_spwd.TestSpwdNonRoot  failure with FileNotFoundError:

___
Python tracker 

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

[issue29155] test.test_spwd.TestSpwdNonRoot failure with FileNotFoundError:

[Gerrit Holl]

Changes by Gerrit Holl :


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

[issue29100] datetime.fromtimestamp() doesn't check min/max year anymore: regression of Python 3.6

[STINNER Victor]

STINNER Victor added the comment:

timestamp_limits.patch: Add many checks in the _datetime module to avoid 
overflows or creating a object out of the range. The patch adds unit tests.

The unit test checks dates around year 1 and year . I expect failures on 
platforms which only work well on year in the range 1970..2038. My plan is to 
wait for buildbot reports to check on which platforms the test fails and with 
which exception.

Since the patch is likely to break buildbots, I will apply first to the default 
branch, fix it, and then backport to Python 3.6.

--
Added file: http://bugs.python.org/file46142/timestamp_limits.patch

___
Python tracker 

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

[issue29154] 5 failures in test_doctest: ModuleNotFoundError: No module named 'IPython'

[Gerrit Holl]

Gerrit Holl added the comment:

I get the same failure cause in test_pdb and test_zipimport_support, also in 
situations with tests based on doctest, again getting an unexpected `*** 
ModuleNotFoundError: No module named 'IPython'`

--

___
Python tracker 

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

[issue29145] failing overflow checks in replace_*

[Xiang Zhang]

Xiang Zhang added the comment:

Ohh sorry I misunderstand your intention. :-( Attach a patch. :-)

--
keywords: +patch
stage:  -> patch review
Added file: http://bugs.python.org/file46141/replace-overflow-check.patch

___
Python tracker 

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

[issue28768] Warning: implicit declaration of function '_setmode'

[Roundup Robot]

Roundup Robot added the comment:

New changeset 5ea0fef6ec53 by Steve Dower in branch '2.7':
Issue #28768: Fix implicit declaration of function _setmode. Patch by Masayuki 
Yamamoto
https://hg.python.org/cpython/rev/5ea0fef6ec53

--

___
Python tracker 

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

[issue28180] sys.getfilesystemencoding() should default to utf-8

[STINNER Victor]

STINNER Victor added the comment:

> The default encoding in the C/POSIX locale is ASCII (which is the entire 
> source of the problem).

The reality is more complex than that :-) It depends on the OS.

Some OS uses Latin1 for the POSIX locale. Some OS announces to use
Latin1 for the POSIX locale, but use ASCII in practice :-) On these
lying OS, Python decodes bytes 0x80..0xff using mbstowcs() to check if
we get ASCII or Latin1: see the check_force_ascii() function.

/* Workaround FreeBSD and OpenIndiana locale encoding issue with the C locale.
   On these operating systems, nl_langinfo(CODESET) announces an alias of the
   ASCII encoding, whereas mbstowcs() and wcstombs() functions use the
   ISO-8859-1 encoding. The problem is that os.fsencode() and os.fsdecode() use
   locale.getpreferredencoding() codec. For example, if command line arguments
   are decoded by mbstowcs() and encoded back by os.fsencode(), we get a
   UnicodeEncodeError instead of retrieving the original byte string.

   The workaround is enabled if setlocale(LC_CTYPE, NULL) returns "C",
   nl_langinfo(CODESET) announces "ascii" (or an alias to ASCII), and at least
   one byte in range 0x80-0xff can be decoded from the locale encoding. The
   workaround is also enabled on error, for example if getting the locale
   failed.

(...) */

--

___
Python tracker 

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

[issue28768] Warning: implicit declaration of function '_setmode'

[STINNER Victor]

STINNER Victor added the comment:

Well, the change is not going to hurt. I backported the change. Thanks for the 
fix Masayuki!

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

[issue29134] contextlib doc bug

[Kyle Altendorf]

Kyle Altendorf added the comment:

I would think that the idea of simply adding some reference to `User` such as 
was suggested with `UserDefinedContextClass` would be reasonable and helpful.  
This doesn't involve any more code merely a more explanatory name.

--
nosy: +altendky

___
Python tracker 

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

[issue29154] 5 failures in test_doctest: ModuleNotFoundError: No module named 'IPython'

[Gerrit Holl]

New submission from Gerrit Holl:

I am building and testing Python 3.6 on the JASMIN Analysis Platform 
, which runs Red 
Hat Enterprise Linux Server release 6.8 on a machine with 48 × Intel(R) Xeon(R) 
CPU E7-4860 v2 @ 2.60GHz, 2 TiB RAM, and a PanFSⓇ 
 distributed file system.  I am 
experiencing failures in test_doctest, specifically with `ModuleNotFoundError: 
No module named 'IPython'`.  I don't know why it comes up with IPython at all.

Below is the non-verbose test output.  Attached is the verbose test output.


$ ./python -m test test_doctest
Run tests sequentially
0:00:00 [1/1] test_doctest
**
File "/dev/shm/gerrit/Python-3.6.0/Lib/test/test_doctest.py", line 1841, in 
test.test_doctest.test_debug
Failed example:
try: doctest.debug_src(s)
finally: sys.stdin = real_stdin
Expected:
> (1)()
(Pdb) next
12
--Return--
> (1)()->None
(Pdb) print(x)
12
(Pdb) continue
Got:
*** ModuleNotFoundError: No module named 'IPython'
> (1)()
(Pdb) next
12
--Return--
> (1)()->None
(Pdb) print(x)
12
(Pdb) continue
**
File "/dev/shm/gerrit/Python-3.6.0/Lib/test/test_doctest.py", line 1885, in 
test.test_doctest.test_pdb_set_trace
Failed example:
try: runner.run(test)
finally: sys.stdin = real_stdin
Expected:
--Return--
> (1)()->None
-> import pdb; pdb.set_trace()
(Pdb) print(x)
42
(Pdb) continue
TestResults(failed=0, attempted=3)
Got:
--Return--
*** ModuleNotFoundError: No module named 'IPython'
> (1)()->None
-> import pdb; pdb.set_trace()
(Pdb) print(x)
42
(Pdb) continue
TestResults(failed=0, attempted=3)
**
File "/dev/shm/gerrit/Python-3.6.0/Lib/test/test_doctest.py", line 1914, in 
test.test_doctest.test_pdb_set_trace
Failed example:
try:
runner.run(test)
finally:
sys.stdin = real_stdin
Expected:
--Return--
> (3)calls_set_trace()->None
-> import pdb; pdb.set_trace()
(Pdb) print(y)
2
(Pdb) up
> (1)()
-> calls_set_trace()
(Pdb) print(x)
1
(Pdb) continue
TestResults(failed=0, attempted=2)
Got:
--Return--
*** ModuleNotFoundError: No module named 'IPython'
> (3)calls_set_trace()->None
-> import pdb; pdb.set_trace()
(Pdb) print(y)
2
(Pdb) up
> (1)()
-> calls_set_trace()
(Pdb) print(x)
1
(Pdb) continue
TestResults(failed=0, attempted=2)
**
File "/dev/shm/gerrit/Python-3.6.0/Lib/test/test_doctest.py", line 1952, in 
test.test_doctest.test_pdb_set_trace
Failed example:
try: runner.run(test)
finally: sys.stdin = real_stdin
# doctest: +NORMALIZE_WHITESPACE
Expected:
--Return--
> (3)g()->None
-> import pdb; pdb.set_trace()
(Pdb) list
  1 def g(x):
  2 print(x+3)
  3  -> import pdb; pdb.set_trace()
[EOF]
(Pdb) next
--Return--
> (2)f()->None
-> g(x*2)
(Pdb) list
  1 def f(x):
  2  -> g(x*2)
[EOF]
(Pdb) next
--Return--
> (1)()->None
-> f(3)
(Pdb) list
  1  -> f(3)
[EOF]
(Pdb) continue
**
File "foo-...@baz.py", line 7, in foo-bar@baz
Failed example:
f(3)
Expected nothing
Got:
9
TestResults(failed=1, attempted=3)
Got:
--Return--
*** ModuleNotFoundError: No module named 'IPython'
> (3)g()->None
-> import pdb; pdb.set_trace()
(Pdb) list
  1 def g(x):
  2 print(x+3)
  3  -> import pdb; pdb.set_trace()
[EOF]
(Pdb) next
--Return--
> (2)f()->None
-> g(x*2)
(Pdb) list
  1 def f(x):
  2  -> g(x*2)
[EOF]
(Pdb) next
--Return--
> (1)()->None
-> f(3)
(Pdb) list
  1  -> f(3)
[EOF]
(Pdb) continue
**
File "foo-...@baz.py", line 7, in foo-bar@baz
Failed example:
f(3)
Expected nothing
Got:
9
TestResults(failed=1, attempted=3)
File "/dev/shm/gerrit/Python-3.6.0/Lib/test/test_doctest.py", line 2025, in 
test.test_doctest.test_pdb_set_trace_nested
Failed example:
try:
runner.run(test)
finally:
sys.stdin = real_stdin
# doctest: +REPORT_NDIFF
Differences (ndiff with -expected +actual):
+ *** ModuleNotFoundError: No module named 'IPython'
  > (5)calls_set_trace()
  -> self.f1()
  (Pdb) print(y)
  1
  (Pdb) step
  --Call--
  > (7)f1()
  -> def f1(self):
  (Pdb) step
  > 

[issue23680] Sporadic freeze in test_interrupted_write_retry_text

[Gerrit Holl]

Gerrit Holl added the comment:

I experience this problem when trying to build/test Python 3.6 on the [JASMIN 
Analysis Platform](http://www.jasmin.ac.uk/services/jasmin-analysis-platform/) 
which runs Red Hat Enterprise Linux Server release 6.8 on a machine with 48 × 
Intel(R) Xeon(R) CPU E7-4860 v2 @ 2.60GHz, 2 TiB RAM, and a 
[PanFSⓇ](http://www.panasas.com/products/panfs) distributed file system.  I 
experience this problem regardless whether I build/test Python 3.6 from within 
a PanFS filesystem or otherwise.

./python -m test -v test_io
== CPython 3.6.0 (default, Jan 4 2017, 15:08:07) [GCC 4.4.7 20120313 (Red Hat 
4.4.7-17)]
==   Linux-2.6.32-642.6.2.el6.x86_64-x86_64-with-redhat-6.8-Santiago 
little-endian
==   hash algorithm: siphash24 64bit
==  cwd: /dev/shm/gerrit/Python-3.6.0/build/test_python_34342
==  encodings: locale=UTF-8, FS=utf-8
Testing with flags: sys.flags(debug=0, inspect=0, interactive=0, optimize=0, 
dont_write_bytecode=0, no_user_site=0, no_site=0, ignore_environment=0, 
verbose=0, bytes_warning=0, quiet=0, hash_randomization=1, isolated=0)
Run tests sequentially
0:00:00 [1/1] test_io
[…snip many lines…]
test_interrupted_write_retry_text (test.test_io.CSignalsTest) ...

after which there is no more output.

--
nosy: +Gerrit.Holl

___
Python tracker 

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

[issue28180] sys.getfilesystemencoding() should default to utf-8

[Nick Coghlan]

Nick Coghlan added the comment:

The default encoding in the C/POSIX locale is ASCII (which is the entire source 
of the problem).

The initial verison of the PEP I uploaded didn't explain that background, but I 
added a section about it in the update earlier this week: 
https://www.python.org/dev/peps/pep-0538/#background

--

___
Python tracker 

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

[issue29145] failing overflow checks in replace_*

[jan matejek]

jan matejek added the comment:

No, your changes from issue 27473 are OK. However functions like 
replace_interleave and replace_single_character etc. still use the broken code:

/* use the difference between current and new, hence the "-1" */
/*   result_len = self_len + count * (to_len-1)  */
product = count * (to_len-1);
if (product / (to_len-1) != count) {
PyErr_SetString(PyExc_OverflowError, "replace bytes is too long");
return NULL;
}

--

___
Python tracker 

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

[issue29145] failing overflow checks in replace_*

[Xiang Zhang]

Xiang Zhang added the comment:

> It does, but "-fwrapv" is not automatically added when you specify custom OPT 
> flags.

Indeed I think this is why the changes in #27473 and #1621 make sense.

> GCC 6 optimizes away broken overflow checks.

I am sorry but I don't understand this. What do you mean by broken overflow 
checks? Is `if (size > PY_SSIZE_T_MAX - vo.len)` broken?

--
nosy: +xiang.zhang

___
Python tracker 

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

[issue29145] failing overflow checks in replace_*

[jan matejek]

jan matejek added the comment:

It does, but "-fwrapv" is not automatically added when you specify custom OPT 
flags. I should have clarified that in the original report.

--

___
Python tracker 

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

[issue5322] Python 2.6 object.__new__ argument calling autodetection faulty

[Jeroen Demeyer]

Jeroen Demeyer added the comment:

It worries me that nothing in the Python docs nor in any PEP describes how 
tp_new is inherited. In my opinion, ​this patch makes a significant change 
which should be subject to a PEP. However, neither the old nor new behaviour is 
described anywhere. This also makes it harder to argue which behaviour is 
correct.

--

___
Python tracker 

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

[issue29153] Test test.test_asynchat.TestAsynchat / test.test_asynchat.TestAsynchat_WithPoll fail test_close_when_done

[patrila]

Changes by patrila :


Added file: 
http://bugs.python.org/file46139/test_asynchat_add_receive_something_flag_2.7.13.patch

___
Python tracker 

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

[issue29153] Test test.test_asynchat.TestAsynchat / test.test_asynchat.TestAsynchat_WithPoll fail test_close_when_done

[patrila]

New submission from patrila:

Dear Python developers

The tests

test.test_asynchat.TestAsynchat.test_close_when_done
test.test_asynchat.TestAsynchat_WitrhPoll.test_close_when_done

fail with

==
FAIL: test_close_when_done (test.test_asynchat.TestAsynchat)
--
Traceback (most recent call last):
  File ".../Lib/test/test_asynchat.py", line 256, in test_close_when_done
self.assertGreater(len(s.buffer), 0)
AssertionError: 0 not greater than 0

==
FAIL: test_close_when_done (test.test_asynchat.TestAsynchat_WithPoll)
--
Traceback (most recent call last):
  File ".../Lib/test/test_asynchat.py", line 256, in test_close_when_done
self.assertGreater(len(s.buffer), 0)
AssertionError: 0 not greater than 0

Looking in the source code we see

self.assertEqual(c.contents, [])
# the server might have been able to send a byte or two back, but this
# at least checks that it received something and didn't just fail
# (which could still result in the client not having received anything)
self.assertGreater(len(s.buffer), 0)

We therefore conjecture that the server was able to send all data back.
The relevant part is around line 61, the run() method of echo_server.

# this may fail on some tests, such as test_close_when_done,
# since the client closes the channel when it's done sending
while self.buffer:
n = conn.send(self.buffer[:self.chunk_size])
time.sleep(0.001)
self.buffer = self.buffer[n:]


Indeed, if we change the sleeping time to something larger, e.g. 1sec. The 
tests pass fine.

In general it is a bad habit to relay on "hardware to be slow enough" to 
work/pass.
I therefore propose to introduce a separate field in echo_server which is set 
to True if the server has received some data.
Patch is attached and also included below. It is tested against Python-3.6.0 
(sorry no "default" branch).
Python 3.5.3rc1 also works, but the patch below has an offset of -1 (the import 
warnings line was added/removed depending on the point of view).
For Python 2.7.13 the "same patch" also works but needs different line numbers 
and also different context. Patch is attached.

Patch for 3.6.0:

--- a/Lib/test/test_asynchat.py
+++ b/Lib/test/test_asynchat.py
@@ -42,12 +42,15 @@
 self.event.set()
 conn, client = self.sock.accept()
 self.buffer = b"" 
+self.received_something = False
 # collect data until quit message is seen
 while SERVER_QUIT not in self.buffer:
 data = conn.recv(1)
 if not data:
 break
 self.buffer = self.buffer + data
+if self.buffer:
+self.received_something = True

 # remove the SERVER_QUIT message
 self.buffer = self.buffer.replace(SERVER_QUIT, b'')
@@ -252,7 +255,7 @@
 # the server might have been able to send a byte or two back, but this
 # at least checks that it received something and didn't just fail
 # (which could still result in the client not having received anything)
-self.assertGreater(len(s.buffer), 0)
+self.assertTrue(s.received_something)

 def test_push(self):
 # Issue #12523: push() should raise a TypeError if it doesn't get

--
files: test_asynchat_add_receive_something_flag_3.6.patch
keywords: patch
messages: 284636
nosy: patrila
priority: normal
severity: normal
status: open
title: Test test.test_asynchat.TestAsynchat / 
test.test_asynchat.TestAsynchat_WithPoll fail test_close_when_done
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7
Added file: 
http://bugs.python.org/file46138/test_asynchat_add_receive_something_flag_3.6.patch

___
Python tracker 

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

[issue29152] unittest subTest does not call addFailure

[kristall]

New submission from kristall:

unittests subTests do not call addFailure in the case of a failure.

Please see 
http://stackoverflow.com/questions/41432353/python3-4-unittest-addfailure-not-called-when-subtests-are-used
 for detailed problemdescription.

--
components: Tests
messages: 284635
nosy: kristall
priority: normal
severity: normal
status: open
title: unittest subTest does not call addFailure
versions: Python 3.4, Python 3.5

___
Python tracker 

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

[issue29149] SSL.py recursion limit crash

[R. David Murray]

Changes by R. David Murray :


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