[issue25057] Make parameter of io.base to be positional and keyword

2015-09-11 Thread shiyao.ma

shiyao.ma added the comment:

You've listed much of the benefits it can bring about.

The real problem is there are many places like iobase.seek to modify
to support keyword argument, and seems not many people think it's a
good idea to do that, per issue 8706. But I think the former is the
main hinder. If there is one commiter that is interested to merge in
the related code, I might consider taking my time and handling the
rest related similar functions, including the test and the doc.

--

___
Python tracker 

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



[issue25068] The proxy key's string should ignore case.

2015-09-11 Thread Chuang Cao

New submission from Chuang Cao:

When use a urllib2.ProxyHandler to set a proxy, if the proxies's key is an 
upper string, like "HTTP", "HTTPS". The proxy url can't be used, because they 
can't find the _open function.

Two way can sovle the issue.
1. Specify it in document to let users to use a lower string like "http".

2. Add a patch in urllib2.py:

diff -up ./urllib2.py.orig ./urllib2.py
--- ./urllib2.py.orig   2015-09-11 15:06:55.686927934 +0800
+++ ./urllib2.py2015-09-11 16:56:48.306138898 +0800
@@ -102,6 +102,7 @@ import sys
 import time
 import urlparse
 import bisect
+import string
 
 try:
 from cStringIO import StringIO
@@ -713,6 +714,7 @@ class ProxyHandler(BaseHandler):
 assert hasattr(proxies, 'has_key'), "proxies must be a mapping"
 self.proxies = proxies
 for type, url in proxies.items():
+type = string.lower(type)
 setattr(self, '%s_open' % type,
 lambda r, proxy=url, type=type, meth=self.proxy_open: \
 meth(r, proxy, type))


I think the second way is a good way.

--
components: Library (Lib)
messages: 250454
nosy: Chuang Cao
priority: normal
severity: normal
status: open
title: The proxy key's string should ignore case.
type: resource usage
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



[issue25068] The proxy key's string should ignore case.

2015-09-11 Thread Chris Angelico

Chris Angelico added the comment:

This sounds like a feature enhancement, which means it (almost certainly) won't 
be applied to Python 2.7. Does the same question come up in Python 3?

Also (FWIW) if you can confidently assume that all the keys are strings. then 
type.lower() is better than string.lower(type).

--
nosy: +Rosuav

___
Python tracker 

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



[issue24684] socket.getaddrinfo(host) doesn't ensure that host.encode() returns a byte string

2015-09-11 Thread Chris Angelico

Chris Angelico added the comment:

ISTM this is a case where Python's core shouldn't be using assert. It's 
possible for userland code to trigger an assertion failure, which means it 
should be a regular if(..) raise. Patch attached.

@haypo, what do you mean by "fuzzing"? Is there something I've missed here?

--
keywords: +patch
nosy: +Rosuav
Added file: http://bugs.python.org/file40434/dont_assert.patch

___
Python tracker 

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



[issue24684] socket.getaddrinfo(host) doesn't ensure that host.encode() returns a byte string

2015-09-11 Thread Chris Angelico

Chris Angelico added the comment:

Oops, forgot to add a test. Using a variant of poc_getaddr.py to construct 
something which fails on current CPython tip, and passes with the patch.

--
Added file: http://bugs.python.org/file40435/dont_assert_with_test.patch

___
Python tracker 

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



[issue25068] The proxy key's string should ignore case.

2015-09-11 Thread Martin Panter

Martin Panter added the comment:

Looking at the code, I think Python 3 is in the same boat. Most things in 
Python are case-sensitive, but I think it is reasonable to make an exception 
here, since the protocol schemes in general are insensitive. E.g. 
urlopen("HTTPS://bugs.python.org/issue25068") still uses "https" internally.

It would be good to include a test case and a note in the documentation if we 
added this though.

--
nosy: +martin.panter
stage:  -> needs patch
type: resource usage -> enhancement
versions: +Python 3.6 -Python 2.7

___
Python tracker 

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



[issue25068] The proxy key's string should ignore case.

2015-09-11 Thread Martin Panter

Martin Panter added the comment:

On the other hand, a documentation update saying it has to be lower case would 
be fine for Python 2.7 and 3.4+, if you wanted to go that way.

--

___
Python tracker 

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



[issue23484] SemLock acquire() keyword arg 'blocking' is invalid

2015-09-11 Thread Berker Peksag

Changes by Berker Peksag :


--
assignee: docs@python -> berker.peksag
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



[issue25038] test_os.TestSendfile.test_keywords() introduced a regression

2015-09-11 Thread Martin Panter

Changes by Martin Panter :


--
components: +Tests
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
type:  -> behavior

___
Python tracker 

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



[issue25069] Clean issue when generator not exhausted (garbage collector related?)

2015-09-11 Thread guilimo

New submission from guilimo:

Hello!


I experienced a strange behavior when using a generator, with some code 
encapsulated in a try/finally clause or a context manager.

If the generator is not exhausted when we leave the script (because normal end 
of script, uncatched exception, etc...), I expect an internal mechanism to 
execute properly the finally clause (or __exit__ if context manager).
However, in some specific cases, it seems that this mechanism does not work as 
expected.


Example
===

Consider the following code:

import time

def create_generator():
try:
yield
finally:
time.sleep(2)

