[issue1602378] Incorrect docs for bisect_left

[Jack Aidley]

Jack Aidley added the comment:

This is still an issue in the latest version of the documentation.

It states "The returned insertion point i partitions the array a into two 
halves so that all(val < x for val in a[lo:i]) for the left side and all(val >= 
x for val in a[i:hi]) for the right side."

But this is not true, the returned value DOES NOT meet these criteria.

--
nosy: +JackAidley
versions: +Python 3.6 -Python 2.5

___
Python tracker 

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

[issue1602378] Incorrect docs for bisect_left

[Tim Peters]

Tim Peters added the comment:

What's your objection?  Here's your original example:

>>> from bisect import *
>>> L = [1,2,3,3,3,4,5]
>>> x = 3
>>> i = bisect_left(L, x)
>>> i
2
>>> all(val < x for val in L[:i])
True
>>> all(val >= x for val in L[i:])
True

Which criteria are not met?

--

___
Python tracker 

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

[issue25171] does not build on OpenBSD with no value defined for PY_GETENTROPY

[Remi Pointel]

Remi Pointel added the comment:

Attached is the diff to use defined(PY_GETENTROPY) instead of #define 
PY_GETENTROPY 1.

--
Added file: http://bugs.python.org/file40631/Python_random_c

___
Python tracker 

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

[issue25278] Unexpected socket exception on SFTP 'STOR' command

[Blanquier]

Blanquier added the comment:

Hi,

I send you the file as attached document.
I use the test_sftp_upload() as entry point.

Le 30/09/2015 16:43, R. David Murray a écrit :
> R. David Murray added the comment:
>
> As Eric said, we really can't diagnose this unless you show is your python 
> code (as code, not as a partial screenshot).
>
> --
>
> ___
> Python tracker 
> 
> ___
>

--
Added file: http://bugs.python.org/file40630/gui_ftp.py

___
Python tracker 

___# -*- coding: iso-8859-1 -*-
# ---
__file__ = "gui_ftp.py"
__doc__= "FTP functions for ul/downloading one or several server in parallele 
with multiple connections."
__author__ = "Philippe Blanquier"
__version__ = "v0.1"
__date__ = "24/06/2011"
__copyright__ = "Alcatel-Lucent"
__contact__ = "philippe.blanqu...@alcatel-lucent.com"
# ---

# Python include
import os,sys,ftplib,glob,time,threading,socket,copy

# Private include
import gui_common,gui_scenario_manager,gui_user

###  ###
### Private data ###
###  ###
_ftps_certificate_file_name = 
"C:"+os.sep+"Nemo_Pyc"+os.sep+"sftp_certificate.crt"  #: FTPS certificate for 
labo servers

_ftp_error_tag = "FTP"
_ftp_block_size = 64*gui_common.kilo_unit #: Maximum chunk size to read/write 
on the low-level socket object created to do the actual transfer
_ftp_repeat_nb = 10 #: Maximal command repeatition number before saying 'KO'...
_ftp_repeat_waiting_delay = 30.0 #: Delay between 2 repetition when a failure 
is detected

_upload_cmd   = "Upload"
_download_cmd = "Download"

_file_size_tag = "File size"

_ftp_posix_separator = '/' #: Normalized FTP directory separator ( UNIX POSIX !)
_ftp_dir_size = -1 #: Dummy FTP directory size

_ftp_create_dir_mutex = gui_common.nice_mutex( this_name = "FTP_Dir_Mutex") #: 
Internal directory creation protection

# see: http://en.wikipedia.org/wiki/List_of_FTP_server_return_codes
#
# FTP server return codes always have three digits, and each digit has a 
special meaning.
#
# The first digit denotes whether the response is good, bad or incomplete:
#   1xx Positive Preliminary reply
#   2xx Positive Completion reply
#   3xx Positive Intermediate reply
#   4xx Transient Negative Completion reply
#   5xx Permanent Negative Completion reply
#   6xx Protected reply
# The second digit is a grouping digit and encodes the following information:
#   x0x Syntax
#   x1x Information
#   x2x Connections
#   x3x Authentication and accounting
#   x4x Unspecified as of RFC 959.
#   x5x File system
### The requested action is being taken. Expect a reply before proceeding with 
a new command.
# 100   Series: The requested action is being initiated, expect another reply 
before proceeding with a new command.
# 110   Restart marker replay . In this case, the text is exact and not left to 
the particular implementation;
#   it must read: MARK  =  where  is User-process data stream 
marker, and  server's equivalent marker (note the spaces between markers 
and "=").
# 120   Service ready in nnn minutes.
# 125   Data connection already open; transfer starting.
# 150   File status okay; about to open data connection.
### The requested action has been successfully completed.
# 200   Command okay.
# 202   Command not implemented, superfluous at this site.
# 211   System status, or system help reply.
# 212   Directory status.
# 213   File status.
# 214   Help message.On how to use the server or the meaning of a particular 
non-standard command. This reply is useful only to the human user.
# 215   NAME system type. Where NAME is an official system name from the 
registry kept by IANA.
# 220   Service ready for new user.
# 221   Service closing control connection.
# 225   Data connection open; no transfer in progress.
# 226   Closing data connection. Requested file action successful (for example, 
file transfer or file abort).
# 227   Entering Passive Mode (h1,h2,h3,h4,p1,p2).
# 228   Entering Long Passive Mode (long address, port).
# 229   Entering Extended Passive Mode (|||port|).
# 230   User logged in, proceed. Logged out if appropriate.
# 231   User logged out; service terminated.
# 232   Logout command noted, will complete when transfer done.
# 250   Requested file action okay, completed.
# 257   "PATHNAME" created.
### The command has been accepted, but the requested action is being held 
pending receipt of further information.
# 331   User name okay, need password.
# 332   Need account for login.
# 350   Requested file action pending further information

[issue25194] Opt-in motivations & affiliations page for core contributors

[Marc-Andre Lemburg]

Marc-Andre Lemburg added the comment:

Thanks, Nick. The second version looks much better.

A few minor nits, which you may want to address:

 * Order in the section should probably be alphabetic rather than
   random time based (makes it easier to search for entries once the
   list gets longer)

 * If someone is available for paid work, should we flag this in a
   generic way or simply mention this in the descriptive text ?

 * How should contact information be added to the sections ?

--

___
Python tracker 

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

[issue18967] Find a less conflict prone approach to Misc/NEWS

[R. David Murray]

R. David Murray added the comment:

I never said they always had to be different, and "wholly different" is 
certainly not the case, nor do I think I implied that.

So if your tool supports my scenario that's all I'm asking for :)

--

___
Python tracker 

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

[issue25275] Documentation v/s behaviour mismatch wrt integer literals containing non-ASCII characters

[R. David Murray]

R. David Murray added the comment:

No, we can't make it stop working for int, that would be a backward 
compatibility break.  Doing so was discussed at one point and rejected (another 
issue somewhere in this tracker :)

--

___
Python tracker 

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

[issue25284] Spec for BaseEventLoop.run_in_executor(executor, callback, *args) is outdated in documentation

[Guido van Rossum]

Guido van Rossum added the comment:

Someone please submit a patch...

--
assignee:  -> docs@python
components: +Documentation -asyncio
keywords: +easy
nosy: +docs@python

___
Python tracker 

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

[issue24755] asyncio.wrap_future undocumented

[Andrej A Antonov]

Changes by Andrej A Antonov :


--
nosy: +polymorphm

___
Python tracker 

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

[issue25285] regrtest: run tests in subprocesses with -j1 on buildbots

[STINNER Victor]

New submission from STINNER Victor:

Currently, regrtest ignores the -j1 parameter. For -jN, the multiprocess mode 
is only enabled for N != 1. I propose to modify regrtest to run tests in 
subprocesses when -j1 is used. It would solve the issue #18906.

I also want to run tests in subprocesses in buildbot to better isolate tests. 
Running all tests in the same process, sequentially, cause various issues:

* various kinds of side effects
* memory leaks
* random failures (unreliable tests)

"make buildbot" already runs regrtest with -j1. I propose to also modify 
Tools/buildbot/test.bat to use run tests with -j1 by default on Windows.

I fixed regrtest to setup tests using the same code for classic mode and 
multiprocess mode: slaves (child processes running tests for regrtest -jN) now 
inherit
--memlimit/-M, --threshold/-t and --nowindows/-n options.

Only 3 remaining functions are incompatible with -jN: --coverage/-T and 
--findleaks/-l.

Finally, the multiprocess mode of regrtest now displays the duration of tests 
which took longer than 30 seconds, and every minute, it displays the tests 
running since longer than 30 seconds. Example with multiple workers (-j4):
---
...
[395/399/1] test_mimetypes -- running: test_lzma (111 sec), 
test_multiprocessing_forkserver (224 sec)
[396/399/1] test_poplib -- running: test_lzma (111 sec), 
test_multiprocessing_forkserver (225 sec)
[397/399/1] test_lzma (111 sec) -- running: test_multiprocessing_forkserver 
(225 sec)
[398/399/1] test_range -- running: test_multiprocessing_forkserver (227 sec)
running: test_multiprocessing_forkserver (287 sec)
[399/399/1] test_multiprocessing_forkserver (340 sec)
378 tests OK.
---

Note: "python -m test -j1 -j4" uses 4 workers, only the last -jN parameter is 
used. Some buildbots add -jN to use more workers.

--
components: Tests
messages: 251962
nosy: haypo
priority: normal
severity: normal
status: open
title: regrtest: run tests in subprocesses with -j1 on buildbots
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

[issue25285] regrtest: run tests in subprocesses with -j1 on buildbots

[STINNER Victor]

Changes by STINNER Victor :


--
keywords: +patch
Added file: http://bugs.python.org/file40632/regrtest_run_in_subprocess.patch

___
Python tracker 

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

[issue25171] does not build on OpenBSD with no value defined for PY_GETENTROPY

[Roundup Robot]

Roundup Robot added the comment:

New changeset e4ac5a899657 by Victor Stinner in branch 'default':
Issue #25171: Fix compilation issue on OpenBSD in random.c
https://hg.python.org/cpython/rev/e4ac5a899657

--
nosy: +python-dev

___
Python tracker 

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

[issue18967] Find a less conflict prone approach to Misc/NEWS

[Larry Hastings]

Larry Hastings added the comment:

I don't agree that in all cases the Misc/NEWS entry and the checkin comment 
must be wholly different.  While I concur that that's called for now and again, 
I believe this to be rare.  Most checkins are small changes, and a single-line 
summary for both Misc/NEWS and the first line of the checkin comment will 
suffice.

However, clearly the tool should *support* making them wholly separate.  But 
that's easy to support.  pyci now supports a "-n" or "--newsonly" flag, which 
instructs it to only add the Misc/NEWS item and to not check in.  This is 
presumably also nicer for folks used to shell-integrated hg tools (TortoiseHG 
etc).

I think it's important that this *not* be the default behavior, as it's going 
to be hard enough to get the core dev community to adopt this tool, and I would 
prefer it make the experience nicer rather than clunkier.

--

___
Python tracker 

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

[issue25284] Spec for BaseEventLoop.run_in_executor(executor, callback, *args) is outdated in documentation

[Yaroslav Admin]

Changes by Yaroslav Admin :


--
title: Docs for BaseEventLoop.run_in_executor(executor, callback, *args) is 
outdated in documentation -> Spec for BaseEventLoop.run_in_executor(executor, 
callback, *args) is outdated in documentation

___
Python tracker 

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

[issue25275] Documentation v/s behaviour mismatch wrt integer literals containing non-ASCII characters

[Shreevatsa R]

Shreevatsa R added the comment:

About the mismatch: of course it's probably not a good idea to change the 
parser (so that simply typing १२३४ in Python 3 code is like typing 1234), but 
how about changing the behaviour of int()? Not sure whether anyone should be 
relying on int(u'१२३४') being 1234, given that it is not documented as such.

--

___
Python tracker 

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

[issue25275] Documentation v/s behaviour mismatch wrt integer literals containing non-ASCII characters

[R. David Murray]

R. David Murray added the comment:

Good catch.  Yes, it is already documented that Int ignores leading and 
trailing whitespace.

But, even that isn't quite correct:

>>> 'A'.isdecimal()
False
>>> int('A', 16)
10

I seem to vaguely recall a discussion somewhere in this tracker about what 
"should" count as digits for larger-than-decimal radii, but I don't remember 
the outcome.

--

___
Python tracker 

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

[issue25284] Spec for BaseEventLoop.run_in_executor(executor, callback, *args) is outdated in documentation

[Nicholas Chammas]

Changes by Nicholas Chammas :


--
nosy: +Nicholas Chammas

___
Python tracker 

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

[issue18906] Create a way to always run tests in subprocesses within regrtest

[STINNER Victor]

STINNER Victor added the comment:

I created the issue #25285: "regrtest: run tests in subprocesses with -j1 on 
buildbots".

--
nosy: +haypo

___
Python tracker 

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

[issue25275] Documentation v/s behaviour mismatch wrt integer literals containing non-ASCII characters

[Shreevatsa R]

Shreevatsa R added the comment:

Minor difference, but the relevant function for int() is not quite isdigit(), 
e.g.:

>>> import unicodedata
>>> s = u'\u2460'
>>> unicodedata.name(s)
'CIRCLED DIGIT ONE'
>>> print s
①
>>> s.isdigit()
True
>>> s.isdecimal()
False
>>> int(s)
Traceback (most recent call last):
  File "", line 1, in 
