date:20151127


Changes by Terry J. Reedy :


--
assignee:  -> terry.reedy
stage:  -> needs patch
versions: +Python 3.4, Python 3.5, Python 3.6

___
Python tracker 

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

[issue25741] Usual Installation Directory

2015-11-27 Thread Brett Cannon


Changes by Brett Cannon :


--
nosy: +steve.dower

___
Python tracker 

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

[issue25719] Deprecate spitfire benchmark

2015-11-27 Thread Roundup Robot


Roundup Robot added the comment:

New changeset 75751d838789 by Zachary Ware in branch 'default':
Issue #25719: Deprecate spitfire benchmark.
https://hg.python.org/benchmarks/rev/75751d838789

--
nosy: +python-dev

___
Python tracker 

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

[issue25719] Deprecate spitfire benchmark

2015-11-27 Thread Zachary Ware


Zachary Ware added the comment:

Done.  Thanks, Florin!

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

[issue24053] Define EXIT_SUCCESS and EXIT_FAILURE constants in sys

2015-11-27 Thread Robert Collins


Robert Collins added the comment:

@Serhiy, EXIT_FAILURE is used in Python's C code itself (just once admittedly, 
and then we use 0 sometimes for success and sometimes for errors, and then 1 
for errors... aiee.)

FWIW to the extent that folk want to write posix code in Python, I'm all for 
helping them, I find the amount of help this will be to be hard to assess. 
There is some code to adding the constants in documentation and learning 
surface area.

Right now we don't document all the ways Python can interact with exit codes, 
and I suspect thats actually a bigger burden than writing the code to generate 
any given code.

--
nosy: +rbcollins

___
Python tracker 

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

[issue25749] asyncio.Server class documented but not exported

2015-11-27 Thread Ron Frederick


New submission from Ron Frederick:

The asyncio documentation defines the class 'asyncio.Server' in section 
18.5.1.15. However, this class is not exported by asyncio. It is defined in 
base_events.py but not in the __all__ list. The only class exported at the 
asyncio top level is asyncio.AbstractServer, defined in events.py.

I think the documentation should match the exports. Either Server should be 
exported out of base_events.py, or the documentation should only refer to 
asyncio.AbstractServer.

--
components: asyncio
messages: 255476
nosy: Ron Frederick, gvanrossum, haypo, yselivanov
priority: normal
severity: normal
status: open
title: asyncio.Server class documented but not exported
type: behavior
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

[issue25744] Reference leaks in test_collections


New submission from Serhiy Storchaka:

$ ./python -m test.regrtest -uall -R 3:3 test_collections
[1/1] test_collections
beginning 6 repetitions
123456
..
test_collections leaked [-2, 0, 0] references, sum=-2
test_collections leaked [-1, 2, 1] memory blocks, sum=2
1 test failed:
test_collections

--
components: Extension Modules, Tests
messages: 255469
nosy: rhettinger, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Reference leaks in test_collections
type: resource usage
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

[issue25745] Reference leaks in test_curses


New submission from Serhiy Storchaka:

$ ./python -m test.regrtest -uall -R 3:3 test_curses
[1/1] test_curses
beginning 6 repetitions
123456
.
test_curses leaked [2, 2, 2] references, sum=6
test_curses leaked [0, 1, 2] memory blocks, sum=3
1 test failed:
test_curses

--
components: Extension Modules, Tests
messages: 255470
nosy: serhiy.storchaka, twouters
priority: normal
severity: normal
status: open
title: Reference leaks in test_curses
type: resource usage
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

[issue25743] Clarify exactly what \w matches in UNICODE mode

2015-11-27 Thread Zack Weinberg


New submission from Zack Weinberg:

The `re` module documentation does not do a good job of explaining exactly what 
`\w` matches.  Quoting https://docs.python.org/3.5/library/re.html :

> \w
> For Unicode (str) patterns:
> Matches Unicode word characters; this includes most characters
> that can be part of a word in any language, as well as numbers
> and the underscore.

Empirically, this appears to mean "everything in Unicode general categories L* 
and N*, plus U+005F (underscore)".  That is a perfectly sensible definition and 
the documentation should state it in those terms.  "Unicode word characters" 
could mean any number of different things; note for instance that UTS#18 gives 
a very different definition.

(Further reading: https://gist.github.com/zackw/3077f387591376c7bf67 plus links 
therefrom).

--
assignee: docs@python
components: Documentation
messages: 255463
nosy: docs@python, zwol
priority: normal
severity: normal
status: open
title: Clarify exactly what \w matches in UNICODE mode
versions: Python 2.7, Python 3.2, Python 3.3, 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