ct = create_generator()
ct.next()


If you try to execute it, you will get a:
"Exception AttributeError: "'NoneType' object has no attribute 'sleep'" in 
 ignored"



Description
===

My understanding is the following (but I may be wrong):
At the end of the script, the garbage collector automatically calls the close() 
method of the generator. As a result, GeneratorExit is raised from the "yield", 
the finally clause is executed, but for some reason, time does not exist 
anymore (already collected by the GC?).
If you try just a print "xxx" instead of the time.sleep, it seems that there is 
not any problem.


Important note:
===

An other very strange thing:
It seems that if I use an other name than "ct" for the generator, the same 
exact code runs flawlessly...

You can find attached 3 examples (with try/finally, with a context manager, and 
with an other name for the generator).

I also found this ticket where some discussion may be related to my situation, 
even if not describing exactly my current problem:
https://bugs.python.org/issue25014

--
components: Interpreter Core
files: examples.zip
messages: 250460
nosy: guilimo
priority: normal
severity: normal
status: open
title: Clean issue when generator not exhausted (garbage collector related?)
type: crash
versions: Python 2.7
Added file: http://bugs.python.org/file40436/examples.zip

___
Python tracker 

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



[issue24684] socket.getaddrinfo(host) doesn't ensure that host.encode() returns a byte string

2015-09-11 Thread Roundup Robot

Roundup Robot added the comment:

New changeset 2bff115e6ba0 by Victor Stinner in branch '3.4':
Issue #24684: socket.socket.getaddrinfo() now calls
https://hg.python.org/cpython/rev/2bff115e6ba0

New changeset 0c13674cf8b5 by Victor Stinner in branch '2.7':
Issue #24684: socket.socket.getaddrinfo() now calls
https://hg.python.org/cpython/rev/0c13674cf8b5

--
nosy: +python-dev

___
Python tracker 

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



[issue24684] socket.getaddrinfo(host) doesn't ensure that host.encode() returns a byte string

2015-09-11 Thread STINNER Victor

STINNER Victor added the comment:

Ok, I fixed the bug in Python 2.7, 3.4, 3.5 and 3.6. (Python 2.7 was also 
impacted for custom *unicode* strings.)

Thanks for your bug report paul!

> ISTM this is a case where Python's core shouldn't be using assert. It's 
> possible for userland code to trigger an assertion failure, which means it 
> should be a regular if(..) raise.

Right, this check is implemented in PyUnicode_AsEncodedString(). Moreover, 
PyUnicode_AsEncodedString() calls directly the codec, it doesn't call the 
encode() method of the input string.

(Sorry, I wrote PyUnicode_AsEncodedObject() which has a different purpose.)

> @haypo, what do you mean by "fuzzing"?

This: https://en.wikipedia.org/wiki/Fuzz_testing

--
resolution:  -> fixed
status: open -> closed
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



[issue25066] Better repr for multiprocessing.synchronize objects

2015-09-11 Thread Berker Peksag

Changes by Berker Peksag :


--
nosy: +berker.peksag

___
Python tracker 

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



[issue25003] os.urandom() should call getrandom(2) not getentropy(2) on Solaris 11.3 and newer

2015-09-11 Thread STINNER Victor

STINNER Victor added the comment:

> But EINVAL should also be checked for to make sure the system call was 
> invoked with proper parameters.

py_getrandom() calls Py_FatalError() or raises an OSError on EINVAL. The error 
is not silently ignored.


> My builds of Python 3.5.0.X (don't recall whether X was a late Beta or 
> release candidate) were core dumping because Python was making that syscall 
> but not checking for EINVAL,

Py_FatalError() calls abort(). Usually, operating systems dump a core dump in 
this case. But it is the expected behaviour. Python now refuses to start if the 
OS random number generator doesn't work. There are similar checks on the system 
and monotonic clocks for example.

> ... and thus assuming the call was valid, when it was not.

Ah! Finally you explain the problem :-) I wrote py_getrandom() for Linux. I 
didn't expect other operating systems to implement the getrandom() syscall. I 
hardcoded the flags (0) for example.

py_getrandom() calls directly the syscall, because I like the new cool 
getrandom() syscall of Linux: it avoids the need of a private file descriptor. 
It would be much better to call a function of the C library, but the GNU C 
library didn't expose the function yet...

On Solaris, the function is available in C, no need to call directly the 
syscall. It would be better to call the C function, and check if it's available 
in configure.

Can you please try remove_get_entropy.patch + urandom_solaris.patch?

--
Added file: http://bugs.python.org/file40437/getrandom_solaris.patch

___
Python tracker 

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



[issue25069] Clean issue when generator not exhausted (garbage collector related?)

2015-09-11 Thread Martin Panter

Martin Panter added the comment:

You are basically right that it is garbage collection which causes your 
generator instance to be cleaned up, and in this instance it is happening after 
“time.sleep” has been set to None. It could also happen in the order, which 
would explain why changing names changes the behaviour you see.

Why the interpreter has to set module globals to None I’ve never quite 
understood. Maybe it is to guarantee that modules involved in garbage cycles 
with __del__() can still be partly cleaned up, otherwise such a cycle could 
easily keep lots of modules alive via globals.