UnicodeEncodeError: 'decimal' codec can't encode character u'\u2460' in 
position 0: invalid decimal Unicode string

It seems to be isdecimal(), plus if there are other digits in the string then 
many leading and trailing space-like characters are also allowed (e.g. 5760 
OGHAM SPACE MARK or 8195 EM SPACE or 12288 IDEOGRAPHIC SPACE:

>>> 987 == int(u'\u3000\n 987\u1680\t')
True

--

___
Python tracker 

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

[issue25284] Docs for BaseEventLoop.run_in_executor(executor, callback, *args) is outdated in documentation

[Yaroslav Admin]

New submission from Yaroslav Admin:

Parameter for BaseEventLoop.run_in_executor(executor, callback, *args) was 
renamed from callback to func in 3.5.0 release, but it's not reflected in the 
docs.

Commit with change: 
https://github.com/python/cpython/commit/111610562141a46f1eaac64d497d79fe13290847#diff-08afa52ab2b1511bee8527814ad44d80L468
Documentation: 
https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.BaseEventLoop.run_in_executor

--
components: asyncio
messages: 251961
nosy: Yaroslav Admin, gvanrossum, haypo, yselivanov
priority: normal
severity: normal
status: open
title: Docs for BaseEventLoop.run_in_executor(executor, callback, *args) is 
outdated in documentation
type: enhancement
versions: Python 3.5

___
Python tracker 

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

[issue18967] Find a less conflict prone approach to Misc/NEWS

[Antoine Pitrou]

Antoine Pitrou added the comment:

I sometimes put a bit more info in the commit message, but it's true that 
generally it's a copy/paste job as far as I'm concerned.

--

___
Python tracker 

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

[issue24820] IDLE themes for light on dark

[Marc Paul Rubin]

Marc Paul Rubin added the comment:

Greetings from an idle-dev 'lurker.' Has anyone tested the new dark
theme with a Set Breakpoint command? The dark theme is great for me
except for this quirk: breakpoints are invisible on my test box. Under
the Classic light scheme breakpoints appear on a bright yellow 
background. 
 
Appreciate all the interest and work going into idle these days. I'll
add any needed details on request. For starters I'm just wondering
whether breakpoints have yet to be tested with this dark theme.
 
Thanks, 
jayseye (Marc Paul Rubin)

--
nosy: +jayseye

___
Python tracker 

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

[issue25251] Unknown MS Compiler version 1900

[Matt Hickford]

Matt Hickford added the comment:

I'm not sure what the correct analogue of msvcr100 is for Visual C++ 14.0. 
"msvcr140.dll no longer exists" 
http://blogs.msdn.com/b/vcblog/archive/2014/06/03/visual-studio-14-ctp.aspx

elif msc_ver == '1600':
 # VS2010 / MSVC 10.0
 return ['msvcr100']
elif msc_ver == '1900':

--

___
Python tracker 

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

[issue25182] python -v crashes in nonencodable directory

[STINNER Victor]

STINNER Victor added the comment:

> Before importing the io module sys.stderr is stdprinter. It always encodes 
> written string to UTF-8. Proposed patch makes it to use the backslashreplace 
> error handler.

I like this solution. stdprinter is supposed to be replaced quickly.

But we may need something else to escape non-encodable characters in the 
filename when sys.stdout is a TextIOWrapper using the strict error handler.

--
nosy: +haypo

___
Python tracker 

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

[issue25182] python -v crashes in nonencodable directory

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Before importing the io module sys.stderr is stdprinter. It always encodes 
written string to UTF-8. Proposed patch makes it to use the backslashreplace 
error handler.

In future perhaps we could implement stdprinter in Python.

--
components: +Interpreter Core
keywords: +patch
stage:  -> patch review
Added file: http://bugs.python.org/file40625/stdprinter_backslashreplace.patch

___
Python tracker 

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

[issue25270] codecs.escape_encode systemerror on empty byte string

[Marc-Andre Lemburg]

Marc-Andre Lemburg added the comment:

The patch looks fine to me, but I still wonder how p - PyBytes_AS_STRING(v) can 
be negative when size == 0...

Ah, now I get it: the new size is 0, but the refcount is not 1, since the 
nullstring is shared. This causes the exception.

>From _PyBytes_Resize():

if (!PyBytes_Check(v) || Py_REFCNT(v) != 1 || newsize < 0) {
*pv = 0;
Py_DECREF(v);
PyErr_BadInternalCall();
return -1;
}

--

___
Python tracker 

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

[issue25276] test_decimal sometimes crash on PPC64 AIX 3.x

[STINNER Victor]

New submission from STINNER Victor:

This buildbot has low free memory. Maybe some part of _decimal doesn't handle 
an allocation failure?

http://buildbot.python.org/all/builders/PPC64%20AIX%203.x/builds/4173/steps/test/logs/stdio

...
[307/399/10] test_decimal
Fatal Python error: Segmentation fault

Current thread 0x0001 (most recent call first):
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_decimal.py",
 line 444 in eval_equation
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_decimal.py",
 line 321 in eval_line
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_decimal.py",
 line 299 in eval_file
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_decimal.py",
 line 5591 in 
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/unittest/case.py",
 line 600 in run
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/unittest/case.py",
 line 648 in __call__
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/unittest/suite.py",
 line 122 in run
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/unittest/suite.py",
 line 84 in __call__
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/unittest/suite.py",
 line 122 in run
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/unittest/suite.py",
 line 84 in __call__
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/unittest/runner.py",
 line 176 in run
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/support/__init__.py",
 line 1775 in _run_suite
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/support/__init__.py",
 line 1809 in run_unittest
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/test_decimal.py",
 line 5598 in test_main
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/libregrtest/runtest.py",
 line 160 in runtest_inner
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/libregrtest/runtest.py",
 line 113 in runtest
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/libregrtest/main.py",
 line 292 in run_tests_sequential
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/libregrtest/main.py",
 line 334 in run_tests
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/libregrtest/main.py",
 line 365 in main
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/libregrtest/main.py",
 line 407 in main
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/libregrtest/main.py",
 line 429 in main_in_temp_cwd
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/test/__main__.py",
 line 3 in 
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/runpy.py", 
line 85 in _run_code
  File 
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/runpy.py", 
line 170 in _run_module_as_main
make: *** [buildbottest] Segmentation fault (core dumped)

--
messages: 251919
nosy: haypo
priority: normal
severity: normal
status: open
title: test_decimal sometimes crash on PPC64 AIX 3.x
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

[issue25277] test_eintr hangs on randomly on "AMD64 FreeBSD 9.x 3.x"

[STINNER Victor]

New submission from STINNER Victor:

Too bad, the test test_eintr hangs sometimes on "AMD64 FreeBSD 9.x 3.x".

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

[397/399] test_traceback -- running: test_eintr (254 sec), test_subprocess (62 
sec)
[398/399] test_subprocess (71 sec) -- running: test_eintr (264 sec)
running: test_eintr (324 sec)
running: test_eintr (384 sec)
running: test_eintr (444 sec)
running: test_eintr (504 sec)
...

running: test_eintr (3505 sec)
running: test_eintr (3565 sec)
[399/399] test_eintr
Timeout (1:00:00)!
Thread 0x000801807400 (most recent call first):
  File "/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/selectors.py", 
line 375 in select
  File "/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/subprocess.py", 
line 1698 in _communicate
  File "/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/subprocess.py", 
line 1068 in communicate
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/support/script_helper.py",
 line 86 in run_python_until_end
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/support/script_helper.py",
 line 96 in _assert_python
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/support/script_helper.py",
 line 135 in assert_python_ok
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/test_eintr.py", 
line 19 in test_all
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/unittest/case.py", line 
600 in run
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/unittest/case.py", line 
648 in __call__
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/unittest/suite.py", 
line 122 in run
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/unittest/suite.py", 
line 84 in __call__
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/unittest/suite.py", 
line 122 in run
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/unittest/suite.py", 
line 84 in __call__
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/unittest/suite.py", 
line 122 in run
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/unittest/suite.py", 
line 84 in __call__
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/unittest/runner.py", 
line 176 in run
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/support/__init__.py",
 line 1775 in _run_suite
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/support/__init__.py",
 line 1809 in run_unittest
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/libregrtest/runtest.py",
 line 159 in test_runner
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/libregrtest/runtest.py",
 line 160 in runtest_inner
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/libregrtest/runtest.py",
 line 113 in runtest
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/libregrtest/runtest_mp.py",
 line 68 in run_tests_slave
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/libregrtest/main.py",
 line 357 in main
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/libregrtest/main.py",
 line 407 in main
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/libregrtest/main.py",
 line 429 in main_in_temp_cwd
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/regrtest.py", line 
39 in 
  File "/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/runpy.py", line 
85 in _run_code
  File "/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/runpy.py", line 
170 in _run_module_as_main
Traceback (most recent call last):
  File "/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/runpy.py", line 
170, in _run_module_as_main
"__main__", mod_spec)
  File "/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/runpy.py", line 
