date:20150923


Terry J. Reedy added the comment:

List indent glitch: In the command line section, after the box, idle.rst has 

If there are arguments:

#. If ``-``, ``-c``, or ``r`` is used, all arguments are placed in
   ``sys.argv[1:...]`` and ``sys.argv[0]`` is set to ``''``, ``'-c'``,
   or ``'-r'``.  No editor window is opened, even if that is the default
   set in the Options dialog.

Firefox shows this as (but does not allow copying of '1. ')

If there are arguments:

1. If -, -c, or r is used, all arguments are placed in sys.argv[1:...] and 
sys.argv[0] is set to '', '-c', or '-r'. No editor window is opened, even if 
that is the default set in the Options dialog.

The help window shows this, for example, (but not copy indent) as

If there are arguments: 

  * If -, -c, or r is used, all arguments are placed in sys.argv[1:...] and 
sys.argv[0] is set to
'', '-c', or '-r'.  No editor window is opened, even if that is the default set 
in the Options dialog.

The point is not '1. ' versus '* ', this being the only place where idle.rst 
uses '#' for a list (and I changed this).  The problem is the dedent of the 
second line.  This only occurs if the second line starts with a font change.  
If I narrow the window so it begins with 'to', the line is indented properly. 
Narrow further so it begins with 'sys', no ident. I am pretty sure I have not 
touched your indent code.  Any ideas on how to fix?  or a tk glitch?

--

___
Python tracker 

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

[issue22052] Comparison operators called in reverse order for subclasses with no override.

2015-09-23 Thread Mark Dickinson


Mark Dickinson added the comment:

For Python 2, I think the most we should do is document the behaviour 
somewhere; changing it in a bugfix release seems both unnecessary and 
potentially risky.

--

___
Python tracker 

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

[issue22052] Comparison operators called in reverse order for subclasses with no override.

2015-09-23 Thread Mark Dickinson


Mark Dickinson added the comment:

> the most we should do is document the behaviour somewhere

And indeed, perhaps this issue counts as sufficient documentation...

--

___
Python tracker 

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

[issue25117] Windows installer: precompiling stdlib fails with missing DLL errors

2015-09-23 Thread Marius Gedminas


Marius Gedminas added the comment:

For the record, I rebooted once, after installing both 32-bit and 64-bit 
versions of Python 3.5.

(Also, it seems that the Python 3.5 installer didn't install pip for me, which 
could be fallout from this bug?  I had to run python -m ensurepip to get it.)

--

___
Python tracker 

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

[issue19143] Finding the Windows version getting messier (detect windows 8.1?)

2015-09-23 Thread Marc-Andre Lemburg


Marc-Andre Lemburg added the comment:

On 23.09.2015 02:33, Steve Dower wrote:
> 
> Done.

Thanks.

> As this is (meant to be) a purely informational/diagnostic module, seems like 
> a good idea to fix every version we're supporting in any way.

Yep, that's the intention behind the platform module.

--

___
Python tracker 

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

[issue25219] Update doc for Idle command line argument.


Roundup Robot added the comment:

New changeset 80e92eba23e0 by Terry Jan Reedy in branch '2.7':
Issue #25219: Update doc for Idle command line options.
https://hg.python.org/cpython/rev/80e92eba23e0

New changeset 97f3d7749d3f by Terry Jan Reedy in branch '3.4':
Issue #25219: Update doc for Idle command line options.
https://hg.python.org/cpython/rev/97f3d7749d3f

--
nosy: +python-dev

___
Python tracker 

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

[issue25219] Update doc for Idle command line arguments.


Changes by Terry J. Reedy :


--
assignee:  -> terry.reedy

___
Python tracker 

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

[issue25219] Update doc for Idle command line arguments.


Changes by Terry J. Reedy :


--
title: Update doc for Idle command line argument. -> Update doc for Idle 
command line arguments.

___
Python tracker 

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

[issue25219] Update doc for Idle command line options.


Changes by Terry J. Reedy :


--
title: Update doc for Idle command line arguments. -> Update doc for Idle 
command line options.

___
Python tracker 

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

[issue9928] weird oddity with bz2 context manager

2015-09-23 Thread Roman Valls


Roman Valls added the comment:

It still seems to be failing with Python 2.7.10... or am I doing sth wrong? :/


$ ipython
Python 2.7.10 |Anaconda 2.2.0 (x86_64)| (default, May 28 2015, 17:04:42)
Type "copyright", "credits" or "license" for more information.

IPython 4.0.0 -- An enhanced Interactive Python.
? -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help  -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.

In [1]: import bz2
In [2]: import pandas as pd
In [3]: import numpy as np
In [4]: import matplotlib as plt
In [5]: import seaborn as sns
In [6]: import cPickle as pickle

In [7]: with open("./collectl_info.pickle.bz2", "rb") as comp:
   ...: with bz2.decompress(comp.read()) as decomp:
   ...: data, hardware, steps = pickle.load(decomp)
   ...:

---
AttributeErrorTraceback (most recent call last)
 in ()
  1 with open("./collectl_info.pickle.bz2", "rb") as comp:
> 2 with bz2.decompress(comp.read()) as decomp:
  3 data, hardware, steps = pickle.load(decomp)
  4

AttributeError: __exit__

--
nosy: +Roman Valls
versions:  -Python 3.1, Python 3.2

___
Python tracker 

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

[issue25148] Windows registry PythonCore key changed inconsistent with other releases

2015-09-23 Thread Barry Scott


Barry Scott added the comment:

To clarify:

3.5 means 3.5 64 bit
3.5-32 means 3.5 32 bit

You do not add the -64 as it is the default.

However: this change should have been in the "What's New" as it breaks Windows 
installation code for extensions.

--

___
Python tracker 

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

[issue1401] urllib2 302 POST

2015-09-23 Thread RuixiaZhang


RuixiaZhang added the comment:

I am using  python 2.7,the same ,come to 302 lost cookies,
I try add the code :
req.headers.pop('content-length')
to urllib2.py:536
but, have another error:
KeyError: 'content-length'
So, I want to ask is there any better method to solver this error?

--
components: +Windows -XML
nosy: +paul.moore, steve.dower, tim.golden, zach.ware, zhangruixia0108
versions: +Python 2.7 -Python 2.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

2015-09-23 Thread Larry Hastings


Larry Hastings added the comment:

Okay.  I got tired of the constant Misc/NEWS merge conflicts, so I wrote a tool 
to fix the problem.  It's checked in to Bitbucket here:

https://bitbucket.org/larry/mergenews/

There's a readme, which you'll see rendered on that page.

I don't know what you mean by "attach Misc/NEWS entries to the issue tracker".  
I figure, the Misc/NEWS entry is used as the checkin comment, so Roundup Robot 
already adds it for you, so maybe that's good enough.

Can we maybe switch to this for 3.6?  Should we consider switching all 3.x 
branches under active development to use this approach?

--

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


New submission from STINNER Victor:

The Lib/test/regrtest.py file became a monster. It's very long, it uses a lot 
of global variables. It's hard to review and hard to maintain. I propose to:

- split single file regrtest.py into multiple files in a new Lib/test/regrtest/ 
package
- refactor the test runner as a class to avoid global variables
- refactor the multiprocessing test runner as a class in a separated file

Attached patch implements this idea.


The following commands still work:

   ./python -m test [options] [args]
   ./python -m test.regrtest [options] [args]

But the following command doesn't work anymore:

   ./python Lib/test/regrtest.py [options] [args]

If regrtest.py is executed directly on buildbots, these buildbots should be 
modified first.


The "./python -m test.regrtest" command should work on all Python versions 
(Python 2 and Python 3) and so should be preferred. The "./python -m test" 
command only works on Python 3 (thanks to the new __main__.py feature).


The change adds a new feature: it now displays name of concurrent tests running 
since 30 seconds or longer when the multiprocessing test runner is used (-j 
command line option). Example:

...
[240/399] test_uu
[241/399] test_urllib_response
[242/399] test_struct
[243/399] test_descrtut
[244/399] test_threadedtempfile
[245/399] test_tracemalloc -- running: test_concurrent_futures (30 sec)
[246/399] test_dbm_dumb -- running: test_concurrent_futures (30 sec)
[247/399] test_codeop -- running: test_concurrent_futures (30 sec)
...
[395/399/1] test_asyncio -- running: test_multiprocessing_fork (40 sec), 
test_multiprocessing_spawn (44 sec)
[396/399/1] test_faulthandler -- running: test_multiprocessing_fork (50 
sec), test_multiprocessing_spawn (54 sec)
[397/399/1] test_multiprocessing_fork (52 sec) -- running: 
test_multiprocessing_spawn (56 sec)
[398/399/1] test_multiprocessing_spawn (68 sec) -- running: 
test_multiprocessing_forkserver (39 sec)
[399/399/1] test_multiprocessing_forkserver (50 sec)

I want this feature to analysis why more and more buildbots fail with a timeout 
without saying which test was running (well, I suspect multiprocessing 
tests...).

Note: faulthandler can show where regrtest is blocked, but not when the 
multiprocessing test runner is used. And sometimes the process is killed by the 
buildbot, not by faulthandler :-/


Another minor new feature: on CTRL+c, it shows which tests are running when the 
multiprocessing test runner is used. Example:

[ 38/399] test_dummy_thread
[ 39/399] test_codecmaps_jp
[ 40/399] test_future5
^C
Waiting for test_scope, test_decimal, test_memoryview, test_heapq, 
test_unicodedata, test_trace, test_threadsignals, test_cgitb, test_runpy, 
test_cmd_line_script


Other changes:

* Show test timing when a test runs longer than 30 seconds

* Don't make __file__ absolute, findtestdir() calls os.path.abspath() instead. 
Remove these lines:

__file__ = os.path.abspath(__file__)
assert __file__ == os.path.abspath(sys.argv[0])

* print() is now called wih flush=True (it didn't check all calls, only the 
major calls), remove sys.stdout.flush() and  sys.stdout.flush()

* A lot of refactoring. Sorry, I didn't take notes for each change.


I fear that test_regrtest has a small code coverage. I only tested major 
options, I didn't test -R for example.


Note: I don't understand how the --single option works when regrtest is not run 
from the Python source code directory. A temporary directory, so the pynexttest 
file is removed after its creation, no? If it doesn't make sense to use 
--single outside Python directory, maybe an error should be raised?

--
components: Tests
files: regrtest_package.patch
keywords: patch
messages: 251419
nosy: ezio.melotti, haypo, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Enhance and refactor test.regrtest (convert regrtest.py to a package)
versions: Python 3.6
Added file: http://bugs.python.org/file40554/regrtest_package.patch

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

2015-09-23 Thread Jeremy Kloth


Changes by Jeremy Kloth :


--
nosy: +jkloth

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

2015-09-23 Thread Serhiy Storchaka


Serhiy Storchaka added the comment:

середа, 23-вер-2015 10:12:35 STINNER Victor написано:
> New submission from STINNER Victor:
> 
> The Lib/test/regrtest.py file became a monster. It's very long, it uses a
> lot of global variables. It's hard to review and hard to maintain. I
> propose to:
> 
> - split single file regrtest.py into multiple files in a new
> Lib/test/regrtest/ package

You can just mover parts of the code into utility files (or to the test.support 
package) without converting regrtest.py to a package. This preserves 
compatibility with running Lib/test/regrtest.py as a script.

> - refactor the test runner as a class to avoid global variables

Global variables are not evil in a script. Are there other reasons besides 
aesthetic?

--

___
Python tracker 

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

[issue25131] The AST for dict and set displays has the lineno of the first value

2015-09-23 Thread Berker Peksag


Changes by Berker Peksag :


--
keywords: +3.5regression

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


Martin Panter added the comment:

I never used --single, but quickly looking at the code, it looks like the 
pynexttest file got stored in /tmp or similar, via tempfile.gettempdir(), so it 
should usually survive. However it looks like your patch now creates 
“pynexttest” in a temporary directory that gets removed at the end?

Left another comment on Rietveld about out of date stuff in __main__.

--
nosy: +martin.panter

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

2015-09-23 Thread Berker Peksag


Berker Peksag added the comment:

I like the new features, but I think we should take a look at issue 10967 
before converting it to a package or refactoring it.

The buildbot part is also a bit complicated. For example, support.verbose 
doesn't work correctly on builtbots: issue 23235.

--
nosy: +berker.peksag

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


STINNER Victor added the comment:

Serhiy Storchaka wrote:
"""
You can just mover parts of the code into utility files (or to the test.support 
package) without converting regrtest.py to a package. This preserves 
compatibility with running Lib/test/regrtest.py as a script.
"""

Does it really matter? Who runs directly Lib/test/regrtest.py? It's simple to 
replace Lib/test/regrtest.py with -m test (or -m test.regrtest), no?

Serhiy Storchaka wrote: "Global variables are not evil in a script. Are there 
other reasons besides 
aesthetic?"

It's much easier to split a long function using multiple small functions when 
no global variable is used. I also like OOP, so I created a class. Should I 
understand that you don't like classes and would prefer to keep flat functions?

Martin Panter wrote:
"I never used --single, but quickly looking at the code, it looks like the 
pynexttest file got stored in /tmp or similar, via tempfile.gettempdir(), so it 
should usually survive. However it looks like your patch now creates 
“pynexttest” in a temporary directory that gets removed at the end?"

Ah ok, it's /tmp. I misunderstood the code. I understand that it creates a 
temporary subdirectory and write into the temporary subdirectory which will be 
removed.

Berker Peksag: "I like the new features, but I think we should take a look at 
issue 10967 before converting it to a package or refactoring it."

Even if we move some features to unittest, I don't think that regrtest.py will 
be reduced to fewer than 100 lines of code. By the way, most reusable code is 
in test.support. test.regrtest is much more specific to the CPython test suite, 
no?