Re: [issue25625] "chdir" Contex manager for pathlib

2015-11-27 Thread Stephane Wirtel

What's the relation with subprocess ?

-- 
Stéphane Wirtel - http://wirtel.be - @matrixise
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25747] test_idle failure in leaks searching mode


New submission from Serhiy Storchaka:

$ ./python -m test.regrtest -uall -R 3:3 test_idle
[1/1] test_idle
beginning 6 repetitions
123456
test test_idle failed -- Traceback (most recent call last):
  File "/home/serhiy/py/cpython-debug/Lib/idlelib/idle_test/test_warning.py", 
line 76, in test_idlever
self.assertEqual(len(w), 1)
AssertionError: 0 != 1

1 test failed:
test_idle

--
components: IDLE, Tests
messages: 255472
nosy: kbk, roger.serwy, serhiy.storchaka, terry.reedy
priority: normal
severity: normal
status: open
title: test_idle failure in leaks searching mode
type: behavior
versions: Python 3.6

___
Python tracker 

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

[issue25743] Clarify exactly what \w matches in UNICODE mode

2015-11-27 Thread Andi McClure


Andi McClure added the comment:

I would like to request also a clear explanation be given for the documentation 
in the 2.7 branch. From https://docs.python.org/2.7/library/re.html :

"\w ... If UNICODE is set, this will match the characters [0-9_] plus whatever 
is classified as alphanumeric in the Unicode character properties database"

This is ambiguous. Does it mean the "Alphabetic" property from UAX#44? Does it 
mean something else?

--
nosy: +Andi McClure

___
Python tracker 

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

[issue25746] test_unittest failure in leaks searching mode


New submission from Serhiy Storchaka:

$ ./python -m test.regrtest -uall -R 3:3 test_unittest
[1/1] test_unittest
test test_unittest failed -- multiple errors occurred; run in verbose mode for 
details
1 test failed:
test_unittest

$ ./python -m test.regrtest -vvuall -R 3:3 test_unittest
...
==
ERROR: test_discover_with_init_module_that_raises_SkipTest_on_import 
(unittest.test.test_discovery.TestDiscovery)
--
Traceback (most recent call last):
  File "/home/serhiy/py/cpython-debug/Lib/unittest/test/test_discovery.py", 
line 532, in test_discover_with_init_module_that_raises_SkipTest_on_import
pickle.loads(pickle.dumps(suite, proto))
_pickle.PicklingError: Can't pickle : 
attribute lookup ModuleSkipped on unittest.loader failed

==
ERROR: test_discover_with_module_that_raises_SkipTest_on_import 
(unittest.test.test_discovery.TestDiscovery)
--
Traceback (most recent call last):
  File "/home/serhiy/py/cpython-debug/Lib/unittest/test/test_discovery.py", 
line 508, in test_discover_with_module_that_raises_SkipTest_on_import
pickle.loads(pickle.dumps(suite, proto))
_pickle.PicklingError: Can't pickle : 
attribute lookup ModuleSkipped on unittest.loader failed

--

--
components: Tests
messages: 255471
nosy: ezio.melotti, michael.foord, rbcollins, serhiy.storchaka
priority: normal
severity: normal
status: open
title: test_unittest failure in leaks searching mode
type: behavior
versions: Python 3.6

___
Python tracker 

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

[issue25687] Error during test case and tearDown


Changes by Terry J. Reedy :


--
nosy: +ezio.melotti, michael.foord, rbcollins
versions: +Python 3.5, Python 3.6 -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

[issue25748] Resource warnings when run test_asyncio in leaks searching mode


New submission from Serhiy Storchaka:

$ ./python -m test.regrtest -uall -R 3:3 test_asyncio
[1/1] test_asyncio
...
.Executing .start() done, defined at 
/home/serhiy/py/cpython-debug/Lib/test/test_asyncio/test_pep492.py:146> 
result=None created at 
/home/serhiy/py/cpython-debug/Lib/asyncio/base_events.py:317> took 0.133 seconds
/home/serhiy/py/cpython-debug/Lib/threading.py:864: ResourceWarning: unclosed 

  self._target(*self._args, **self._kwargs)
returning true from eof_received() has no effect when using ssl
returning true from eof_received() has no effect when using ssl
/home/serhiy/py/cpython-debug/Lib/asyncio/base_events.py:379: ResourceWarning: 
unclosed event loop <_UnixSelectorEventLoop running=False closed=False 
debug=False>
  warnings.warn("unclosed event loop %r" % self, ResourceWarning)