This is not documented very obviously either. The best I can find at the moment 
is the warning under 
, which says 
“when __del__() is invoked in response to a module being deleted, [globals may 
be] in the process of being torn down”. The same applies to generator cleanup 
code. Looking through Python code you will often find workarounds such as 
prefixing globals with an underscore or caching references in non-global 
locations.

My recommended workaround though is to avoid relying on garbage collection as 
much as possible, and instead use a try / finally or “with” block. Then you 
know exactly when your generator will be cleaned up:

ct = create_generator()
try:
ct.next()
finally:
ct.close()

from contextlib import closing
with closing(create_generator()) as ct:
ct.next()

--
nosy: +martin.panter
type: crash -> behavior

___
Python tracker 

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



[issue24965] Implement PEP 498: Literal String Formatting

2015-09-11 Thread Martin Panter

Martin Panter added the comment:

Another version of that AST that is better for my digestion:

f'a={a}'

Module(body=[Expr(
value=JoinedStr(values=[
Str(s='a='),
FormattedValue(
value=Name(id='a', ctx=Load()),
conversion=0,
format_spec=None,
),
]),
)])

I have been reading over the test cases, and left a bunch of suggestions for 
more edge cases etc. Some of them might reflect that I haven’t completely 
learnt how the inner Python expression syntax, outer string escaping syntax, 
{{curly bracket}} escaping, automatic concatenation, etc, are all meant to fit 
together.

--
nosy: +martin.panter

___
Python tracker 

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



[issue25069] Clean issue when generator not exhausted (garbage collector related?)

2015-09-11 Thread R. David Murray

R. David Murray added the comment:

Yes, it is (was) to break otherwise unbreakable GC cycles involving __del__.  
Many improvements have been made to these algorithms in python3, such that 
__del__ methods no longer create unbreakable cycles, although I believe a few 
cases still remain.  Since some python interpreters do not do GC the way 
CPython does, it is always best to not depend on GC cleanup but instead to be 
explicit.

--
nosy: +r.david.murray
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

___
Python tracker 

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



[issue24965] Implement PEP 498: Literal String Formatting

2015-09-11 Thread Eric V. Smith

Eric V. Smith added the comment:

Thanks, Martin. I've posted my replies. I'll add some more tests, and work on 
the triple quoted string bug.

--

___
Python tracker 

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



[issue25070] Python 2.6 - Python 3.4 allows unparenthesized generator with *args, **kw, forbidden in 3.5

2015-09-11 Thread Antti Haapala

New submission from Antti Haapala:

User DeTeReR asked a question 
(http://stackoverflow.com/questions/32521140/generator-as-function-argument) on 
Stack Overflow about a special case of code that seemed to work in Python 3.4:

f(1 for x in [1], *[2])

and

f(*[2], 1 for x in [1])

I found out that when Python 2.6 introduced the "keyword arguments after 
*args", the checks in ast.c did not follow:

for (i = 0; i < NCH(n); i++) {
node *ch = CHILD(n, i);
if (TYPE(ch) == argument) {
if (NCH(ch) == 1)
nargs++;
else if (TYPE(CHILD(ch, 1)) == gen_for)
ngens++;
else
nkeywords++;
}
}
if (ngens > 1 || (ngens && (nargs || nkeywords))) {
ast_error(n, "Generator expression must be parenthesized "
  "if not sole argument");
return NULL;
}

the *args, **kwargs were not considered to be of type "argument" by the 
Grammar, and thus the error was not generated in this case.

Further down, the error "non-keyword arg after keyword arg" was not triggered 
in the case of sole unparenthesized generator expression.

Now, the parsing changes in 3.5 have disallowed all of these constructs:

f(1 for i in [42], **kw)
f(1 for i in [42], *args)
f(*args, 1 for i in [42])

which were (erroneously) allowed in previous versions.

I believe at least 3.5 release notes should mention this change.

--
components: Interpreter Core
messages: 250468
nosy: ztane
priority: normal
severity: normal
status: open
title: Python 2.6 - Python 3.4 allows unparenthesized generator with *args, 
**kw, forbidden in 3.5
type: behavior
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5

___
Python tracker 

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



[issue25070] Python 2.6 - Python 3.4 allows unparenthesized generator with *args, **kw, forbidden in 3.5

2015-09-11 Thread STINNER Victor

STINNER Victor added the comment:

I guess that it's a consequence of the PEP 448 "additional unpacking 
generalizations".

--
nosy: +haypo, yselivanov

___
Python tracker 

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



[issue25070] Python 2.6 - Python 3.4 allows unparenthesized generator with *args, **kw, forbidden in 3.5

2015-09-11 Thread Antti Haapala

Antti Haapala added the comment:

@haypo yes.

I must add that I found out that Python 2.5 also allows 

f(1 for x in [1], *a)

and 

f(1 for x in [1], **kw)

but not

f(*a, 1 for x in [1])

So I do not know if the first and second cases were intentional or not.
Also, in Python 2.6 - 3.4, f(*a, 1 for x in [1]) provides the generator as the 
*first* positional argument, in 3.5 it'd be the last one.

--

___
Python tracker 

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



[issue25070] Python 2.6 - Python 3.4 allows unparenthesized generator with *args, **kw, forbidden in 3.5

2015-09-11 Thread Stefan Krah

Stefan Krah added the comment:

According to the human readable grammar in the docs

   https://docs.python.org/3/reference/expressions.html#calls

I'd say this was a bug that is now fixed in 3.5. The call should
either take a single unparenthesized generator expression or an
argument_list (which may contain parenthesized generator expressions).

--
nosy: +skrah

___
Python tracker 

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



[issue25070] Python 2.6 - Python 3.4 allows unparenthesized generator with *args, **kw, forbidden in 3.5

2015-09-11 Thread Antti Haapala

Antti Haapala added the comment:

Yeah, it is a bug in 2.5 too; https://docs.python.org/2.5/ref/calls.html

call ::= primary "(" [argument_list [","]
 | expression genexpr_for] ")"

--
assignee:  -> docs@python
components: +Documentation
nosy: +docs@python

___
Python tracker 

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



[issue25043] document socket constants for Bluetooth

2015-09-11 Thread Tim Tisdall

Tim Tisdall added the comment:

Okay, since there's currently no existing tests for the Bluetooth components of 
socket and the only example for BDADDR_ALL seems to be for something I'm not 
sure you can do in socket, I'm just going to not bother including it.

I've attached a 3.6 patch without BDADDR_ALL.

--
Added file: http://bugs.python.org/file40438/bdaddr_36_2.patch

___
Python tracker 

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



[issue24927] multiprocessing.Pool hangs forever on segfault

2015-09-11 Thread Brian Boonstra

Brian Boonstra added the comment:

See also issue 22393

--
nosy: +brianboonstra

___
Python tracker 

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



[issue24899] Add an os.path <=> pathlib equivalence table in pathlib docs

2015-09-11 Thread Nikita Klimov

Changes by Nikita Klimov :


--
nosy: +klimov

___
Python tracker 

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



[issue25043] document socket constants for Bluetooth

2015-09-11 Thread Tim Tisdall

Tim Tisdall added the comment:

okay, I talked to one of the Bluez developers and he recommended leaving out 
BDADDR_ALL since it doesn't seem to correspond to anything in the kernel.

--

___
Python tracker 

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



[issue25071] Windows installer requires TargetDir parameter when installing quietly

2015-09-11 Thread Steve Dower

New submission from Steve Dower:

If you run the installer without UI and without specifying an installation 
path, it will not install. For example:

C:\> python-3.5.0rc4-amd64-webinstall.exe /passive

The workaround is to specify TargetPath:

C:\> python-3.5.0rc4-amd64-webinstall.exe /passive TargetPath="C:\Python35_x64"

However, this workaround should not be necessary. We should use the default 
path based on the InstallAllUsers setting (false by default).

--
assignee: steve.dower
components: Installation, Windows
messages: 250476
nosy: paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
stage: needs patch
status: open
title: Windows installer requires TargetDir parameter when installing quietly
type: behavior
versions: Python 3.5, Python 3.6

___
Python tracker 

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



[issue25071] Windows installer requires TargetDir parameter when installing quietly

2015-09-11 Thread Steve Dower

Steve Dower added the comment:

Adding Larry, as this either needs a fix or a prominent release note for 3.5.0 
(or we document the bug in the docs).

I *think* the fix will be fairly simple and constrained entire to one file. 
Should have something ready later today.

--
nosy: +larry

___
Python tracker 

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



[issue25071] Windows installer requires TargetDir parameter when installing quietly

2015-09-11 Thread Steve Dower

Changes by Steve Dower :


--
nosy: +takluyver

___
Python tracker 

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



[issue25003] os.urandom() should call getrandom(2) not getentropy(2) on Solaris 11.3 and newer

2015-09-11 Thread John Beck

John Beck added the comment:

Yes, those patches work, with a caveat.  While testing this, I found out why I 
had needed EINVAL earlier (and still do, for now): there is a bug in the 
Solaris implementation of getrandom(2).  If flags are 0 and the buffer size > 
1024, then it fails with EINVAL.  That is only supposed to happen for a buffer 
that big if GNRD_RANDOM is set in flags but GNRD_NONBLOCK is not set.  So until 
that bug is fixed, I have to patch py_getrandom() to treat EINVAL like ENOSYS 
and fall back to using /dev/urandom as if getrandom(2) were not supported.

--

___
Python tracker 

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



[issue25072] CGI large POST data string truncated

2015-09-11 Thread Vincent Caloone

New submission from Vincent Caloone:

For "large" POST request (> 25 ko), cgi.FieldStorage() doesn't contains all 
field in the html form. When we trace the root of the issue, it is located in 
file server.py : 

if self.command.lower() == "post" and nbytes > 0:
data = self.rfile.read(nbytes)

the size of 'rfile' is less than the number of byte we attemp to read 'nbyte' 
with is corresponding to the Content-Length of the POST request header.

Issue seems to be linked with buffering since changing rbufsize from 0 to -1 : 

# Make rfile unbuffered -- we need to read one line and then pass
# the rest to a subprocess, so we can't use buffered input.
#rbufsize = 0
rbufsize = -1 

stop the issue. Any idea of the real root of this issue ?

Many thanks.

--
messages: 250479
nosy: Vincent Caloone
priority: normal
severity: normal
status: open
title: CGI large POST data string truncated
type: behavior
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



[issue25071] Windows installer requires TargetDir parameter when installing quietly

2015-09-11 Thread Steve Dower

Steve Dower added the comment:

Patch attached.

PR for 3.5.0 at: 
https://bitbucket.org/larry/cpython350/pull-requests/25/issue-25071-windows-installer-should-not/diff

--
keywords: +patch
stage: needs patch -> patch review
Added file: http://bugs.python.org/file40439/25071_1.patch

___
Python tracker 

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



[issue24903] Do not verify destdir argument to compileall

2015-09-11 Thread Jake Garver

Jake Garver added the comment:

Updated patch.  Same as before, but updates tests.

Sorry I went MIA on this issue.

--
Added file: http://bugs.python.org/file40440/python34_compileall_ddir_2.diff

___
Python tracker 

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



[issue25073] Document asyncio.test_utils

2015-09-11 Thread Zachary Ware

New submission from Zachary Ware:

asyncio.test_utils is not documented.  I'm unsure as to whether that's because 
it's meant to be private, or if it just hasn't been done yet.

--
assignee: docs@python
components: Documentation, asyncio
messages: 250482
nosy: docs@python, gvanrossum, haypo, yselivanov, zach.ware
priority: normal
severity: normal
stage: needs patch
status: open
title: Document asyncio.test_utils
type: enhancement
versions: Python 3.4, Python 3.5, Python 3.6

___
Python tracker 

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



[issue25073] Document asyncio.test_utils

2015-09-11 Thread Yury Selivanov

Yury Selivanov added the comment:

It's meant to be private.

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

___
Python tracker 

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



[issue25073] Document asyncio.test_utils

2015-09-11 Thread Guido van Rossum

Guido van Rossum added the comment:

Agreed, but then why isn't it in the tests directory? There are some examples 
in the asyncio repo on GitHub that use test_utils.dummy_ssl_context(), and 
that's probably why; but that's a fairly bad practice plus it's really a 
one-liner.

--

___
Python tracker 

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



[issue24965] Implement PEP 498: Literal String Formatting

2015-09-11 Thread Eric V. Smith

Eric V. Smith added the comment:

Thanks again, Martin. I've found 4 bugs so far, based on your suggested tests. 
The ones I haven't fixed are: 'fur' strings don't work (something in the 
lexer), and triple quoted strings don't work correctly. I'm working on both of 
those, and should have an updated patch in the next day or so.

--

___
Python tracker 

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



[issue25071] Windows installer requires TargetDir parameter when installing quietly

2015-09-11 Thread Larry Hastings

Larry Hastings added the comment:

Pull request approved.  Hopefully the last one for 3.5.0!  Please forward-merge.

--

___
Python tracker 

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



[issue25071] Windows installer requires TargetDir parameter when installing quietly

2015-09-11 Thread Roundup Robot

Roundup Robot added the comment:

New changeset da8f2767b6cc by Steve Dower in branch '3.5':
Issue #25071: Windows installer should not require TargetDir parameter when 
installing quietly
https://hg.python.org/cpython/rev/da8f2767b6cc

New changeset bb7363b8b50e by Steve Dower in branch 'default':
Issue #25071: Windows installer should not require TargetDir parameter when 
installing quietly
https://hg.python.org/cpython/rev/bb7363b8b50e

--
nosy: +python-dev

___
Python tracker 

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



[issue25071] Windows installer requires TargetDir parameter when installing quietly

2015-09-11 Thread Steve Dower

Steve Dower added the comment:

I hope so too :)

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