Berker Peksag: "The buildbot part is also a bit complicated. For example, 
support.verbose doesn't work correctly on builtbots: issue 23235."

Sorry, I don't see the link with this issue. How are these two issues related?

--

___
Python tracker 

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

[issue25214] asyncio ssl transport regression

2015-09-23 Thread Andrew Svetlov


Andrew Svetlov added the comment:

I've missed your patch, sorry.

Everything is fixed by http://bugs.python.org/issue25114

--
resolution:  -> duplicate
stage:  -> resolved

___
Python tracker 

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

[issue25214] asyncio ssl transport regression


STINNER Victor added the comment:

> I've missed your patch, sorry.

There is no need to be sorry :-)

> Everything is fixed by http://bugs.python.org/issue25114

Wow, great :-)

Thanks again Mathieu Pasquet who reported the issue #22768.

--
status: open -> closed
superseder:  -> asyncio: add ssl_object extra info

___
Python tracker 

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

[issue19084] No way to use TLS-PSK from python ssl

2015-09-23 Thread Luiz Francisco Artigas de Prá


Changes by Luiz Francisco Artigas de Prá :


--
nosy: +Luiz Francisco Artigas de Prá

___
Python tracker 

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

[issue25214] asyncio ssl transport regression

2015-09-23 Thread Andrew Svetlov


Andrew Svetlov added the comment:

BTW for fingerprint check for self-signed certs I need binary form of 
certificate `ssl_obj.getpeercert(binary_form=True)` but 
`transp.get_extra_info('peercert')` returns a dict-based form.

--

___
Python tracker 

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

[issue25214] asyncio ssl transport regression


STINNER Victor added the comment:

>> Thanks again Mathieu Pasquet who reported the issue #22768.

> BTW for fingerprint check for self-signed certs I need binary form of 
> certificate `ssl_obj.getpeercert(binary_form=True)` but 
> `transp.get_extra_info('peercert')` returns a dict-based form.

Yes, it's exactly the use case described in #22768 ;-) But ssl_object extra 
info is more generic, it gives access to all SSL methods.

--

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


STINNER Victor added the comment:

"I want this feature to analysis why more and more buildbots fail with a 
timeout without saying which test was running (well, I suspect multiprocessing 
tests...)."

Recent example:

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

...

[395/399] test_pep352
[396/399] test_ioctl
[397/399] test_multiprocessing_fork
[398/399] test_multiprocessing_forkserver

command timed out: 3900 seconds without output running ['make', 'buildbottest', 
'TESTOPTS= -j4', 'TESTPYTHONOPTS=', 'TESTTIMEOUT=3600'], attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=4949.196279

--

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


STINNER Victor added the comment:

Another recent example:

http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.x/builds/6712/steps/test/logs/stdio

...
[395/399] test_asyncio
[396/399] test_email
[397/399] test_threaded_import
[398/399] test_tools

command timed out: 3900 seconds without output, attempting to kill
program finished with exit code 1
elapsedTime=4958.515000

--

___
Python tracker 

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

[issue9928] weird oddity with bz2 context manager

2015-09-23 Thread Armin Rigo


Armin Rigo added the comment:

Roman: bz2.decompress(comp.read()) returns a string, so you can't use "with" on 
it.  This bug was about using "with bz2.BZ2File(...) as f:".

--

___
Python tracker 

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

[issue9928] weird oddity with bz2 context manager

2015-09-23 Thread Roman Valls


Roman Valls added the comment:

Gotcha, sorry about that :-S

On Wed, Sep 23, 2015 at 4:43 PM, Armin Rigo  wrote:
>
> Armin Rigo added the comment:
>
> Roman: bz2.decompress(comp.read()) returns a string, so you can't use "with" 
> on it.  This bug was about using "with bz2.BZ2File(...) as f:".
>
> --
>
> ___
> Python tracker 
> 
> ___

--

___
Python tracker 

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

[issue25194] Register of Financial Interests for core contributors


R. David Murray added the comment:

What about those of us who would *like* to broadcast our availability? :)

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

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

2015-09-23 Thread Larry Hastings


Larry Hastings added the comment:

In case you're too lazy to go visit the link to my "mergenews" repository and 
read the readme...

mergenews has three tools:

* splitnews, which splits the existing Misc/NEWS file into hundreds of 
individual files,
* mergenews, which merges the hundreds of individual files back into a single 
coherent Misc/NEWS file, and
* pyci, a front-end for "hg ci" which automatically writes out the checkin 
comment as a new news entry into the right spot so mergenews will see it.

It's all basically working already.  pyci limits you in what command-line 
options it supports, other than that I think it all does what you want.  Can we 
use it please?  ;-)

--

___
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

2015-09-23 Thread Brett Cannon


Brett Cannon added the comment:

What I mean by "attach Misc/NEWS entries to the issue tracker" is there will 
literally be a field in the issue tracker to enter the entry for the change log 
and Misc/NEWS will simply be auto-generated from the issue tracker. You can't 
use the commit message for what to put in the change log because too many 
people are against that solution (trust me, I tried to convince them otherwise).

--

___
Python tracker 

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

[issue25083] Python can sometimes create incorrect .pyc files

2015-09-23 Thread tzickel


tzickel added the comment:

Although I haven't reviewed python 3.5 code, I've put an breakpoint on calling 
"ferror" in the debugger, and it seems that python 3 does not check the file 
status on import as well...

--
nosy: +eric.snow, ncoghlan

___
Python tracker 

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

[issue25221] PyLong_FromLong() potentially returns irregular object when small_ints[] isn't used

2015-09-23 Thread s-wakaba


New submission from s-wakaba:

When compiling cpython with specifying NSMALLPOSINTS and NSMALLNEGINTS macros 
as zero to skip making small_ints[] array, like following command, process 
couldn't finish.

$ ./configure CPPFLAGS='-DNSMALLPOSINTS=0 -DNSMALLNEGINTS=0'
$ make

The reason looks a problem that PyLong_FromLong(0) returns irregular int 
object: Py_SIZE(zero_int) must be 0, but it becomes 1.

maybe this problem never appears in actual cases, but in "longobject.c", it 
still looks supported to compile without small_ints[].
I don't know it should be fixed or not. but, as a result, I could compile 
cpython after addition of one line like attached patch.
Could you confirm this point?

Thanks.

--
components: Interpreter Core
files: longobject.c.patch
keywords: patch
messages: 251436
nosy: s-wakaba
priority: normal
severity: normal
status: open
title: PyLong_FromLong() potentially returns irregular object when small_ints[] 
isn't used
type: behavior
versions: Python 3.5
Added file: http://bugs.python.org/file40555/longobject.c.patch

___
Python tracker 

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

[issue25205] setattr accepts invalid identifiers


R. David Murray added the comment:

I wouldn't call the sendfile case troublesome.  'in' is a keyword, so if you 
want to use it in function arguments, you have to pass it as a string.  
Perfectly logical :)