...
1 test OK.

Cited lines are repeated 6 times (for the number of test runs).

--
components: Tests, asyncio
messages: 255475
nosy: giampaolo.rodola, gvanrossum, haypo, pitrou, serhiy.storchaka, yselivanov
priority: normal
severity: normal
status: open
title: Resource warnings when run test_asyncio in leaks searching mode
type: resource usage
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

[issue25704] Update the devguide to 3.5


Terry J. Reedy added the comment:

The section of committing.rst in question was updated from 3.3 and 3.4 to 3.4 
and 3.5 in 414a7e2067b2 after 3.4 came out.  I think we should continue to 
update it.

--
nosy: +terry.reedy

___
Python tracker 

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

[issue25749] asyncio.Server class documented but not exported

2015-11-27 Thread Yury Selivanov


Yury Selivanov added the comment:

Let's not export the Server class -- in uvloop, for instance, I have a 
completely different internal implementation of Server (I can't use the one 
from asyncio).

--

___
Python tracker 

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

[issue25743] Clarify exactly what \w matches in UNICODE mode

2015-11-27 Thread Zack Weinberg


Zack Weinberg added the comment:

FWIW, the actual behavior of \w matching "everything in Unicode general 
categories L* and N*, plus U+005F (underscore)" is consistent across all 
versions I can conveniently test (2.7, 3.4, 3.5).

In 2.7, there are four characters in general category Nl that \w doesn't match, 
but I believe that is just a bug, not an intentional difference of behavior.

--

___
Python tracker 

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

[issue25733] Idle does not handle non-standard compile errors


Terry J. Reedy added the comment:

I believe startup files are compiled in PyShell.py, line 649 (3.x)
try:
code = compile(source, filename, "exec")
except (OverflowError, SyntaxError):

and editor code is compiled in ScriptBinding.py, line 100
try:
# If successful, return the compiled code
return compile(source, filename, "exec")
except (SyntaxError, OverflowError, ValueError) as value:

Adding SystemError to the tuple is trivial.  I just need to test to verify.  
(Side note: I think the tuple should be the same for both.  The reasons for 
entries other than SyntaxError should be documented.  ValueError when 
compiling?)

I believe that interactive input is forwarded to stdlib 
code.InteractiveInterpreter in PyShell.py, line 679
try:
# InteractiveInterpreter.runsource() calls its runcode() method,
# which is overridden (see below)
return InteractiveInterpreter.runsource(self, source, filename)

The compile call and error catching is inside Lib/code.py, line 57.
try:
code = self.compile(source, filename, symbol)
except (OverflowError, SyntaxError, ValueError):

It should be fixed here.

--
nosy: +terry.reedy

___
Python tracker 

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

[issue22233] http.client splits headers on non-\r\n characters

2015-11-27 Thread R. David Murray


R. David Murray added the comment:

I agree.  Can you update the email issue with this suggestion and/or a patch?

The problem with this, of course is backward compatibility, but since it is 
more correct per the RFCs, our past policy has been to fix it anyway.

--

___
Python tracker 

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

[issue25752] asyncio.readline - add customizable line separator


STINNER Victor added the comment:

I like the idea. It's common in protocols to have different kinds of
"terminators" to mark the end of a message. C strings use a null byte
for example. I would be trivial to accept other terminators, since we
don't store received bytes as lines, but as a raw byte string
(technically in a bytearray).

> if not isinstance(separator, bytes) or len(separator) != 1:

Yes, we should only reject empty terminator string. But terminator
strings of more than 1 character are fine, no? I don't think that we
need to put an arbitrary limitation here.

> Since I cannot create pull-request, I will write just here what I want:

Oh, what is your problem? You can use https://github.com/python/asyncio

--

___
Python tracker 

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

[issue25608] ascynio readexactly() should raise ValueError if passed length <= 0 in argument

2015-11-27 Thread Guido van Rossum


Guido van Rossum added the comment:

read(0) on a regular stream and os.read(fd, 0) also return an empty string 
without error. This is not something we should keep debating.

--

___
Python tracker 

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

[issue25696] "make -j9 install" fails because bininstall target requires the libainstall target


Changes by Martin Panter :


Added file: http://bugs.python.org/file41178/bininstall-4.patch

___
Python tracker 

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

[issue25757] Subclasses of property lose docstring

2015-11-27 Thread Emanuel Barry


Emanuel Barry added the comment:

Pointed out a refleak and a small nit.