[issue24915] Profile Guided Optimization improvements (better training, llvm support, etc)

2015-09-11 Thread Brett Cannon

Brett Cannon added the comment:

Attached is what I plan to commit to Python 2.7 assuming everyone is happy with 
the outcome. I tweaked the echoed messages from Alecsandru's patch, pulled in 
the README changes, and dropped the x86 checks as Antoine and Stefan requested.

Assuming people are happy with the patch I will also apply it to Python 3.5 
with the appropriate tweaks.

--
Added file: http://bugs.python.org/file40441/issue24915-python2.7.diff

___
Python tracker 

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



[issue25074] Bind logger and waninigs modules for asyncio __del__ methods

2015-09-11 Thread Andrew Svetlov

New submission from Andrew Svetlov:

See https://github.com/KeepSafe/aiohttp/issues/497 for the reason.

Desctructors and descendant code (`loop.call_exception_handler()`) can be 
called on interpreter shutdown stage, which leads to printouts like 'None 
object has no attribute "errror"'.

--
assignee: asvetlov
components: asyncio
files: asyncio_bind_modules.patch
keywords: patch
messages: 250490
nosy: asvetlov, gvanrossum, haypo, yselivanov
priority: normal
severity: normal
stage: patch review
status: open
title: Bind logger and waninigs modules for asyncio __del__ methods
type: enhancement
versions: Python 3.5, Python 3.6
Added file: http://bugs.python.org/file40442/asyncio_bind_modules.patch

___
Python tracker 

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



[issue20629] Python ctypes BigEndianStructure bitfield assignment misbehavior in Linux

2015-09-11 Thread Brian Trotter

Brian Trotter added the comment:

I am experiencing the same bug with c_uint32 bitfields inside 
BigEndianStructure in Python 3.4.0 on Ubuntu 14.04.3 x64. No problem in Windows 
7 x64. As shown in the example below, the fourth byte is the only one that is 
written correctly. This is a rather significant error.