85, in _run_code
exec(code, run_globals)
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/__main__.py", line 
3, in 
regrtest.main_in_temp_cwd()
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/libregrtest/main.py",
 line 429, in main_in_temp_cwd
main()
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/libregrtest/main.py",
 line 407, in main
Regrtest().main(tests=tests, **kwargs)
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/libregrtest/main.py",
 line 365, in main
self.run_tests()
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/libregrtest/main.py",
 line 332, in run_tests
run_tests_multiprocess(self)
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/libregrtest/runtest_mp.py",
 line 210, in run_tests_multiprocess
raise Exception(msg)
Exception: Child error on test_eintr: Exit code 1
*** [buildbottest] Error code 1

--
messages: 251920
nosy: haypo
priority: 

[issue25182] python -v crashes in nonencodable directory

[STINNER Victor]

STINNER Victor added the comment:

Hum, the code didn't compile anymore on Windows. I took the opportunity to fix 
the errno issue that I saw.

Note: In fact, Python/fileutils.c is a a little bit different. Functions like 
_Py_write() save errno to restore it later because the caller expects errno to 
be set.

--

___
Python tracker 

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

[issue25275] Documentation v/s behaviour mismatch wrt integer literals containing non-ASCII characters

[R. David Murray]

R. David Murray added the comment:

Apparently that documentation is simply wrong.  The actual definition of what 
'int' handles is *different* from what the parser handles.  I think that 
difference must constitute a bug (not just a doc bug), but I'm not sure if it 
is something that we want to fix (changing the parser).

I think the *operational* definition of int conversion for both is the same as 
for isdigit in python3 
(https://docs.python.org/3/library/stdtypes.html#str.isdigit).  (The python2 
docs just say '8 bit strings may be locale dependent', which means the same 
thing but is less precise).

>>> १२३४
  File "", line 1
१२३४
   ^
SyntaxError: invalid character in identifier
>>> int('१२३४')
1234
>>> '१२३४'.isdigit()
True

The above behavior discrepancy doesn't apply to python2, since in python2 you 
can't use unicode in integer literals.