--
nosy: +ebarry
stage:  -> patch review

___
Python tracker 

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

[issue25741] Usual Installation Directory

2015-11-27 Thread Steve Dower


Steve Dower added the comment:

That patch looks good to me.

LOCALAPPDATA is set by the operating system, typically to 
C:\Users\\AppData\Local (at least since Vista I think? Certainly 
since Win7). While it's possible to customize it, people who know how to do 
that won't be emailing webmasters expecting technical support.

--

___
Python tracker 

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

[issue25754] Test test_rlcompleter failed if run twice


New submission from Serhiy Storchaka:

$ ./python -m test.regrtest test_rlcompleter test_rlcompleter
[1/2] test_rlcompleter
[2/2] test_rlcompleter
test test_rlcompleter failed -- Traceback (most recent call last):
  File "/home/serhiy/py/cpython-debug/Lib/test/test_rlcompleter.py", line 66, 
in test_attr_matches
['CompleteMe.mro(', 'CompleteMe.spam'])
AssertionError: Lists differ: ['CompleteMe.me(', 'CompleteMe.mro(', 
'CompleteMe.spam'] != ['CompleteMe.mro(', 'CompleteMe.spam']

First differing element 0:
CompleteMe.me(
CompleteMe.mro(

First list contains 1 additional elements.
First extra element 2:
CompleteMe.spam

- ['CompleteMe.me(', 'CompleteMe.mro(', 'CompleteMe.spam']
?  --

+ ['CompleteMe.mro(', 'CompleteMe.spam']

1 test OK.
1 test failed:
test_rlcompleter

--
components: Tests
messages: 255492
nosy: martin.panter, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Test test_rlcompleter failed if run twice
type: behavior
versions: Python 3.6

___
Python tracker 

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

[issue25742] locale.setlocale does not work with unicode strings


STINNER Victor added the comment:

I don't see the benefit of supporting Unicode strings for setlocale() 
arguments: locale name are always encodable to ASCII, so loc.decode('ascii') is 
enough to workaround the issue.

But well, I think it's ok if it doesn't make the code much more complex ;-)

I wrote a patch, what do you think? Is it worth it? ;-)

--
keywords: +patch
Added file: http://bugs.python.org/file41175/setlocale_unicode.patch

___
Python tracker 

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

[issue25757] Subclasses of property lose docstring

2015-11-27 Thread Torsten Landschoff


New submission from Torsten Landschoff:

I actually found this in Python2, but it is still unchanged in Python 3.6 dev. 
Namely, creating an instance of a class derived from property will drop the 
docstring passed explicitly to the constructor: 

torsten@defiant:~$ python3.6
Python 3.6.0a0 (default:9fcfdb53e8af, Nov 27 2015, 23:11:09) 
[GCC 4.8.4] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> property(doc="Hello world").__doc__
'Hello world'
>>> class SubProp(property): pass
... 
>>> SubProp(doc="Hello world").__doc__
>>>

This war surprising to me. I actually used a subclass of property to describe 
fields of configuration classes with extensive documentation, which disappeared 
during runtime.

In Python2 I work around this by assigning to __doc__ as the last thing in the 
constructor of my SubProp class.

--
components: Interpreter Core
messages: 255511
nosy: torsten
priority: normal
severity: normal
status: open
title: Subclasses of property lose docstring
type: behavior
versions: Python 3.6

___
Python tracker 

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

[issue25742] locale.setlocale does not work with unicode strings


STINNER Victor added the comment:

Marc-Andre Lemburg added the comment:
> No big deal. There are probably lots more places in the stdlib which
> break without Unicode compiled in... :-)

Well, to have more fun, try to run any Python application with a
Python compiled without Unicode support *and* without thread support
:-D

--

___
Python tracker 

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

[issue25757] Subclasses of property lose docstring

2015-11-27 Thread Torsten Landschoff


Torsten Landschoff added the comment:

Just a note about the patch: I changed the behaviour a bit in that the code 
does not ignore random exceptions while getting getter.__doc__.

I think that would be surprising for most users and it also does not match the 
application of the doc field to the subclass, where exceptions are propagated.

--

___
Python tracker 

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

[issue25757] Subclasses of property lose docstring

2015-11-27 Thread Torsten Landschoff


Torsten Landschoff added the comment:

Here is a proposed patch to correct this including regression tests.

--
keywords: +patch
Added file: http://bugs.python.org/file41176/subprop_doc.diff

___
Python tracker 

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

[issue16151] Deferred KeyboardInterrupt in interactive mode