Source:

import ctypes

class BitFieldsBE(ctypes.BigEndianStructure):
_pack_ = 1
_fields_ = [
('a', ctypes.c_uint32, 8),
('b', ctypes.c_uint32, 8),
('c', ctypes.c_uint32, 8),
('d', ctypes.c_uint32, 8)]

class BitFieldsLE(ctypes.LittleEndianStructure):
_pack_ = 1
_fields_ = [
('a', ctypes.c_uint32, 8),
('b', ctypes.c_uint32, 8),
('c', ctypes.c_uint32, 8),
('d', ctypes.c_uint32, 8)]

be = BitFieldsBE()
le = BitFieldsLE()

def prints(arg):
print(arg)
print('be',bytes(be))
print('le',bytes(le))

prints('')
be.a = 0xba; be.b = 0xbe; be.c = 0xfa; be.d = 0xce
le.a = 0xba; le.b = 0xbe; le.c = 0xfa; le.d = 0xce
prints('babeface')
be.a = 0xde; be.b = 0xad; be.c = 0xbe; be.d = 0xef
le.a = 0xde; le.b = 0xad; le.c = 0xbe; le.d = 0xef
prints('deadbeef')


Output:


be b'\x00\x00\x00\x00'
le b'\x00\x00\x00\x00'
babeface
be b'\x00\xfa\x00\xce'
le b'\xba\xbe\xfa\xce'
deadbeef
be b'\x00\xbe\x00\xef'
le b'\xde\xad\xbe\xef'

--
nosy: +Brian Trotter
type:  -> behavior
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



[issue25073] Document asyncio.test_utils

2015-09-11 Thread Yury Selivanov

Yury Selivanov added the comment:

> Agreed, but then why isn't it in the tests directory?

I think that the main reason is to make it possible for tests to import some 
common functionality from 'asyncio' package, when you run them from the cloned 
github asyncio repo.

In fact, I think we should prefix the module with an underscore.

--

___
Python tracker 

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



[issue24965] Implement PEP 498: Literal String Formatting

2015-09-11 Thread Eric V. Smith

Eric V. Smith added the comment:

It turns out 'fur' strings aren't a thing, because 'ur' strings aren't.

>From tokenizer.c:
/* ur"" and ru"" are not supported */

And the PEP:
https://www.python.org/dev/peps/pep-0414/#exclusion-of-raw-unicode-literals

I'll add a test to make sure this fails.

So I just need to work on the triple-quoted string problem.

--

___
Python tracker 

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



[issue25073] Document asyncio.test_utils

2015-09-11 Thread Guido van Rossum

Guido van Rossum added the comment:

The _ is a good idea. Please do fix up the examples!

--

___
Python tracker 

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



[issue23447] Import fails when doing a circular import involving an `import *`

2015-09-11 Thread Brett Cannon

Brett Cannon added the comment:

Here is Steven's patch touched up. I still have not decided if the semantic 
change is worth it. If anyone else has an opinion please feel free to speak up. 
All tests do pass, though, so it at least doesn't seem to directly break 
anything.

--
Added file: http://bugs.python.org/file40443/issue23447.diff

___
Python tracker 

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



[issue25003] os.urandom() should call getrandom(2) not getentropy(2) on Solaris 11.3 and newer

2015-09-11 Thread STINNER Victor

STINNER Victor added the comment:

>  While testing this, I found out why I had needed EINVAL earlier (and still 
> do, for now): there is a bug in the Solaris implementation of getrandom(2).  
> If flags are 0 and the buffer size > 1024, then it fails with EINVAL.  That 
> is only supposed to happen for a buffer that big if GNRD_RANDOM is set in 
> flags but GNRD_NONBLOCK is not set.  So until that bug is fixed, ...

Ah! So it was useful to dig the EINVAL issue, it's a bug in the kernel :-)

You wrote that the final version of Solaris 11.3 and 12 was not released yet. 
Can we expect a fix in the kernel before the final version?

--

___
Python tracker 

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



[issue25003] os.urandom() should call getrandom(2) not getentropy(2) on Solaris 11.3 and newer

2015-09-11 Thread John Beck

John Beck added the comment:

I have queried the engineer who owns the kernel bug and will post an update 
once I hear back from him.  But as it is already almost midnight on Friday in 
his geo, it may well be Monday before I hear back.

--

___
Python tracker 

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



[issue25043] document socket constants for Bluetooth

2015-09-11 Thread Martin Panter

Martin Panter added the comment:

Thanks for your work on this. I think the patch is good, although I might add 
:const:`BDADDR_ANY` etc markup around the references within the text.

By the way, you don’t normally need to make separate patches for each branch. 
When I commit this I will just apply the 3.4 version, and then automatically 
merging to the other branches should be trivial.

--
assignee: docs@python -> martin.panter
nosy: +berker.peksag
stage:  -> commit review

___
Python tracker 

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



[issue25072] CGI large POST data string truncated

2015-09-11 Thread R. David Murray

R. David Murray added the comment:

Any chance you could provide code that demonstrates this bug?

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



[issue25070] Python 2.6 - Python 3.4 allows unparenthesized generator with *args, **kw, forbidden in 3.5

2015-09-11 Thread R. David Murray