IIRC pypy uses an optimized dictionary if there are no non-identifier keywords 
in the attribute __dict__.  I *think* it supports non-identifiers by falling 
back to a slower implementation, but I could be wrong.  I seem to remember a 
discussion where it was ruled that the fact that CPython's default __dict__ 
accepts non-identifiers is a CPython implementation detail and code should not 
rely on it working...but of course some code does, so we can't "fix" it :).

If I'm remembering right, and if __dict__'s permissiveness is not noted as a 
CPython implementation detail in the language reference, it should be, but I 
would expect that it is since that discussion was one of the ones that 
triggered the introduction such documentation notes.

But, as MvL pointed out, setattr does *not* have this restriction, even if the 
python implementation rejects it for default __dicts__, because an object can 
do anything it wants during in its __setattr__ method, and this is an important 
(and used in the wild!) feature of the language.

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

[issue25205] setattr accepts invalid identifiers

2015-09-23 Thread eryksun


eryksun added the comment:

Even MvL appears to slip up when he states "some may accept non-strings as 
attribute names". That would be pointless in a __setattr__ method since setattr 
/ PyObject_SetAttr reject non-string values as 'names'.

--

___
Python tracker 

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

[issue23329] _ssl cannot be compiled with LibreSSL anymore (on OpenBSD 5.5) because of ALPN

2015-09-23 Thread Remi Pointel


Remi Pointel added the comment:

With this patch it works fine on OpenBSD with LibreSSL.
Could you test on a Linux machine with OpenSSL supporting ALPN please?

Thanks spil@ for the idea.

--
keywords: +patch
Added file: http://bugs.python.org/file40556/python_have_alpn.diff

___
Python tracker 

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

[issue25210] Special-case NoneType() in do_richcompare()


R. David Murray added the comment:

There are other places NoneType shows up (eg: attribute error).  Why should 
this case be special?  Do we want to fix them all?

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

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


R. David Murray added the comment:

Wording looks ok...except that technically it is not that 'n' is an integer, 
it's that 'n' can play the role of an integer (ie: it has an __index__ method).

--

___
Python tracker 

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

[issue23329] _ssl cannot be compiled with LibreSSL anymore (on OpenBSD 5.5) because of ALPN


Changes by STINNER Victor :


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

___
Python tracker 

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

[issue25143] 3.5 install fails poorly on Windows XP

2015-09-23 Thread Tim Golden


Tim Golden added the comment:

I'd just bail as early as poss. from the installer. If it's possible to 
detect Windows versions, stick something like "The last version to 
support WinXP is 3.4". If that's too tricky, perhaps something "Your 
system may be unsupported. Please try an earlier version of Python"

--

___
Python tracker 

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

[issue25164] Windows default installation path is inconsistent between per-user and system-wide installation

2015-09-23 Thread Tim Golden


Tim Golden added the comment:

I don't feel that strongly, but my preference would be 
"python35[-whatever]" rather than the version with the spaces & the 
dots. Both for ease of use and for some kind of continuity with the 
c:\pythonxy we've had for many years.

--

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


R. David Murray added the comment:

This may be opening a can of worms, but I wonder if what we should really do is 
re-engineer regrtest from the ground up, keeping the existing regrtest around 
until we are satisfied with its replacement...and maybe some of the options 
wouldn't make the transition.  (I've used --single, but it's been a long time, 
and I think it may have only been when I was testing regrtest after modifying 
it...)

We could then shift buildbots over to the new command gradually (or, do a few 
first, and then all the rest).  Then when we're satisfied we could change -m 
test to use the new interface, but keep regrtest around, unmaintained, for a 
couple of releases for those who are still using it.

I haven't looked at Victor's code to see if I like his re-engineering, but I'm 
really talking about starting the re-engineering from the API, and only then 
thinking about the code to implement it.

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

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


STINNER Victor added the comment:

"This may be opening a can of worms, but I wonder if what we should really do 
is re-engineer regrtest from the ground up,"

It's not a full reengineering. My patch takes the current code and split it 
into smaller files. It's not a new implementation or anything like that.

"keeping the existing regrtest around until we are satisfied with its 
replacement..."

why are you saying "replacement"? Replaced by what?

"(I've used --single, but it's been a long time, and I think it may have only 
been when I was testing regrtest after modifying it...)"

You can propose to remove this option if you think that it's useless. I don't 
want to touch options, I don't know how regrtest is used, and regrtest works 
right? (If it works, don't touch it :-))

"I haven't looked at Victor's code to see if I like his re-engineering, but I'm 
really talking about starting the re-engineering from the API, and only then 
thinking about the code to implement it."

Sorry, but writing a new regrtest project is a full new project. Please open a 
new issue if you want to invest time on that.

--

___
Python tracker 

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

[issue25210] Special-case NoneType() in do_richcompare()


STINNER Victor added the comment:

R. David Murray wrote: "There are other places NoneType shows up (eg: attribute 
error).  Why should this case be special?  Do we want to fix them all?"

I think you missed the last sentence of the initial message :-) We are simply 
discussing a comment :-D

Ezio wrote: "if not, the comment should be removed."

Come on, just remove the comment, that's all ;-)

--

___
Python tracker 

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

[issue25205] setattr accepts invalid identifiers


R. David Murray added the comment:

I did however make the same mistake without checking the docs or the behavior.  
But the fact that I didn't look at it doesn't make the current documentation 
wrong :)

What change is it that you think would be beneficial?

--

___
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


Terry J. Reedy added the comment:

Larry: commit messages are for other developers, which news entries are 
ultimately for users.  Some developers want (insist on) the freedom to make the 
two different, with different details.  I am using that for Idle patches since 
NEWS entries become 'What New for Idle' in each release.

Brett, I presume that you mean a new NEWS box like this Comment box, maybe with 
3 lines and a new Section: box like Components.  Question: Is it impossible to 
put labels above a box rather than to the right?   

We could allow that news section to be (initially) filled out by someone other 
than the committer.  Latter could (optionally) copy and paste as (initial draft 
of) commit message.  Having message visible on issue might result in typos 
being corrected sooner, and would make it much easier to edit news message 
later (But editing after close should be limited to core devs).

Larry, a commit hook would be better that a separate pyci since TortoiseHG 
[Commit] button would still work.  With Brett's solution, a commit hook could 
email commit message to tracker as NEWS message (if empty).  And yes, change 
should apply to all versions.  Otherwise, NEWS commits to older versions would 
have to be null-merged.

--
components: +2to3 (2.x to 3.x conversion tool)

___
Python tracker 

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

[issue25194] Register of Financial Interests for core contributors

2015-09-23 Thread Antoine Pitrou


Antoine Pitrou added the comment:

What would be the rules for how to fill this up?

For example, I work for Continuum, which develops Conda and Anaconda, but I'm 
not paid to work on CPython (I work on Numba). However, perhaps someone might 
want to ask for CPython work that aligns with Continuum's interests, and then 
I'd obviously be in the loop for the actual work.