So, this is a bit of a mess :(.

The doc fix is simple: just replace the mention of integer literal with a link 
to isdigit, and fix the python2 isdigit docs to match python3's.

--
nosy: +r.david.murray
stage:  -> needs patch
type:  -> behavior
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

[issue25278] Unexpected socket exception on SFTP 'STOR' command

[Blanquier]

New submission from Blanquier:

With Filezilla Server 0.9.53, SFTP activated (force SSL on login, allow 
explicit FTP over TLS). From the FTP client point of view: when I use 
ftp_id.storbinary( 'STOR file_name'...), a socket.error exception arrive 
sometime. It's a socket.error exception and the errno record value is 0 (zero). 
The full message is b'[Errno 0] Error'. If I want to obtain the real server 
answer, I MUST call ftp_id.getresp().
It looks like a desynchronisation between the command and the answer.

Could you correct it please ?

Best regards.

--
components: Library (Lib)
messages: 251933
nosy: blanquier
priority: normal
severity: normal
status: open
title: Unexpected socket exception on SFTP 'STOR' command
type: behavior
versions: Python 2.7

___
Python tracker 

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

[issue25278] Unexpected socket exception on SFTP 'STOR' command

[R. David Murray]

R. David Murray added the comment:

Does this have anything to do with python itself and its standard library?  
From your description this sounds like a problem with filezilla and should be 
reported to them.

--
nosy: +r.david.murray
resolution:  -> third party
stage:  -> resolved
status: open -> pending

___
Python tracker 

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

[issue25280] Message can be formatted twice in importlib

[Serhiy Storchaka]

New submission from Serhiy Storchaka:

In importlib a verbose message can be formatted twice, the first time before 
passing it to _verbose_message(), and the second time in _verbose_message(), 
Example:

$ python -v
...
>>> open('{0}.pyc', 'wb').close()
>>> __import__('{0}')
Traceback (most recent call last):
  File "", line 1, in 
  File "", line 969, in _find_and_load
  File "", line 958, in _find_and_load_unlocked
  File "", line 673, in _load_unlocked
  File "", line 658, in exec_module
  File "", line 869, in get_code
  File "", line 440, in 
_validate_bytecode_header
  File "", line 368, in _verbose_message
IndexError: tuple index out of range

Proposed patch fixes the issue.

--
components: Library (Lib)
files: importlib_format_verbose_message.patch
keywords: patch
messages: 251937
nosy: brett.cannon, eric.snow, ncoghlan, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Message can be formatted twice in importlib
type: behavior
versions: Python 3.4, Python 3.5, Python 3.6
Added file: 
http://bugs.python.org/file40626/importlib_format_verbose_message.patch

___
Python tracker 

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

[issue25182] python -v crashes in nonencodable directory

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

> Hum, the code didn't compile anymore on Windows. I took the opportunity to
> fix the errno issue that I saw.

Thank you Victor.

--

___
Python tracker 

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

[issue25278] Unexpected socket exception on SFTP 'STOR' command

[R. David Murray]

R. David Murray added the comment:

(Note: issue 25278 with a small amount of additional info closed as a duplicate 
of this one).

--
status: pending -> open

___
Python tracker 

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

[issue25182] python -v crashes in nonencodable directory

[Roundup Robot]

Roundup Robot added the comment:

New changeset 2652c1798f7d by Victor Stinner in branch '3.4':
Issue #25182: Fix compilation on Windows
https://hg.python.org/cpython/rev/2652c1798f7d

New changeset 0eb26a4d5ffa by Victor Stinner in branch '3.5':
(Merge 3.4) Issue #25182: Fix compilation on Windows
https://hg.python.org/cpython/rev/0eb26a4d5ffa

New changeset d1090d733d39 by Victor Stinner in branch 'default':
(Merge 3.5) Issue #25182: Fix compilation on Windows
https://hg.python.org/cpython/rev/d1090d733d39

--

___
Python tracker 

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

[issue25275] Documentation v/s behaviour mismatch wrt integer literals containing non-ASCII characters

[R. David Murray]

R. David Murray added the comment:

I mean, in python2 you can use unicode in python code, only in strings, as 
opposed to python3 where unicode is valid in identifiers (but not integer 
literals, obviously).

--

___
Python tracker 

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

[issue25194] Opt-in motivations & affiliations page for core contributors

[R. David Murray]

R. David Murray added the comment:

After the "are especially encouraged" bullet list, I think you should add a 
paragraph about the motivations for that special encouragement (that you've 
previously articulated, such as colleagues being able to learn they have a 
coworker they can turn to as a resource).

Other than that it looks good to me.

--

___
Python tracker 

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

[issue25279] Unexpected ftplib.error_xxx exception on SFTP 'STOR' command

[Blanquier]

Blanquier added the comment:

With Filezilla Server 0.9.53, SFTP activated (force SSL on login, allow 
explicit FTP over TLS). From the FTP client point of view: when I use 
ftp_id.storbinary( 'STOR file_name'...), a ftplib.error_xxx exception arrive 
someting. 

On the windows server:
(000336)30/09/2015 08:56:59 - nemo_pyc (135.238.179.15)> STOR Handle.exe
(000336)30/09/2015 08:56:59 - nemo_pyc (135.238.179.15)> 150 Opening data 
channel for file upload to server of "/Handle.exe"
(000336)30/09/2015 08:56:59 - nemo_pyc (135.238.179.15)> 550 can't access file.
(000336)30/09/2015 08:57:29 - nemo_pyc (135.238.179.15)> TYPE I
(000336)30/09/2015 08:57:29 - nemo_pyc (135.238.179.15)> 200 Type set to I
(000336)30/09/2015 08:57:59 - nemo_pyc (135.238.179.15)>  ×3DG}
(000336)30/09/2015 08:58:04 - nemo_pyc (135.238.179.15)> 'Y'jQÌ~.
¾0Žåà ×3DG~
(000336)30/09/2015 08:58:04 - nemo_pyc (135.238.179.15)> 500 Syntax error, 
command unrecognized.
(000336)30/09/2015 08:58:09 - nemo_pyc (135.238.179.15)> ͈Ï!x›dƒïæA—:•\ 
×3DG
...

Could you fix the bug please ?
Best regards,

--

___
Python tracker 

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

[issue25278] Unexpected socket exception on SFTP 'STOR' command

[Eric V. Smith]

Eric V. Smith added the comment:

>From the info in issue 25279, I'd say it's an error in your code.

But to make sure it's not an error in the stdlib, can you show us your code? 
Without that, it's not possible to diagnose this any further.

--
nosy: +eric.smith
status: pending -> open

___
Python tracker 

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

[issue25278] Unexpected socket exception on SFTP 'STOR' command

[Eric V. Smith]

Changes by Eric V. Smith :


--
status: open -> pending

___
Python tracker 

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

[issue25182] python -v crashes in nonencodable directory

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Thank you for the review Victor.

> But we may need something else to escape non-encodable characters in the 
> filename when sys.stdout is a TextIOWrapper using the strict error handler.

This is not related to this issue. sys.stderr uses backslashreplace.

--
assignee:  -> serhiy.storchaka
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

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

[issue25275] Documentation v/s behaviour mismatch wrt integer literals containing non-ASCII characters

[R. David Murray]

R. David Murray added the comment:

I mean, in python2 you can't use unicode in python code, only in strings, as 
opposed to python3 where unicode is valid in identifiers (but not integer 
literals, obviously).

--

___
Python tracker 

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

[issue25275] Documentation v/s behaviour mismatch wrt integer literals containing non-ASCII characters

[R. David Murray]

Changes by R. David Murray :


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

___
Python tracker 

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

[issue25279] Unexpected ftplib.error_xxx exception on SFTP 'STOR' command

[Blanquier]

New submission from Blanquier:

activated (force SSL on login, allow explicit FTP over TLS). From the FTP 
client point of view: when I use ftp_id.storbinary( 'STOR file_name'...), a 
ftplib.error_xxx exception arrive someting. 

On the windows server:
(000336)30/09/2015 08:56:59 - nemo_pyc (135.238.179.15)> STOR Handle.exe
(000336)30/09/2015 08:56:59 - nemo_pyc (135.238.179.15)> 150 Opening data 
channel for file upload to server of "/Handle.exe"
(000336)30/09/2015 08:56:59 - nemo_pyc (135.238.179.15)> 550 can't access file.
(000336)30/09/2015 08:57:29 - nemo_pyc (135.238.179.15)> TYPE I
(000336)30/09/2015 08:57:29 - nemo_pyc (135.238.179.15)> 200 Type set to I
(000336)30/09/2015 08:57:59 - nemo_pyc (135.238.179.15)>  ×3DG}
(000336)30/09/2015 08:58:04 - nemo_pyc (135.238.179.15)> 'Y'jQÌ~.
¾0Žåà ×3DG~
(000336)30/09/2015 08:58:04 - nemo_pyc (135.238.179.15)> 500 Syntax error, 
command unrecognized.
(000336)30/09/2015 08:58:09 - nemo_pyc (135.238.179.15)> ͈Ï!x›dƒïæA—:•\ 
×3DG
...