Martin Panter added the comment:

Discovered Issue 22923 is already open about “Display all possibilities” 
problem. It sounds like that may be a regression in Readline, not Python.

--

___
Python tracker 

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

[issue25742] locale.setlocale does not work with unicode strings


Marc-Andre Lemburg added the comment:

I wouldn't say this is a feature request. 

What the code wanted to check is "if this is an iterable of two strings, 
convert these to a locale string". I have no idea why the doc string uses 
"iterable". IMO, a tuple of two strings would have been fine and make the test 
case a lot simpler - too late to fix, though.

If the code works with Unicode strings, I think we can change the test to:

if locale and not isinstance(locale, basestring):
...

In Python 3, the function will only accept Unicode strings, so no need to fix 
things there.

@tierlieb: Could you provide a patch with test for this ? Thanks.

--

___
Python tracker 

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

[issue25755] Test test_property failed if run twice


New submission from Serhiy Storchaka:

$ ./python -m test.regrtest test_property test_property
[1/2] test_property
[2/2] test_property
test test_property failed -- Traceback (most recent call last):
  File "/home/serhiy/py/cpython-debug/Lib/test/test_property.py", line 172, in 
test_property_decorator_doc_writable
self.assertEqual(sub.__class__.spam.__doc__, 'Eggs')
AssertionError: 'Spam' != 'Eggs'
- Spam
+ Eggs


1 test OK.
1 test failed:
test_property

--
components: Tests
messages: 255493
nosy: serhiy.storchaka
priority: normal
severity: normal
status: open
title: Test test_property failed if run twice
type: behavior
versions: Python 3.6

___
Python tracker 

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

[issue25742] locale.setlocale does not work with unicode strings

2015-11-27 Thread Roundup Robot


Roundup Robot added the comment:

New changeset 7841e9b614eb by Victor Stinner in branch '2.7':
Closes #25742: locale.setlocale() now accepts a Unicode string for its second
https://hg.python.org/cpython/rev/7841e9b614eb

--
nosy: +python-dev
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

___
Python tracker 

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

[issue25742] locale.setlocale does not work with unicode strings

Marc-Andre Lemburg added the comment:

On 27.11.2015 23:50, STINNER Victor wrote:
> 
> STINNER Victor added the comment:
> 
>> BTW: Why did you use (_str, _unicode) instead of basestring ?
> 
> Serhiy usually insists that technically, it's possible to compile Python 2.7 
> without Unicode support. I don't believe that anyone uses this crazy feature, 
> but well, it was easier to use _unicode (which is already defined) than 
> trying to run a poll on python users :-)

Hmm, but basestring is always defined, even when Python is compiled
without Unicode support (which I agree is not used much these
days). unicode won't exist in such a Python version, so basestring
is actually safer to use than the tuple.

--

___
Python tracker 

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

[issue25522] IDLE: warn if save-as name matches stdlib name

2015-11-27 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

[issue25252] Hard-coded line ending in asyncio.streams.StreamReader.readline


Martin Panter added the comment:

Eric seems to have retracted this proposal, however Issue 25752 has also been 
opened, which sounds very similar.

--
nosy: +martin.panter
status: open -> closed

___
Python tracker 

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

[issue18082] Inconsistent behavior of IOBase methods on closed files


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

[issue25742] locale.setlocale does not work with unicode strings


Marc-Andre Lemburg added the comment:

On 27.11.2015 23:11, STINNER Victor wrote:
> 
> STINNER Victor added the comment:
> 
> I don't see the benefit of supporting Unicode strings for setlocale() 
> arguments: locale name are always encodable to ASCII, so loc.decode('ascii') 
> is enough to workaround the issue.
> 
> But well, I think it's ok if it doesn't make the code much more complex ;-)
> 
> I wrote a patch, what do you think?

Thanks :-)

> Is it worth it? ;-)

I think so, since the current failure for Unicode is rather
obscure.

BTW: Why did you use (_str, _unicode) instead of basestring ?

--

___
Python tracker 

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

[issue9504] signal.signal/signal.alarm not working as expected


STINNER Victor added the comment:

I don't understand this issue.

I would expect that a system call fails with EINTR if it is interrupted by a 
signal. Python explicitly configures the C library to get EINTR errors: 
automatic retry is disabled when Python sets its signal handlers.

If a system call doesn't fail, what shoud we do with the result, especially 
when reading data (read/recv)?