--
nosy: +pitrou

___
Python tracker 

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

[issue25085] Windows x86-64 embeddable zip file contains test directorys


Terry J. Reedy added the comment:

Thanks, re-reading I see the new exclusion test for this issue:
  if name in {'test', 'tests'} and p.parts[-3].lower() == 'lib':

--

___
Python tracker 

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

[issue25194] Register of Financial Interests for core contributors


R. David Murray added the comment:

Antoine: think that's exactly what Nick has in mind, exposing that kind of 
information.

--

___
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

2015-09-23 Thread Brett Cannon


Brett Cannon added the comment:

Yes, a text box or something along those lines. I assume the selection label 
question is to specify a section of the change log for something to go into. 
That's actually not necessary as the proper section is implied by the 
Components label.

And we could allow people to initially fill it in if desired, but I think 
worrying about whether to open it up or not is premature optimization; I'm fine 
with starting with it for only people with Developer privileges on the issue 
tracker.

--
components:  -2to3 (2.x to 3.x conversion tool)

___
Python tracker 

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

[issue25222] 3.5.0 regression - Fatal Python error: Cannot recover from stack overflow

2015-09-23 Thread Bernie Hackett


New submission from Bernie Hackett:

While running PyMongo's test suite against python 3.5.0 the interpreter 
inconsistently aborts when we test encoding a recursive data structure like:

evil = {}
evil['evil'] = evil

The test that triggers this was added to test the use of Py_EnterRecursiveCall 
in PyMongo's C extensions and passes without issues on all previous CPython 
releases back to 2.4.x (the oldest version PyMongo supports). The interesting 
thing about this abort is that it only occurs when testing PyMongo *without* 
its C extensions. The stacktrace looks like this:

test_bad_encode (test_bson.TestBSON) ... Exception ignored in: >
RecursionError: maximum recursion depth exceeded while calling a Python object
Fatal Python error: Cannot recover from stack overflow.
 
Thread 0x0b6c (most recent call first):
  File "C:\10gen\mongo-python-driver\pymongo\periodic_executor.py", line 105 in 
_run
  File "C:\Python35\lib\threading.py", line 871 in run
  File "C:\Python35\lib\threading.py", line 923 in _bootstrap_inner
  File "C:\Python35\lib\threading.py", line 891 in _bootstrap
 
Thread 0x0690 (most recent call first):
  File "C:\Python35\lib\threading.py", line 297 in wait
  File "C:\10gen\mongo-python-driver\pymongo\thread_util.py", line 199 in wait
  File "C:\10gen\mongo-python-driver\pymongo\periodic_executor.py", line 110 in 
_run
  File "C:\Python35\lib\threading.py", line 871 in run
  File "C:\Python35\lib\threading.py", line 923 in _bootstrap_inner
  File "C:\Python35\lib\threading.py", line 891 in _bootstrap
 
Thread 0x0900 (most recent call first):
  File "C:\Python35\lib\threading.py", line 297 in wait
  File "C:\10gen\mongo-python-driver\pymongo\thread_util.py", line 199 in wait
  File "C:\10gen\mongo-python-driver\pymongo\periodic_executor.py", line 110 in 
_run
  File "C:\Python35\lib\threading.py", line 871 in run
  File "C:\Python35\lib\threading.py", line 923 in _bootstrap_inner
  File "C:\Python35\lib\threading.py", line 891 in _bootstrap
 
Current thread 0x0a20 (most recent call first):
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 653 in 
_name_value_to_bson
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 692 in 
_element_to_bson
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 433 in 
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 433 in 
_encode_mapping
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 653 in 
_name_value_to_bson
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 462 in 
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 462 in _encode_list
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 653 in 
_name_value_to_bson
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 692 in 
_element_to_bson
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 433 in 
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 433 in 
_encode_mapping
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 653 in 
_name_value_to_bson
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 462 in 
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 462 in _encode_list
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 653 in 
_name_value_to_bson
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 692 in 
_element_to_bson
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 433 in 
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 433 in 
_encode_mapping
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 653 in 
_name_value_to_bson
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 462 in 
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 462 in _encode_list
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 653 in 
_name_value_to_bson
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 692 in 
_element_to_bson
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 433 in 
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 433 in 
_encode_mapping
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 653 in 
_name_value_to_bson
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 462 in 
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 462 in _encode_list
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 653 in 
_name_value_to_bson
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 692 in 
_element_to_bson
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 433 in 
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 433 in 
_encode_mapping
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 653 in 
_name_value_to_bson
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 462 in 
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 462 in _encode_list
  File "C:\10gen\mongo-python-driver\bson\__init__.py", line 653 in 
_name_value_to_bson
  File "C:

[issue25222] 3.5.0 regression - Fatal Python error: Cannot recover from stack overflow


Changes by STINNER Victor :


--
nosy: +haypo

___
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 added the comment:

I believe auto-filling it from the commit message (for those who don't put in 
the effort to treat the two audiences differently :) was something we 
discussed, but it would be a separate enhancement after the news box is added 
to the tracker.  Which I might get to next month or I might not...

--

___
Python tracker 

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

[issue25222] 3.5.0 regression - Fatal Python error: Cannot recover from stack overflow

2015-09-23 Thread A. Jesse Jiryu Davis


Changes by A. Jesse Jiryu Davis :


--
nosy: +emptysquare

___
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 added the comment:

New changeset eaf9a99b6bb8 by Victor Stinner in branch 'default':
Issue #25220: Create Lib/test/libregrtest/
https://hg.python.org/cpython/rev/eaf9a99b6bb8

--
nosy: +python-dev

___
Python tracker 

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

[issue25210] Special-case NoneType() in do_richcompare()


R. David Murray added the comment:

I was agreeing with you, I think the comment should just be dropped.  My point 
was the alternative is really to change it everywhere, not just here :)

--

___
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 added the comment:

New changeset c92d893fd3c8 by Victor Stinner in branch 'default':
Issue #25220: Backed out changeset eaf9a99b6bb8
https://hg.python.org/cpython/rev/c92d893fd3c8

--

___
Python tracker 

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

[issue25154] Drop the pyvenv script

2015-09-23 Thread Brett Cannon


Brett Cannon added the comment:

python-dev did not seem to object to the idea.

--
assignee:  -> brett.cannon

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


STINNER Victor added the comment:

I pushed the changeset eaf9a99b6bb8, but R. David Murray asked me to wait for a 
review before pushing changes. So I reverted my change.

I checked if Lib/test/regrtest.py is called directly. The answer is yes: it's 
called inside Python in various places, but also in scripts to build Python 
packages. Even if "python -m test" works (and "python -m test.regrtest" works 
on all Python versions), I prefer to keep Lib/test/regrest.py to not force 
users to have to modify their script.

So I propose to simply move regrtest.py code to smaller files in 
Lib/test/libregrtest/, as I did in attached regrtest_package.patch.