could you fix the bug please ?
Best regards,

--
components: Library (Lib)
messages: 251934
nosy: blanquier
priority: normal
severity: normal
status: open
title: Unexpected ftplib.error_xxx exception on SFTP 'STOR' command
type: behavior
versions: Python 2.7

___
Python tracker 

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

[issue25220] Enhance and refactor test.regrtest (convert regrtest.py to a package)

[Roundup Robot]

Roundup Robot added the comment:

New changeset ec02ccffd1dc by Victor Stinner in branch 'default':
Issue #25220: Fix "-m test --forever"
https://hg.python.org/cpython/rev/ec02ccffd1dc

--

___
Python tracker 

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

[issue25182] python -v crashes in nonencodable directory

[Roundup Robot]

Roundup Robot added the comment:

New changeset 6347b154dd67 by Serhiy Storchaka in branch '3.4':
Issue #25182: The stdprinter (used as sys.stderr before the io module is
https://hg.python.org/cpython/rev/6347b154dd67

New changeset e8b6c6c433a4 by Serhiy Storchaka in branch '3.5':
Issue #25182: The stdprinter (used as sys.stderr before the io module is
https://hg.python.org/cpython/rev/e8b6c6c433a4

New changeset 0b0945c8de36 by Serhiy Storchaka in branch 'default':
Issue #25182: The stdprinter (used as sys.stderr before the io module is
https://hg.python.org/cpython/rev/0b0945c8de36

--
nosy: +python-dev

___
Python tracker 

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

[issue25182] python -v crashes in nonencodable directory

[STINNER Victor]

STINNER Victor added the comment:

> This is not related to this issue. sys.stderr uses backslashreplace.

Ok, fine.

---
+_errno = errno;
 Py_END_ALLOW_THREADS
+Py_XDECREF(bytes);

 if (n < 0) {
-if (errno == EAGAIN)
+if (_errno == EAGAIN)
 Py_RETURN_NONE;
 PyErr_SetFromErrno(PyExc_IOError);
---

Hum, if you expect that _errno can be modified by Py_XDECREF(bytes), you must 
restore the previous errno value before calling PyErr_SetFromErrno(). This 
strategy is used in Python/fileutils.c.

--

___
Python tracker 

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

[issue25270] codecs.escape_encode systemerror on empty byte string

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

May be better to test a condition "size > 0" before calling _PyBytes_Resize(), 
as in many other case where _PyBytes_Resize() is used.

Or accept shared objects in _PyBytes_Resize() if new size is equal to old size. 
This will allow to getrid of additional tests before calling _PyBytes_Resize().

--
nosy: +serhiy.storchaka

___
Python tracker 

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

[issue25279] Unexpected ftplib.error_xxx exception on SFTP 'STOR' command

[R. David Murray]

Changes by R. David Murray :


--
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Unexpected socket exception on SFTP 'STOR' command

___
Python tracker 

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

[issue25278] Unexpected socket exception on SFTP 'STOR' command

[R. David Murray]

Changes by R. David Murray :


--
status: open -> pending

___
Python tracker 

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

[issue24820] IDLE themes for light on dark

[Mark Roseman]

Mark Roseman added the comment:

Hi Marc, you're correct that is an error in the theme. To correct it, change 
the setting for 'break-background' to be something like #22. Thanks!

--

___
Python tracker 

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

[issue25251] Unknown MS Compiler version 1900

[Steve Dower]

Steve Dower added the comment:

There isn't one. MinGW doesn't support building with the UCRT yet, so you'll 
need to link to a different version of the library and hope that it works (or 
test/fix the extension).

--

___
Python tracker 

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

[issue24820] IDLE themes for light on dark

[Mark Roseman]

Mark Roseman added the comment:

Attached a patch to the current config dialog to add breakpoint to the window, 
and have updated the same thing in my newer dialog.

--
keywords: +patch
Added file: http://bugs.python.org/file40635/breakpoint-prefs.patch

___
Python tracker 

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

[issue12006] strptime should implement %G, %V and %u directives

[Ashley Anderson]

Ashley Anderson added the comment:

Another *ping* for a patch review since it's been almost a month since the last 
one.

--

___
Python tracker 

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

[issue25254] Idle: debugger source line highlighting fails again

[Mark Roseman]

Mark Roseman added the comment:

Was the 'source' checkbox in the debugger checked?

--

___
Python tracker 

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

[issue25272] asyncio tests are getting noisy

[Martin Panter]

Martin Panter added the comment:

Another source of noise is this warning about a task being slow to respond. I 
briefly investigated this a while back. I concluded that it only happens when 
other tests are run before it; it does not happen when test_asyncio is run 
alone. It is caused by the garbage collector, because I was able to stop it by 
invoking gc.collect() at a particular point in the test.

$ make -s -j2 && LC_TIME= ./python -bWall -m test -j0
[. . .]
[ 36/399] test_bytes
[ 37/399] test_bz2 -- running: test_buffer (32 sec), test_asyncore (42 sec), 
test_asyncio (44 sec)
[ 38/399] test_buffer (33 sec) -- running: test_asyncore (43 sec), test_asyncio 
(45 sec)
[ 39/399] test_asyncio (44 sec) -- running: test_asyncore (43 sec)
Executing .start() done, defined at 
/media/disk/home/proj/python/cpython/Lib/test/test_asyncio/test_pep492.py:146> 
result=None created at 
/media/disk/home/proj/python/cpython/Lib/asyncio/base_events.py:323> took 0.177 
seconds
returning true from eof_received() has no effect when using ssl
returning true from eof_received() has no effect when using ssl

--
nosy: +martin.panter

___
Python tracker 

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

[issue25275] Documentation v/s behaviour mismatch wrt integer literals containing non-ASCII characters

[Martin Panter]

Martin Panter added the comment:

Related discussion and background in Issue 10581, although that report seems to 
be geared at extending the Unicode support even further (disallowing mixed 
scripts, allowing proper minus signs, full-width characters, Roman numerals, 
etc).

The existing support is actually documented if you know where to look; see the 
sixth note under the table at 
. I agree that 
the references for each constructor should also document this as well.

--
nosy: +martin.panter

___
Python tracker 

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

[issue12006] strptime should implement %G, %V and %u directives

[Alexander Belopolsky]

Alexander Belopolsky added the comment:

Ashley,

You don't have to be a committer to review a patch.  Given that it is unlikely 
that any of the committers is an expert on ISO calendar, an external review 
will be most welcome.  Would you complete one?

--

___
Python tracker 

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

[issue25258] HtmlParser doesn't handle void element tags correctly

[Martin Panter]

Martin Panter added the comment:

My thinking is that the knowledge that  does not have a closing tag is at 
a higher level than the current HTMLParser class. It is similar to knowing 
where the following HTML implicitly closes the  elements:

Item AItem B

In both cases I would not expect the HTMLParser to report “virtual” empty or 
closing tags. I don’t think it should report an empty  or closing  
tag just because that is easy to do, because it would be inconsistent with 
other implied HTML tags. But maybe see what other people say.

I don’t know your particular use case, but I would suggest if you need to parse 
non-XML HTML  tags, use the handle_starttag() method and don’t rely on the 
end tag :)