Yes, we _can_ checks to check regulary if we got a C signal by adding checks, 
but it's unclear to me if we must raise the exception immediatly, or later. 
Immedialty if I understand correctly the initial message. So should we check 
*all* system calls, or only system calls well known to block on I/O, like 
read/write, send/recv, select, etc.?

Do we try to workaround design choices by the Linux kernel and the GNU libc?

Right now, my favorite choice would be to do nothing. Yes, sometimes signals 
are delayed. Sometimes, a signal doesn't interrupt immediatly a blocked 
program. It's not perfect. But it's already very complex, I'm not sure that I 
want to make the code even more complex to check for signals in more places.

--

___
Python tracker 

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

[issue25696] "make -j9 install" fails because bininstall target requires the libainstall target


Martin Panter added the comment:

I agree your patches should fix your practical bug (I can reproduce it, two out 
of three times). My concern is more about making the code cleaner and less 
likely to grow problems in the future. :) The worse case with patch 3 would be 
the “Creating directory” message being echoed twice. I am just trying to get 
the makefile cleaner.

If that block compiled a file, instead of just creating a directory, then it 
would be a worse problem. The second compile command could truncate the first 
version, causing errors later on.

Also, I don’t believe adding the dash (-) prefix is a good idea here. It tells 
Make to keep going even if the command failed. In this case, if the directory 
already exists, the “if” statement will succeed, and the only way it can fail 
is if $(INSTALL) fails, which I think we would want to know about. The original 
“for” loop under libainstall does not include a dash.

bininstall-4.patch implements my suggestion from before.

--

___
Python tracker 

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

[issue9504] signal.signal/signal.alarm not working as expected


Martin Panter added the comment:

Okay, I tend to agree, and don’t have a problem with rejecting this.

--

___
Python tracker 

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

[issue25755] Test test_property failed if run twice


Serhiy Storchaka added the comment:

As result the test is failed in leaks searching mode.

$ ./python -m test.regrtest -uall -R 3:3 test_property
[1/1] test_property
beginning 6 repetitions
123456
test test_property failed -- Traceback (most recent call last):
  File "/home/serhiy/py/cpython-debug/Lib/test/test_property.py", line 172, in 
test_property_decorator_doc_writable
self.assertEqual(sub.__class__.spam.__doc__, 'Eggs')
AssertionError: 'Spam' != 'Eggs'
- Spam
+ Eggs


1 test failed:
test_property

--
nosy: +berker.peksag, rhettinger

___
Python tracker 

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

[issue25749] asyncio.Server class documented but not exported


STINNER Victor added the comment:

Yury Selivanov added the comment:
> But Ron suggested to actually export the Server class, so that it's available 
> as 'asyncio.Server'. And I think that *that* is a bad idea, (...)

I know, but IMHO the issue is wider than just exporting or not the
symbol. Right now, create_server() doc explicitly says that the list
of sockets is available in server.sockets attribute. We should mention
that it's not always the case, it's only available on "some"
implementations of event loops.

--

___
Python tracker 

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

[issue25742] locale.setlocale does not work with unicode strings


STINNER Victor added the comment:

Marc-Andre Lemburg added the comment:
> Hmm, but basestring is always defined, even when Python is compiled
> without Unicode support (...)

Oh, I didn't know. Well, I already pushed my patch and it works. Feel
free to modify locale.py to use basestring. I'm not interested to
spend time on this *minor* issue anymore ;-)

Thanks for the review.by the way.

--

___
Python tracker 

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

[issue25608] ascynio readexactly() should raise ValueError if passed length <= 0 in argument

2015-11-27 Thread Марк Коренберг


Марк Коренберг added the comment:

result of readexactly(0) is indistinguishable from EOF, so no one should try to 
use that as I think.

What is the useful case when zero bytes should be read ?

--

___
Python tracker 

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

[issue10399] AST Optimization: inlining of function calls


STINNER Victor added the comment:

"Can we resurrect this, perhaps by taking it up on python-dev?"

I created a new "FAT Python" project to reimplement such kind of optimizations 
with a similar design (similar but different ;-)):
https://faster-cpython.readthedocs.org/fat_python.html

--
nosy: +haypo

___
Python tracker 

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

[issue25751] ctypes.util , Shell Injection in find_library()


Martin Panter added the comment:

There is a patch at Issue 22636 which looks like it replaces all five 
os.popen() calls.

--
nosy: +martin.panter
resolution:  -> duplicate
status: open -> closed
superseder:  -> avoid using a shell in ctypes.util: replace os.popen with 
subprocess

___
Python tracker 

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

[issue22636] avoid using a shell in ctypes.util: replace os.popen with subprocess