In the changeset eaf9a99b6bb8, I started with cmdline.py because it's the only 
part of regrtest.py which has real unit tests. I created 
Lib/test/libregrtest/cmdline.py with "hg cp" to keep Mercurial history. I 
checked which moved symbols are used: _parse_args() and RESOURCE_NAMES. I 
exported them in test.libregrtest. I had to modify Lib/test/test_regrtest.py.

For next changes, I will try to add a few new unit tests to 
Lib/test/test_regrtest.py.

--

Berker wrote: "I like the new features, but I think we should take a look at 
issue 10967 before converting it to a package or refactoring it."

IMHO it will be easier to enhance regrtest to reuse unit test features, make 
the code smaller, fix bugs, etc. if regrtest.py is splitted into smaller files. 
Moving code to a new test.libregrtest submodule should help to implement the 
issue #10967 & friends (ex: #16748)

--

___
Python tracker 

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

[issue13253] 2to3 fix_renames renames sys.maxint only in imports

2015-09-23 Thread Nikita Klimov


Nikita Klimov added the comment:

I'm close to solution, but I need another 1 week.

--

___
Python tracker 

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

[issue25222] 3.5.0 regression - Fatal Python error: Cannot recover from stack overflow


STINNER Victor added the comment:

I'm not sure that I understood the bug.

You are testing a function which enters an unlimited loop. You expect to get a 
RecursionError, but Python does crash.

Well, Python has no perfect protection again stack overflow. It's only best 
effect. You should change sys.setrecursionlimit() to a lower limit to try to 
limit the risk of a crash.

It's hard to predict how the stack will be used.

FYI the error message comes from Python/ceval.c:

if (tstate->overflowed) {
if (tstate->recursion_depth > recursion_limit + 50) {
/* Overflowing while handling an overflow. Give up. */
Py_FatalError("Cannot recover from stack overflow.");
}
return 0;
}

I suggest you to use sys.setrecursionlimit() in your test, or remove the test.

Maybe there is a real bug, but if it's the case, it will probably be hard to 
investigate it. You need to dig into gdb.

--

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


R. David Murray added the comment:

Victor and I have been discussing this on IRC.  We agreed that importing from 
regrtest and running regrtest as a script needs to keep working.

Summary of my disagreements: I'm leery of wholesale changes to regrtest
because we have gotten bug reports when we've broken things before.  Obviously 
it's not in the same problem-class as breaking Python, but I'd rather see us 
start a new command that drops the cruft and just does the things we really 
use, and stop maintaining regrtest.  However, I'm not in a position to do that 
work, and Victor has no interest in it.  So, I'm -0.5 on a big refactoring of 
regrtest (but have no objection to the new features :).  I won't block the 
change, I'd just prefer a cleaner solution...but don't have the time to 
implement it myself.

--

___
Python tracker 

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

[issue25223] Statically or dynamically linked to the VC++runtime ? or how Python install fails o Vista despite the VC redist packages - api-ms-win-crt-runtime-l1-1-0.dll

2015-09-23 Thread acx01bc

New submission from acx01bc:

I think you should build Python.exe with the option to be statically linked to
the VC++-runtime. This way, the executable is a little bigger, but you ensure
nobody will have troubles with some VC-runtime different Dll versions.

DETAILS : (I posted it also there
http://stackoverflow.com/questions/32748932/python-3-4-3-works-on-windows-vista-but-not-3-5-0-because-of-vc-redist-package
)