--

___
Python tracker 

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

[issue12006] strptime should implement %G, %V and %u directives

[Ashley Anderson]

Ashley Anderson added the comment:

Thanks Alexander, but I think the latest patch is still mine. It seems strange 
to review my own patch. I'll do it if that's common, but since this will 
(hopefully, eventually) be my first accepted patch I would appreciate the 
feedback from another reviewer.

--

___
Python tracker 

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

[issue25270] codecs.escape_encode systemerror on empty byte string

[Martin Panter]

Martin Panter added the comment:

The patch looks sufficient to fix the problem, though I do like Serhiy’s 
suggestions.

For the record, because I was curious: Function codecs.escape_encode() is not 
documented, and barely tested. It was used for the documented “string_escape” 
codec in Python 2, but this codec was removed for Python 3 in revision 
bc90fc9b70b7. The function was apparently added to support pickling, but I 
don’t see any evidence that it was ever used. Only the decode counterpart was 
used. I wonder if the encode function could be removed at some point.

--
nosy: +martin.panter

___
Python tracker 

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

[issue25276] test_decimal sometimes crash on PPC64 AIX 3.x

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
components: +Extension Modules
type:  -> crash

___
Python tracker 

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

[issue25184] "python -m pydoc -w" fails in nondecodable directory

[Martin Panter]

Martin Panter added the comment:

Here is a patch that implements my IRI (Unicode URL) proposal. Differences 
compared to Serhiy’s patches:

* “file:” URLs use Unicode if possible. Percent encode encoding only used for 
reserved ASCII characters and undecodable bytes.

* HTTP URLs use UTF-8 and retain surrogate escaping. This means that the links 
generated by “getobj” pages to “getfile” pages work with troublesome paths.

* Displayed file names are get an ASCII question mark thanks to the “replace” 
error handler. This means that the generated HTML is now encodable to UTF-8. 
Serhiy’s path would be displayed something like:

/home/serhiy/py/cpy?thon-3.5/Lib/pydoc.py (invalid filename encoding)

* Added some missing html.escape() calls.

--
Added file: http://bugs.python.org/file40636/pydoc_iri.patch

___
Python tracker 

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

[issue24841] Some test_ssl network tests fail if svn.python.org is not accessible.

[Vinson Lee]

Vinson Lee added the comment:

I tested the attached patch on latest cpython master and it works for me.

test_ciphers (test.test_ssl.NetworkedTests) ... skipped "Resource 
'svn.python.org' is not available"
test_connect (test.test_ssl.NetworkedTests) ... skipped "Resource 
'svn.python.org' is not available"
test_connect_cadata (test.test_ssl.NetworkedTests) ... skipped "Resource 
'svn.python.org' is not available"
test_connect_capath (test.test_ssl.NetworkedTests) ... skipped "Resource 
'svn.python.org' is not available"
test_connect_ex (test.test_ssl.NetworkedTests) ... skipped 'svn.python.org 
cannot be reached: Connection refused'
test_connect_with_context (test.test_ssl.NetworkedTests) ... skipped "Resource 
'svn.python.org' is not available"
test_context_setget (test.test_ssl.NetworkedTests) ... skipped "Resource 
'svn.python.org' is not available"
test_get_ca_certs_capath (test.test_ssl.NetworkedTests) ... skipped "Resource 
'svn.python.org' is not available"
test_get_server_certificate (test.test_ssl.NetworkedTests) ... skipped 
"Resource 'svn.python.org' is not available"
test_makefile_close (test.test_ssl.NetworkedTests) ... skipped "Resource 
'svn.python.org' is not available"
test_non_blocking_connect_ex (test.test_ssl.NetworkedTests) ... skipped 
"Resource 'svn.python.org' is not available"
test_non_blocking_handshake (test.test_ssl.NetworkedTests) ... skipped 
"Resource 'svn.python.org' is not available"
test_timeout_connect_ex (test.test_ssl.NetworkedTests) ... skipped 
'svn.python.org cannot be reached: Connection refused'
test_handshake (test.test_ssl.NetworkedBIOTests) ... skipped "Resource 
'svn.python.org' is not available"
test_read_write_data (test.test_ssl.NetworkedBIOTests) ... skipped "Resource 
'svn.python.org' is not available"

Tested-by: Vinson Lee 

--

___
Python tracker 

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

[issue25274] "./python -m test test_sys": Fatal Python error: Cannot recover from stack overflow

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

See also issue25222. _Py_CheckRecursiveCall may be being called recursively 
through Py_FatalError.

--
components: +Interpreter Core, Tests
nosy: +serhiy.storchaka
type:  -> crash

___
Python tracker 

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

[issue25182] python -v crashes in nonencodable directory

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

> > This is not related to this issue. sys.stderr uses backslashreplace.
> Ok, fine.

But is related to issue25183.

--

___
Python tracker 

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

[issue22413] Bizarre StringIO(newline="\r\n") translation

[Martin Panter]

Martin Panter added the comment:

I understand it may not be worth changing the behaviour. Would you instead 
accept a change to the documentation to point out that “newline” does _not_ 
actually work like TextIOWrapper? Or perhaps even deprecating or recommending 
against using “newline”?

--

___
Python tracker 

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

[issue25286] views are not sequences

[Akira Li]

New submission from Akira Li:

The entry for *dict view* in the glossary may be clarified, to avoid
confusion with collection.abc.Sequence i.e., from:

  They are lazy sequences that will see changes in the underlying
  dictionary.

to something like:

  They provide a dynamic view on the dictionary’s entries, which means
  that when the dictionary changes, the view reflects these changes.

See https://mail.python.org/pipermail/python-ideas/2015-October/036682.html

I've attached the corresponding doc patch.

--
assignee: docs@python
components: Documentation
files: dict-views-glossary.patch
keywords: patch
messages: 251995
nosy: akira, docs@python
priority: normal
severity: normal
status: open
title: views are not sequences
type: behavior
versions: Python 3.4, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file40638/dict-views-glossary.patch

___
Python tracker 

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

[issue16701] Docs missing the behavior of += (in-place add) for lists.

[Martin Panter]

Martin Panter added the comment:

“For the most part” works for me. Here is the patch.

--
Added file: http://bugs.python.org/file40637/seq-inplace.v3.patch