R. David Murray added the comment:

If we have decided that this is a "fixed bug", it should indeed be mentioned in 
what's new for 3.5 since it is a behavior change.

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



[issue25043] document socket constants for Bluetooth

2015-09-11 Thread Roundup Robot

Roundup Robot added the comment:

New changeset 152568976062 by Martin Panter  in branch '3.4':
Issue #25043: Document BDADDR_ and HCI_ Bluetooth socket constants
https://hg.python.org/cpython/rev/152568976062

New changeset 3f475417eadd by Martin Panter  in branch '3.5':
Issue #25043: Merge Bluetooth doc from 3.4 into 3.5
https://hg.python.org/cpython/rev/3f475417eadd

New changeset 5325233f117d by Martin Panter  in branch 'default':
Issue #25043: Merge Bluetooth doc from 3.5
https://hg.python.org/cpython/rev/5325233f117d

--
nosy: +python-dev

___
Python tracker 

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



[issue25043] document socket constants for Bluetooth

2015-09-11 Thread Martin Panter

Changes by Martin Panter :


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

___
Python tracker 

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



[issue25075] issue from python in encode base64 with Json Model

2015-09-11 Thread Ramin Farajpour Cami

New submission from Ramin Farajpour Cami:

Hi,

issue from python in encode base64 with Json Model in twice encode with base64 
output python different  with JAVA and C# , if programmer using rest-service in 
server side and other programmer using UI(Python Django) in client site , this 
encode different for encode and decode with match json encode model,


real example :

1- go to https://www.base64encode.org/ 
2- using {"userName":"admin","password":"admin"} (default UTF-8)
3-first encode oupput : "eyJ1c2VyTmFtZSI6ImFkbWluIiwicGFzc3dvcmQiOiJhZG1pbiJ9"
4-again second encode "eyJ1c2VyTmFtZSI6ImFkbWluIiwicGFzc3dvcmQiOiJhZG1pbiJ9" 
output :
"ZXlKMWMyVnlUbUZ0WlNJNkltRmtiV2x1SWl3aWNHRnpjM2R2Y21RaU9pSmhaRzFwYmlKOQ=="

now second output python json model : 

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\Matthew F4rr3ll>python
Python 2.7.7 (default, Jun  1 2014, 14:21:57) [MSC v.1500 64 bit (AMD64)] on win
32
Type "help", "copyright", "credits" or "license" for more information.
>>> import json
>>> s1='{"userName":"admin","password":"admin"}'
>>> s2 = s1.encode("base64")
>>> e = s2.encode("base64")
>>> print e
ZXlKMWMyVnlUbUZ0WlNJNkltRmtiV2x1SWl3aWNHRnpjM2R2Y21RaU9pSmhaRzFwYmlKOQo=

>>>
>>>
>>>

now check this output : 
ZXlKMWMyVnlUbUZ0WlNJNkltRmtiV2x1SWl3aWNHRnpjM2R2Y21RaU9pSmhaRzFwYmlKOQo=
ZXlKMWMyVnlUbUZ0WlNJNkltRmtiV2x1SWl3aWNHRnpjM2R2Y21RaU9pSmhaRzFwYmlKOQ==

you see in two encode different in end line in ("o=" != "==")


also i know resolve this but you should fix in end line encode match with other 
language


Thanks,
Ramin

--
components: 2to3 (2.x to 3.x conversion tool)
messages: 250502
nosy: Ramin Farajpour Cami
priority: normal
severity: normal
status: open
title: issue from python in encode base64 with Json Model
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



[issue25063] shutil.copyfileobj should internally use os.sendfile when possible

2015-09-11 Thread Roundup Robot

Roundup Robot added the comment:

New changeset 3d9cbbad8a04 by Martin Panter  in branch '3.4':
Issue #25063: socket.sendfile() does not exist in 3.4
https://hg.python.org/cpython/rev/3d9cbbad8a04

--
nosy: +python-dev

___
Python tracker 

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



[issue25075] issue from python in encode base64 with Json Model

2015-09-11 Thread Martin Panter

Martin Panter added the comment:

This seems to be as documented. Have a look at the definition of “base64_codec” 
under 
, 
which says “the result always includes a trailing '\n' ”. In fact, line breaks 
are also added for longer encodings so that each line is ≤ 76 symbols.

>>> e.decode("base64")
'eyJ1c2VyTmFtZSI6ImFkbWluIiwicGFzc3dvcmQiOiJhZG1pbiJ9\n'

Your alternative encoding does not include that trailing newline. If you don’t 
want the “MIME Base-64” multiline encoding maybe you should use something like 
base64.b64encode() directly.

See also Issue 16473 where I proposed a patch to fix the Python 3 documentation 
that links to the wrong equivalent function.

--
nosy: +martin.panter
resolution:  -> not a bug
status: open -> closed

___
Python tracker 

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



[issue25075] issue from python in encode base64 with Json Model

2015-09-11 Thread Martin Panter

Changes by Martin Panter :


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



[issue25075] issue from python in encode base64 with Json Model

2015-09-11 Thread Ramin Farajpour Cami

Ramin Farajpour Cami added the comment:

why any update in python 2.7?

you should using a function this code change :