I am on Windows Vista 32bits. I downloaded Python 3.5.0 but I got the famous
api-ms-win-crt-runtime-l1-1-0.dll problem. Then I installed many Visual C++
Redistributable Packages (I tried the 2015's one, then 2013, and 2012) but none
of these packages installed any .dll of the correct name. Then, I tried to
download a previous version of Python, the 3.3.2 win32 release, I got the same
problem !

> Then, I downloaded the Python 3.4.3 Win32 release, and this-one worked
immediately. I suspect that version to have been statically linked with the
VC-runtime. This clearly lacks of coherence, some Python releases work, while
others don't. So I hope some of the Python developers will see that message and
will be able to build some binaries compatible with Windows Vista and the
VC-redist-packages.

Question : did anyone understand where that api-ms-win-crt-runtime-l1-1-0.dll
comes from ? I suppose it is related to the VC++ compiler options used when
building Python.exe (on my VS2010 I have the options code generation/runtime
library/multi-threaded, static or dynamic and general/platform_toolset, V100,
V110, V120 or V140) ?

--
components: Installation
messages: 251463
nosy: acx01bc
priority: normal
severity: normal
status: open
title: Statically or dynamically linked to the VC++runtime ? or how Python
install fails o Vista despite the VC redist packages -
api-ms-win-crt-runtime-l1-1-0.dll
type: crash
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

[issue25223] Statically or dynamically linked to the VC++runtime ? or how Python install fails on Vista despite the VC redist packages - api-ms-win-crt-runtime-l1-1-0.dll

2015-09-23 Thread acx01bc


Changes by acx01bc :


--
title: Statically or dynamically linked  to the VC++runtime ? or how Python 
install fails o Vista despite the VC redist packages - 
api-ms-win-crt-runtime-l1-1-0.dll -> Statically or dynamically linked  to the 
VC++runtime ? or how Python install fails on Vista despite the VC redist 
packages - api-ms-win-crt-runtime-l1-1-0.dll

___
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


New submission from Terry J. Reedy:

idlelib currently has user information that belongs in either the Idle 
reference idle.rst or possibly a separate Idle howto #17583. This information 
should be removed and replaced with an annotated list of files in idlelib.  The 
latter would help people working of Idle, and even people just browsing.

--
assignee: terry.reedy
components: IDLE
messages: 251464
nosy: terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: Replace Idle's README.txt with annotated file list
type: enhancement
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

[issue24894] iso-8859-11 missing from codecs table


STINNER Victor added the comment:

Issue24894.patch is wrong: latin is an alias to ISO 8859-1, not to ISO 8859-11.

>>> codecs.lookup('latin').name
'iso8859-1'

iso8859_11 has 3 aliases: thai, iso_8859_11, iso_8859_11_2001. You can mention 
iso-8859-11 and thai in the doc.

--

___
Python tracker 

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

[issue25222] 3.5.0 regression - Fatal Python error: Cannot recover from stack overflow

2015-09-23 Thread Bernie Hackett


Bernie Hackett added the comment:

> Well, Python has no perfect protection again stack overflow. It's only best 
> effect.

That's interesting. I thought there was a stronger contract, and it appeared 
that way in all previous cpython releases back to 2.4. Again, this failure is 
new with 3.5.0.

> You should change sys.setrecursionlimit() to a lower limit to try to limit 
> the risk of a crash.

That's a great suggestion and it appears to work around the issue, thanks.

Feel free to close this won't fix, but given that this appears to be the second 
report of this issue for 3.5 (see issue22971) someone who understands 
interpreter internals may want to look into the problem a bit more first.

--

___
Python tracker 

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

[issue24894] iso-8859-11 missing from codecs table

2015-09-23 Thread Prashant Tyagi


Prashant Tyagi added the comment:

That was mistake in previous patch,so here is new patch for the same.

--
Added file: http://bugs.python.org/file40557/issue_24894.patch

___
Python tracker 

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

[issue25225] Idle doc: redo Syntax Colors section


New submission from Terry J. Reedy:

I plan to make the following changes to the Syntax colors section:

* Change name to Text and syntax colors, as not all colors are code-syntax 
related.

* Make it a subsection of the previous Editing and navigation section, which is 
about editor and shell windows, which are what get colored. Begin by stating 
that both window types get colored.

* Greatly reduce excessive white space.  Put item and default color on one 
line, such as * Strings: green, and single space lines.

* Add missing item: color pairs

* Correct instruction on how to change defaults.

--
assignee: terry.reedy
messages: 251468
nosy: terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: Idle doc: redo Syntax Colors section
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

[issue25222] 3.5.0 regression - Fatal Python error: Cannot recover from stack overflow

2015-09-23 Thread Bernie Hackett


Bernie Hackett added the comment:

I used sys.setrecursionlimit(250) - the default appears to be 1000 on all my 
test machines - and that reduced the occurrence of the abort but didn't 
completely solve the problem. There must be something more going on here.

--

___
Python tracker 

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

[issue25223] Statically or dynamically linked to the VC++runtime ? or how Python install fails on Vista despite the VC redist packages - api-ms-win-crt-runtime-l1-1-0.dll

2015-09-23 Thread Mark Lawrence


Changes by Mark Lawrence :


--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, 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


Roundup Robot added the comment:

New changeset 5a60fdd9af8c by Terry Jan Reedy in branch '2.7':
Issue 25224: Augment Idle doc feature list and no-subprocess section
https://hg.python.org/cpython/rev/5a60fdd9af8c

New changeset 0f20f3fe7ab4 by Terry Jan Reedy in branch '3.4':
Issue 25224: Augment Idle doc feature list and no-subprocess section
https://hg.python.org/cpython/rev/0f20f3fe7ab4

New changeset b5c8a40d4240 by Terry Jan Reedy in branch '2.7':
Issue 25224: Augment Idle doc feature list and no-subprocess section
https://hg.python.org/cpython/rev/b5c8a40d4240

--
nosy: +python-dev

___
Python tracker 

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

[issue25223] Statically or dynamically linked to the VC++runtime ? or how Python install fails on Vista despite the VC redist packages - api-ms-win-crt-runtime-l1-1-0.dll

2015-09-23 Thread acx01bc


acx01bc added the comment:

With dependency walker I see that :
- in 3.4.3, Python34.exe and also Python.34.dll have been dynamically linked 
with msvcr100.dll (platform target : v100 in Visual C++ project properties), 
- while  in 3.5.0 (the one you download on python.org main page) Python35.exe 
and Python35.dll have been dynamically linked with msvcr140.dll and many other 
dlls (platform v140).

--
Added file: http://bugs.python.org/file40558/python_dll_problem.jpg

___
Python tracker 

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

[issue25211] Error message formatting errors in int object unit-test script


Martin Panter added the comment:

I will commit your patch to 2.7.

Here is a my alternative proposal for 3.4+, dropping the Frm class and using 
subTest() instead. I kept some error messages where I thought they added 
clarity, but dropped most because I thought they were redundant with the test 
code and subTest() parameters.

The test file takes a bit longer to run as a consequence of my patch (was 6.3 
s, now 7.3 s). However I think the simpler and more maintainable code outweighs 
this.

--
nosy: +berker.peksag
Added file: http://bugs.python.org/file40559/subTest-long.patch

___
Python tracker 

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

[issue25211] Error message formatting errors in int object unit-test script


Roundup Robot added the comment:

New changeset e2f1f69d0618 by Martin Panter in branch '2.7':
Issue #25211: Fix error message code in test_long; patch from s-wakaba
https://hg.python.org/cpython/rev/e2f1f69d0618

--
nosy: +python-dev

___
Python tracker 

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

[issue25164] Windows default installation path is inconsistent between per-user and system-wide installation

2015-09-23 Thread eryksun


eryksun added the comment:

Also, why does the per-user install path have a seemingly pointless "Python" 
base directory? I expected it to install directly into 
FOLDERID_UserProgramFiles, to be consistent with installing to 
FOLDERID_ProgramFiles.

Also, I doubt anyone cares, but the roaming "user scheme" is still using the 
name "Python35" without appending a -32 suffix. So 32-bit and 64-bit --user 
installs are still competing for the same site-packages directory. I know, 
hardly anyone seems to use this. I doubt Jane User wants large packages such as 
PyQt4 and SciPy in her roaming profile.

--
nosy: +eryksun

___
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 added the comment:

New patch mentioning __index__()

--
Added file: http://bugs.python.org/file40560/seq-inplace.v2.patch

___
Python tracker 

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

[issue25222] 3.5.0 regression - Fatal Python error: Cannot recover from stack overflow


Martin Panter added the comment:

I saw this error recently on some 3.4 builtbots:

http://buildbot.python.org/all/builders/AMD64%20Windows10%203.4/builds/74/steps/test/logs/stdio
 (failed last 4/5 builds)

[306/390] test_json
Fatal Python error: Cannot recover from stack overflow.

Current thread 0x0fd8 (most recent call first):
  File "D:\buildarea\3.4.bolen-windows10\build\lib\json\encoder.py", line 250 
in iterencode
  File "D:\buildarea\3.4.bolen-windows10\build\lib\json\encoder.py", line 192 
in encode
  File 
"D:\buildarea\3.4.bolen-windows10\build\lib\test\test_json\test_recursion.py", 
line 96 in test_endless_recursion

http://buildbot.python.org/all/builders/x86%20XP-4%203.4/builds/1224/steps/test/logs/stdio
 (only failed 1/5 builds, stack trace essentially the same)

--
nosy: +martin.panter

___
Python tracker 

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

[issue25223] Statically or dynamically linked to the VC++runtime ? or how Python install fails on Vista despite the VC redist packages - api-ms-win-crt-runtime-l1-1-0.dll

2015-09-23 Thread Steve Dower


Steve Dower added the comment:

None of them are statically linked, and we looked into that for 3.5 and it had 
other issues, so we went fully dynamically linked.

This is either an issue specific to your machine, or a Vista issue (we didn't 
get a lot of testing done on Vista).

Installing the VC 2015 redistributable from 
http://www.microsoft.com/en-us/download/details.aspx?id=48145 should include 
the files you need (as should installing Python 3.5.0 itself, but apparently 
that didn't work). The DLL should be under C:\Windows\System32.

--

___
Python tracker 

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

[issue25164] Windows default installation path is inconsistent between per-user and system-wide installation

2015-09-23 Thread Steve Dower


Steve Dower added the comment:

Good question on the extra "Python" directory - I don't recall exactly why that 
was there, but I suspect it was for consistency with something - probably 
{userbase} from sysconfig.

Also, thanks for catching the user scheme difference. We shouldn't really be 
installing any packages into the Roaming profile at all, but as this is a 
highly underused feature it's not a big deal. (And since we add platform tags 
to .pyd files now it can actually be used successfully, but I suspect that 
involves more care.)

--

___
Python tracker 

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

[issue24657] CGIHTTPServer module discard continuous '/' letters from params given by GET method.

2015-09-23 Thread Xiang Zhang


Xiang Zhang added the comment:

I think this is a bug. 

According to the rfcs, "/" is a reserved character in query component and 
continuous "/" in query component may be invalid and how to deal with it 
depends on the server. But encoded "/", %2F, acts as data and should be 
preserved. And from rfc3875, QUERY_STRING must be passed encoded.

I tested in apache2.4 with martin's script, query string is:

('QUERY_STRING', 'k=aa%2F%2Fbb&//q//p//=//a//b//')

In python's CGI server, it is:

('QUERY_STRING', 'k=aa/bb&/q/p/=/a/b/'),

--
nosy: +xiang.zhang

___
Python tracker 

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

[issue25225] Idle doc: redo Syntax Colors section


Terry J. Reedy added the comment:

Current:
3. Syntax colors 

The coloring is applied in a background “thread,” so you may occasionally see 
uncolorized text.  To change the color scheme, edit the [Colors] section in 
config.txt.  

Python syntax colors: 
 
  Keywords 
orange 

  Strings 
   green 

  Comments 
red 

  Definitions 
blue   

Shell colors: 
 
  Console output 
brown 

  stdout 
blue 

  stderr 
dark green 

  stdin 
black

--

___
Python tracker 

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

[issue25225] Idle doc: redo Syntax Colors section


Terry J. Reedy added the comment:

Possible alternative, with additions and corrections:

3. Syntax colors 

The coloring is applied in a background “thread,” so you may occasionally see 
uncolorized text.  To change the color scheme, edit the [Colors] section in 
config.txt.  

Python syntax colors: 
 
  Keywords: orange
  Builtins: purple
  Definitions: blue   
  Strings: green 
  Comments: red 

Shell colors: 
 
  Console output: brown
  Console error: black on red 
  stdin: black  
  stdout: blue 
  stderr: red

Other colors:
  Cursor: black
  Selected: black on gray
  Found: white on black

--

___
Python tracker 

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

[issue25225] Idle doc: redo Syntax Colors section


Terry J. Reedy added the comment:

The alternative above matches the format of help.txt, except that the latter 
has the colors lined up.  The excessive addition of whitespace here was an 
argument against replacing help.txt with help.html (#16893).  I consider the 
proposed condensation to be most of a fix of a regression.

This sentence, "To change the color scheme, edit the [Colors] section in 
config.txt.", is strange in that it for help.txt, it was changed in 2002-12-11 
to refer to the Highlights tab of the Configure dialog.  In any case, the color 
list was added before that tab, but not seems not necessary.  As a 'repeat', it 
is subject to obsolescence if not updated, which it has not been.  So I think 
we should either drop the section or drop the colors and replace with a better 
description of what is being replaced.

2.4. Text and Syntax colors 

Text is both editor and shell windows get color coded. The coloring is applied 
in the background, so you may occasionally see uncolor text.  To change the 
color scheme, use the Configure IDLE dialog, Highlighting tab.

Colors can be set for the follow types of text. 

Python syntax in both editor and shell: normal code, keywords, builtin class 
and function names, user-defined class and function names, strings, and 
comments.

Shell output: console output, console error text, user output, and user error 
output and tracebacks. 
 
Other text: cursor, selected text, and text found by search.  

Debugger breakpoint lines in the editor are indicated by a dark yellow 
background (not configurable).


Note: I believe the marking of found text is OS dependent and know that it is 
the subject of discussion in other issues, so this part needs elaboration.

--

___
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

2015-09-23 Thread Nick Coghlan


Nick Coghlan added the comment:

I think Larry's "split news" and "merge news" ideas are still useful as a 
bridging mechanism to help us get from the status quo to a tracker based 
solution.

It would just mean that, at some point in the future, the commit hook would 
change to be a post-commit hook that pushed to the issue tracker, rather than a 
pre-commit hook writing to a file in the source repo, and "merge news" would 
start pulling from the tracker, rather than from the source repo.

--

___
Python tracker 

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

[issue25194] Register of Financial Interests for core contributors

2015-09-23 Thread Nick Coghlan


Nick Coghlan added the comment:

Right, I'm in a similar situation at Red Hat to the one Antoine's in at 
Continuum Analytics - I'm not personally part of Red Hat's Python maintenance 
team (I used to work on internal Engineering tools, and now work on Fedora's 
overall developer experience), but I do sometimes spend work time helping our 
Python maintainers negotiate the upstream contribution and collaboration 
process. I also have quite a bit of leeway when it comes to getting sidetracked 
on upstream activities related to CPython, distutils-sig or the PSF.

Disclosing that affiliation aims to address a few things:

* it lets other community members know that Red Hat's interests are something 
I'm considering in community discussions - core development isn't a purely 
volunteer activity for me any more (and hasn't been for a number of years)
* it lets other Red Hatters know they have at least one colleague that may be 
able to help them out if they need particular CPython issues looked at more 
closely
* it (hopefully) helps nudge other commercial organisations towards the notion 
of either paying commercial redistributors or hiring current core developers to 
address their Python support needs, rather than expecting community volunteers 
to support their business activities for free
* inverting that last motivation, I'm hoping to help encourage commercial 
redistributors and other folks with a vested interest in the long term 
sustainability of CPython core development to engage professionally with 
current core contributors, and also allow their existing staff to spend work 
time on *becoming* core contributors

As far as more specific guidelines go, I'm thinking it may be worth including 
some notes on "Why might a core contributor want to publicly disclose their 
affiliations?" and "Why might a core contributor want to preserve their 
privacy?". I'm not sure exactly what that would look like yet, but I'll come up 
with something for the next draft.

For the final section on availability for consulting, training, and contract 
work, I think David makes a good point regarding folks potentially *wanting* to 
broadcast their availability, so I'll draft that such that "Contact via the 
PSF" is an option that core contributors can choose to take up. That way folks 
can choose between "available for direct contact" and "available for screened 
PSF referrals".

I'll aim to put that next draft together this coming Sunday.

--

___
Python tracker 

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

[issue22820] RESTART line with no output


Roundup Robot added the comment:

New changeset e7bf0727f7df by Terry Jan Reedy in branch '2.7':
Issue #22820: Explain need for *print* when running file from Idle editor.
https://hg.python.org/cpython/rev/e7bf0727f7df

New changeset 824cb25448ab by Terry Jan Reedy in branch '3.4':
Issue #22820: Explain need for *print* when running file from Idle editor.
https://hg.python.org/cpython/rev/824cb25448ab

--
nosy: +python-dev

___
Python tracker 

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

[issue22820] RESTART line with no output