Martin Panter added the comment:

See Issue 25751 for some demo exploits on Linux, if anyone wants inspiration 
for test cases. Maybe this should be applied as a bug fix. I haven’t looked at 
the patch, other than confirming it removes all five os.popen() calls.

--
nosy: +martin.panter
stage:  -> patch review

___
Python tracker 

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

[issue25751] ctypes.util , Shell Injection in find_library()


Martin Panter added the comment:

Your Ubuntu link seems broken, or is that a private report?

--

___
Python tracker 

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

[issue22636] avoid using a shell in ctypes.util: replace os.popen with subprocess


Changes by Martin Panter :


--
components: +ctypes

___
Python tracker 

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

[issue25742] locale.setlocale does not work with unicode strings


STINNER Victor added the comment:

> BTW: Why did you use (_str, _unicode) instead of basestring ?

Serhiy usually insists that technically, it's possible to compile Python 2.7 
without Unicode support. I don't believe that anyone uses this crazy feature, 
but well, it was easier to use _unicode (which is already defined) than trying 
to run a poll on python users :-)

--

___
Python tracker 

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

[issue25742] locale.setlocale does not work with unicode strings


Marc-Andre Lemburg added the comment:

On 28.11.2015 00:00, STINNER Victor wrote:
> 
> STINNER Victor added the comment:
> 
> Marc-Andre Lemburg added the comment:
>> Hmm, but basestring is always defined, even when Python is compiled
>> without Unicode support (...)
> 
> Oh, I didn't know. Well, I already pushed my patch and it works. Feel
> free to modify locale.py to use basestring. I'm not interested to
> spend time on this *minor* issue anymore ;-)

No big deal. There are probably lots more places in the stdlib which
break without Unicode compiled in... :-)

> Thanks for the review.by the way.

Thanks for the patch.

--

___
Python tracker 

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

[issue25756] asyncio WriteTransport documentation typo

2015-11-27 Thread Марк Коренберг


New submission from Марк Коренберг:

Here is the match against master.


Doc/library/asyncio-protocol.rst:

@@ -156,9 +156,9 @@ WriteTransport
   high-water limit is given, the low-water limit defaults to an
   implementation-specific value less than or equal to the
   high-water limit.  Setting *high* to zero forces *low* to zero as
-  well, and causes :meth:`pause_writing` to be called whenever the
+  well, and causes :meth:`resume_writing` to be called whenever the
   buffer becomes non-empty.  Setting *low* to zero causes
-  :meth:`resume_writing` to be called only once the buffer is empty.
+  :meth:`pause_writing` to be called only once the buffer is empty.
   Use of zero for either limit is generally sub-optimal as it
   reduces opportunities for doing I/O and computation
   concurrently.

--
assignee: docs@python
components: Documentation
messages: 255508
nosy: docs@python, mmarkk
priority: normal
severity: normal
status: open
title: asyncio WriteTransport documentation typo
type: enhancement
versions: Python 3.2, Python 3.3, 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

[issue21579] Python 3.4: tempfile.close attribute does not work

2015-11-27 Thread Марк Коренберг


Марк Коренберг added the comment:

No activity last week ? Why not to merge ?

--

___
Python tracker 

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

[issue22233] http.client splits headers on non-\r\n characters


Martin Panter added the comment:

David: what is the email issue you mentioned? In the mean time, I am uploading 
a patch to this issue.

It seems using StringIO is a bit slower than str.splitlines(). I found a way to 
optimize building long lines, which compensated a lot of the loss, but this 
optimization would apply even without using StringIO. My patch makes 
test.test_email 0.3% slower (the optimization alone would make it 4.4% faster), 
and test_email.TestFeedParsers.test_long_lines() is 3% slower (optimization 12% 
faster).

I also tried two other alternatives to str.splitlines(), but they were both 
slower than the StringIO technique:
* _partial is a list of UTF-8 bytes; join and use bytes.splitlines()
* _partial is a UTF-8 bytearray; use bytearray.splitlines()

--
keywords: +patch
stage: needs patch -> patch review
versions: +Python 3.6
Added file: http://bugs.python.org/file41177/crlf-headers.patch

___
Python tracker 

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

[issue25754] Test test_rlcompleter failed if run twice


Martin Panter added the comment:

Here is a possible fix, just using mock.patch.object() and a context manager to 
remove the attribute after the test.

--
keywords: +patch
stage:  -> patch review
Added file: http://bugs.python.org/file41179/repeat-rlcompleter.patch

___
Python tracker 

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