___
Python tracker 

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

[issue25281] Incorrect enum behavior during json.dumps serialization

[R. David Murray]

R. David Murray added the comment:

As indicated by the issue you referenced and the fact that you are using 
enum34, this is not a bug in the python or its standard library.  I believe the 
correct place to report this is 
https://bitbucket.org/stoneleaf/enum34/issues?status=new=open.

--
nosy: +ethan.furman, r.david.murray
resolution:  -> third party
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

[issue25194] Opt-in motivations & affiliations page for core contributors

[Zachary Ware]

Changes by Zachary Ware :


--
nosy: +zach.ware

___
Python tracker 

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

[issue25224] Replace Idle's README.txt with annotated file list

[Mark Roseman]

Mark Roseman added the comment:

Good start... would have been very helpful for me a couple of months back!

Have attached a patch to your patch, breaking the main implementation into a 
few categories, and fixing a few typos.

--
Added file: http://bugs.python.org/file40629/README2.diff

___
Python tracker 

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

[issue25281] Incorrect enum behavior during json.dumps serialization

[Vitaly Belman]

Vitaly Belman added the comment:

Note: Using pip library enum34

--

___
Python tracker 

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

[issue25281] Incorrect enum behavior during json.dumps serialization

[Vitaly Belman]

New submission from Vitaly Belman:

Possibly related to: http://bugs.python.org/issue18264


The following code:

>>> import IntEnum from enum
>>> from enum import IntEnum
>>> class a(IntEnum): a=0
>>> json.loads(json.dumps({"x": a.a}))

Produces:

ValueError: No JSON object could be decoded

Which makes sense because the json dumps function produces is: {"x": a.a}

--
messages: 251945
nosy: Vitaly Belman
priority: normal
severity: normal
status: open
title: Incorrect enum behavior during json.dumps serialization
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

[issue25278] Unexpected socket exception on SFTP 'STOR' command

[R. David Murray]

R. David Murray added the comment:

As Eric said, we really can't diagnose this unless you show is your python code 
(as code, not as a partial screenshot).

--

___
Python tracker 

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

[issue11215] test_fileio error on AIX

[STINNER Victor]

Changes by STINNER Victor :


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

[issue11215] test_fileio error on AIX

[STINNER Victor]

STINNER Victor added the comment:

I see that the test pass on AIX, on Python 2.7 and Python 3.6 buildbots, so I 
close the issue.

This issue was opened 4 years ago. The test is now skipped on many platforms:

if sys.platform != "win32":
try:
f = self.FileIO("/dev/tty", "a")
except OSError:
# When run in a cron job there just aren't any
# ttys, so skip the test.  This also handles other
# OS'es that don't support /dev/tty.
pass
else:
self.assertEqual(f.readable(), False)
self.assertEqual(f.writable(), True)
if sys.platform != "darwin" and \
   'bsd' not in sys.platform and \
   not sys.platform.startswith('sunos'):
# Somehow /dev/tty appears seekable on some BSDs
self.assertEqual(f.seekable(), False)
self.assertEqual(f.isatty(), True)
f.close()

(I'm not 100% sure that the line was this f.seekable() check.)

--
nosy: +haypo

___
Python tracker 

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

[issue25282] Support for recursive patterns

[R. David Murray]

R. David Murray added the comment:

According to this:

   http://www.rexegg.com/regex-recursion.html

regex supports recursive regex, so the thing to do would be to help work toward 
getting regex into the standard library (what we need for that, from what I 
understand, is code reviews).

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

[issue25282] regex: Support for recursive patterns

[STINNER Victor]

Changes by STINNER Victor :


--
title: Support for recursive patterns -> regex: Support for recursive patterns

___
Python tracker 

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

[issue15663] Investigate providing Tcl/Tk 8.6 with OS X installers

[Ned Deily]

Ned Deily added the comment:

"the install_name_tool lets you point a shared library at a different dependent 
shared library than the one it was originally compiled to link against"

Yes, but I'm not sure how we can take advantage of that.  First, keep in mind 
that there is only one version of _tkinter.so per Python installation and that 
is used by all tkinter applications, not just IDLE.  Second, the 
install_name_tool is not part of the base OS X system; it is included with 
either Xcode.app or the Command Line Tools package.  So we can't assume it will 
be available on users' systems.  And, third, changing the Tk library path may 
still break other third-party Python packages that also link directly with Tk 
and expect it to be in {/System}/Library/Frameworks.

"Secondly, we may want to consider adding something post-install (in IDLE?) 
where it would detect at least simpler cases of greatly out-of-date Tcl/Tk and 
offer to download and install a new one." 

That could be a useful addition and one that we could probably do in the 
context of a maintenance release.  The main problem I see with that is what to 
offer to install.  Since there is no truly open-source compatible option, I 
think we would need to provide our own Tcl/Tk 8.5.x package to install.  It's 
something to consider.

--

___
Python tracker 

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

[issue25282] Support for recursive patterns

[Sworddragon]

New submission from Sworddragon:

It seems Python's own regular expressions aren't able of handling nested 
structures so maybe this can be enhanced like it is done with PCRE's recursive 
patterns.

--
components: Library (Lib)
messages: 251951
nosy: Sworddragon
priority: normal
severity: normal
status: open
title: Support for recursive patterns
type: enhancement
versions: Python 3.4

___
Python tracker 

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

[issue15663] Investigate providing Tcl/Tk 8.6 with OS X installers

[Mark Roseman]

Mark Roseman added the comment:

Thanks Ned. 

A couple of things. First, you probably know about this, but for future 
reference in case it might be useful, the install_name_tool lets you point a 
shared library at a different dependent shared library than the one it was 
originally compiled to link against (see end of 
http://www.tkdocs.com/tutorial/fonts.html). This can be sometimes helpful in 
resolving compatibility issues. 

Secondly, we may want to consider adding something post-install (in IDLE?) 
where it would detect at least simpler cases of greatly out-of-date Tcl/Tk and 
offer to download and install a new one. If it were in IDLE, this would have 
the advantage of not affecting everyone who installs Python, but only (a subset 
of) those who would benefit. Plus, not being a "you must decide now" like an 
installer, it could be deferred if people weren't sure. And it would offer to 
provide a bit more active assistance rather than only "go read a web page".

--

___
Python tracker 

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

[issue25283] Make tm_gmtoff and tm_zone available on all platforms

[Alexander Belopolsky]

New submission from Alexander Belopolsky:

See datetime-sig thread [1] for details.

[1]: https://mail.python.org/pipermail/datetime-sig/2015-September/000955.html

--
assignee: belopolsky
messages: 251954
nosy: belopolsky
priority: normal
severity: normal
stage: needs patch
status: open
title: Make tm_gmtoff and tm_zone available on all platforms
type: enhancement
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