enc_sec = 
ZXlKMWMyVnlUbUZ0WlNJNkltRmtiV2x1SWl3aWNHRnpjM2R2Y21RaU9pSmhaRzFwYmlKOQo=
url = re.sub('\o=$','',enc_sec)
result = url.replace('\n','==')
print result

--
status: closed -> open

___
Python tracker 

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



[issue25075] issue from python in encode base64 with Json Model

2015-09-11 Thread R. David Murray

Changes by R. David Murray :


--
status: open -> closed

___
Python tracker 

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



[issue16473] quopri module differences in quoted-printable text with whitespace

2015-09-11 Thread Martin Panter

Martin Panter added the comment:

Will commit a slightly modified version of my doc patch to 3.4+, since 
mentioning the wrong functions is confusing. But I think we still need to fix 
the “binascii” decoding, and have a look at Alejandro’s test suite patch.

--
nosy: +berker.peksag
stage:  -> needs patch
type:  -> behavior
versions: +Python 2.7, Python 3.4, Python 3.5, Python 3.6 -Python 3.3

___
Python tracker 

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



[issue25075] issue from python in encode base64 with Json Model

2015-09-11 Thread Ramin Farajpour Cami

Ramin Farajpour Cami added the comment:

no close plz,

i using python 2.7.3 i get this output without "\n"?


code:
   json_obj='{"userName": "admin", "password": "admin"}'
   enc = json_obj.encode("base64")
   print enc
   enc_sec = re.sub('\n$','',enc)
   print enc_sec
   sec = enc_sec.encode("base64")
   print sec

Output:
{"userName": "admin", "password": "admin"}

eyJ1c2VyTmFtZSI6ICJhZG1pbiIsICJwYXNzd29yZCI6ICJhZG1pbiJ9

ZXlKMWMyVnlUbUZ0WlNJNklDSmhaRzFwYmlJc0lDSndZWE56ZDI5eVpDSTZJQ0poWkcxcGJpSjk=

--

___
Python tracker 

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



[issue16473] quopri module differences in quoted-printable text with whitespace

2015-09-11 Thread Roundup Robot

Roundup Robot added the comment:

New changeset de82f41d6669 by Martin Panter  in branch '3.4':
Issue #16473: Fix byte transform codec documentation; test quotetabs=True
https://hg.python.org/cpython/rev/de82f41d6669

New changeset 28cd11dc2915 by Martin Panter  in branch '3.5':
Issue #16473: Merge codecs doc and test from 3.4 into 3.5
https://hg.python.org/cpython/rev/28cd11dc2915

New changeset 3ecb5766ba15 by Martin Panter  in branch 'default':
Issue #16473: Merge codecs doc and test from 3.5
https://hg.python.org/cpython/rev/3ecb5766ba15

--
nosy: +python-dev

___
Python tracker 

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



[issue16473] quopri module differences in quoted-printable text with whitespace

2015-09-11 Thread Roundup Robot

Roundup Robot added the comment:

New changeset cfb0481c89d7 by Martin Panter  in branch '2.7':
Issue #16473: Fix byte transform codec documentation; test quotetabs=True
https://hg.python.org/cpython/rev/cfb0481c89d7

--

___
Python tracker 

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



[issue25008] Deprecate smtpd

2015-09-11 Thread Terry J. Reedy

Terry J. Reedy added the comment:

http://nullege.com/codes/search?cq=import+smtpd
shows 135 hits.  FWIW, import+asyncore get 972.

--
nosy: +terry.reedy

___
Python tracker 

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



[issue25070] Python 2.6 - Python 3.4 allows unparenthesized generator with *args, **kw, forbidden in 3.5

2015-09-11 Thread Terry J. Reedy

Changes by Terry J. Reedy :


--
versions:  -Python 3.2, Python 3.3

___
Python tracker 

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



[issue25070] Python 2.6 - Python 3.4 allows unparenthesized generator with *args, **kw, forbidden in 3.5

2015-09-11 Thread Yury Selivanov

Yury Selivanov added the comment:

> If we have decided that this is a "fixed bug", [..]

I'd call this a bug fix.  The old syntax was completely unreadable.  

Should I close this issue?

> [..] it should indeed be mentioned in what's new for 3.5 since it is a 
> behavior change.

Sure, I'll document it.

--

___
Python tracker 

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



[issue25076] Wrong parameter name in distutils documentation

2015-09-11 Thread TAKASE Arihiro

New submission from TAKASE Arihiro:

In Doc/distutils/apiref.rst, the palameter name of CCompiler.library_option is 
*lib*, but written *dir* in the documentation.

This also applies to the docstring of CCompiler.library_option().

The attached patch fixes it.

--
assignee: docs@python
components: Documentation
files: library_option.patch
keywords: patch
messages: 250512
nosy: artakase, docs@python
priority: normal
severity: normal
status: open
title: Wrong parameter name in distutils documentation
type: behavior
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6
Added file: http://bugs.python.org/file40444/library_option.patch

___
Python tracker 

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



[issue10614] ZipFile: add a filename_encoding argument

2015-09-11 Thread irdb

Changes by irdb :


--
nosy: +irdb

___
Python tracker 

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



[issue10972] zipfile: add "unicode" option to the force the filename encoding to UTF-8

2015-09-11 Thread irdb

Changes by irdb :


--
nosy: +irdb

___
Python tracker 

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