[issue16151] Deferred KeyboardInterrupt in interactive mode


Changes by Serhiy Storchaka :


--
dependencies: +No prompt for "display all X possibilities" on 
completion-enabled input()

___
Python tracker 

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

[issue25754] Test test_rlcompleter failed if run twice


Serhiy Storchaka added the comment:

LGTM.

--
stage: patch review -> commit review

___
Python tracker 

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

[issue25742] locale.setlocale does not work with unicode strings

2015-11-27 Thread tierlieb


New submission from tierlieb:

Within locale.py in setlocale your have this piece of code:

if locale and type(locale) is not type(""):
# convert to string
locale = normalize(_build_localename(locale))

That does not work with unicode strings as I found out after wondering quite a 
bit about the difference was between my tests and my production code...

So either expand the check here to include type(u"") or make _build_localename 
smarter.

--
components: Unicode
messages: 255461
nosy: ezio.melotti, haypo, tierlieb
priority: normal
severity: normal
status: open
title: locale.setlocale does not work with unicode strings
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

[issue25696] "make -j9 install" fails because bininstall target requires the libainstall target


STINNER Victor added the comment:

> $(LIBPC) is a single directory name, so I suggest dropping the “for” loop.

Ok, here is a version without loop. I also added "-" before the if to mimick 
other lines of the bininstall target.

Does it look better now?

> (...) there is technically still a race with “libainstall” and “bininstall” 
> both testing and creating the same directory.

Sorry, I don't understand. Is it an issue in practice to create the same 
directory twice "at the same time"? Are you able to reproduce the bug?

Please try my use case: "./configure && make && make -j10 install" and enjoy 
the partial installation :-) (The python binary is installed in bin/ but it 
doesn't work because the stdlib is completly missing.)

--
Added file: http://bugs.python.org/file41171/bininstall-3.patch

___
Python tracker 

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

[issue25753] Reference leaks in test_smtplib


New submission from Serhiy Storchaka:

$ ./python -m test.regrtest -uall -R 3:3 test_smtplib
[1/1] test_smtplib
beginning 6 repetitions
123456
..
test_smtplib leaked [0, 1, 1] references, sum=2
test_smtplib leaked [0, 1, 2] memory blocks, sum=3
1 test failed:
test_smtplib

--
components: Tests
messages: 255491
nosy: serhiy.storchaka
priority: normal
severity: normal
status: open
title: Reference leaks in test_smtplib
type: resource usage
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

[issue25749] asyncio.Server class documented but not exported

STINNER Victor added the comment:

Yeah, I recall this point. The doc points to Server, but Guido didn't
want to expose "implementation details" of Server like sockets.
Different implementations of event loops (Yury gave the good example
of uvloop based on libuv) don't give (direct) access to sockets.

The problem is maybe that we try to document two different things at
the same place: asyncio "portable" API (the PEP 3156), and the
implementation of "default" event loops.

Even if it's not possible to directly use server sockets, it's kind of
useful to get them. What do you think?

Server.sockets is documented at:
https://docs.python.org/dev/library/asyncio-eventloop.html#asyncio.Server.sockets

Server.sockets is explicitly documented at:
https://docs.python.org/dev/library/asyncio-eventloop.html#asyncio.BaseEventLoop.create_server

I would prefer to keep the Server.sockets doc, but explain better that
it's an "implementation detail". We already have something similar for
"CPython" implementation details in the doc. Examples:
- https://docs.python.org/dev/library/sys.html#sys._debugmallocstats
- https://docs.python.org/dev/library/sys.html#sys._getframe
- https://docs.python.org/dev/library/dis.html#module-dis
- etc.

What do you think of reusing the ".. impl-detail:" markup? Or do you
prefer to write a different kind of box for asyncio? Or just not box
and a simple sentence?

___
Python tracker

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

[issue25749] asyncio.Server class documented but not exported

2015-11-27 Thread Yury Selivanov


Yury Selivanov added the comment:

> Yeah, I recall this point. The doc points to Server, but Guido didn't
want to expose "implementation details" of Server like sockets.
Different implementations of event loops (Yury gave the good example
of uvloop based on libuv) don't give (direct) access to sockets.

I actually found a way to extract a fileno (there is an API for that).

But Ron suggested to actually export the Server class, so that it's available 
as 'asyncio.Server'. And I think that *that* is a bad idea, since the actual 
implementation of Server is tied to event loop and transports, which may be 
implemented differently (as in uvloop)

--

___
Python tracker 

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

[issue14826] urllib2.urlopen fails to load URL