[issue23203] Aliasing import of sub-{module, package} from the package raises AttributeError on import.

[Ezio Melotti]

Changes by Ezio Melotti :


--
nosy: +brett.cannon, eric.snow, ezio.melotti, ncoghlan
type:  -> behavior

___
Python tracker 

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

[issue23086] Add start and stop parameters to the Sequence.index() ABC mixin method

[Devin Jeanpierre]

Devin Jeanpierre added the comment:

I take it back, I don't want to copy what the list type does, because it's 
wrong: http://bugs.python.org/issue23204

--

___
Python tracker 

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

[issue23204] list.index and rest of list methods disagree if a value is in the list if it's mutated during the call

[Devin Jeanpierre]

New submission from Devin Jeanpierre:

>>> class AppendOnUnequal(object):
... def __init__(self, append_to):
... self.append_to = append_to
... def __eq__(self, other):
... if self is other:
... return True
... self.append_to.append(self)
... return False
... 
>>> L = [1]; AppendOnUnequal(L) in L
True
>>> L = [1]; L.count(AppendOnUnequal(L))
1
>>> L = [1]; L.remove(AppendOnUnequal(L))
>>> L = [1]; L.index(AppendOnUnequal(L))
Traceback (most recent call last):
  File "", line 1, in 
ValueError: <__main__.AppendOnUnequal object at 0x7f2562d071d0> is not in list


.index() is the only odd one out here. Looks like a bug to me.

--
components: Interpreter Core
messages: 233721
nosy: Devin Jeanpierre
priority: normal
severity: normal
status: open
title: list.index and rest of list methods disagree if a value is in the list 
if it's mutated during the call
type: behavior
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6

___
Python tracker 

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

[issue23185] add inf and nan to math module

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

May be make math.inf and math.nan special objects so that for all x (except inf 
and nan):

x < math.inf
x > -math.inf
not (x < math.nan)
not (x > math.nan)

--

___
Python tracker 

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

[issue23203] Aliasing import of sub-{module, package} from the package raises AttributeError on import.

[Franck Michea]

New submission from Franck Michea:

Hi, for those of you that prefer to read an example, you can read that 
commented demonstration of the bug[1].

Today I discovered what I think is a bug in the import system. Here is the 
basic setup:

We have three nested packages: foo -> bar -> baz. The bar package imports 
foo.bar.baz. We try to import foo.bar. This works well unless we try to alias 
the foo.bar.baz import in foo.bar with the "import ... as ..." syntax. In that 
case the file will be read and executed but when we get out of the import 
statement, then python throws:

Traceback (most recent call last):
  File "", line 1, in 
  File "foo_alias_mod/bar/__init__.py", line 1, in 
import foo_alias_mod.bar.baz as name_does_not_matter
AttributeError: 'module' object has no attribute 'bar'

This works whether baz is a package or a module actually. It does not matter if 
it's from the interpreter, or in a file, ... I've seen it trigger with 2.7.5, 
2.7.9, 3.4.5, tip, so I guess this has been here for some time.

Please read the link below for a complete demo, and you can always download the 
tarball[2] to test yourself.

[1]: Commented demonstration: http://98810f8c06.net/wtf_python.html
[2]: Tarball for test: http://98810f8c06.net/wtf_python-demo.tar.bz2

--
components: Interpreter Core
messages: 233719
nosy: franck
priority: normal
severity: normal
status: open
title: Aliasing import of sub-{module,package} from the package raises 
AttributeError on import.

___
Python tracker 

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

[issue23202] pyvenv does not fail like documented when a venv already exists

[Florian Bruhin]

New submission from Florian Bruhin:

https://docs.python.org/3/library/venv.html says:

> If the target directory already exists an error will be raised, unless the 
> --clear or --upgrade option was provided.

However, that doesn't seem to be the case:

[florian@ginny ~]$ python --version
Python 3.4.2
[florian@ginny ~]$ pyvenv foobar
[florian@ginny ~]$ ls foobar
bin  include  lib  lib64  pyvenv.cfg
[florian@ginny ~]$ pyvenv foobar
[florian@ginny ~]$

--
components: Library (Lib)
messages: 233718
nosy: The Compiler, vinay.sajip
priority: normal
severity: normal
status: open
title: pyvenv does not fail like documented when a venv already exists
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

[issue23184] Unused imports, variables, file in IDLE

[Al Sweigart]

Al Sweigart added the comment:

I've updated the patch.

I've removed the EditorWindow deletion. Importing that and using it as a class 
variable instead of using an assignment statement wasn't picked up. (Is there a 
more opaque way to do this import?)

I've left the RemoteDebugger.py change in. The frame variable name is 
(confusingly) reused:

frame = frametable[fid]
# ...cut for brevity...
stack, i = self.idb.get_stack(frame, tb)
stack = [(wrap_frame(frame), k) for frame, k in stack]

Changed to:

# ...cut for brevity...
stack, i = self.idb.get_stack(frametable[fid], tb)
stack = [(wrap_frame(frame), k) for frame, k in stack]


The first use of frame is eliminated by simply using frametable[fid] instead. 
The second use is as the temporary variable inside the list comprehension, 
which means the "frame" name is reused. With this change, the only time the 
frame local variable is used is in the list comprehension. This gets rid of the 
name reuse and makes it a bit simpler.

--
Added file: http://bugs.python.org/file37651/idle_unused_patch2.diff

___
Python tracker 

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

[issue23184] Unused imports, variables, file in IDLE

[Al Sweigart]

Al Sweigart added the comment:

*more transparent, that is. Not opaque.

--

___
Python tracker 

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

[issue16192] ctypes - documentation example

[Brian Thorne]

Changes by Brian Thorne :


--
nosy:  -Thorney, chris.jerdonek, eric.araujo, ezio.melotti, georg.brandl
status: open -> closed

___
Python tracker 

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

[issue23201] Decimal(0)**0 is an error, 0**0 is 1, but Decimal(0) == 0

[Chris Rebert]

Chris Rebert added the comment:

This behavior seems to be required by the General Decimal Arithmetic
Specification (http://speleotrove.com/decimal/daexcep.html ):

> The following exceptional conditions can occur:
> [...]
> Invalid operation
> This occurs and signals "invalid-operation" if:
> [...]
> * both operands of the "power" operation are zero

"signals invalid-operation" apparently being mapped by default in Python to 
"raise the InvalidOperation exception".

--
nosy: +cvrebert

___
Python tracker 

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

[issue23201] Decimal(0)**0 is an error, 0**0 is 1, but Decimal(0) == 0

[Devin Jeanpierre]

Devin Jeanpierre added the comment:

Yes, also, it is documented: 
https://docs.python.org/3/library/decimal.html#decimal.InvalidOperation

Still, the status quo is bad. At the very least there should be clear 
documentation on how Decimal differs in behavior from floats and ints. (Other 
than the obvious, like 1/5 taking on a different value -- although explicitly 
mentioning that in the list might be a good idea.)

BTW, 0**0=1 is not mathematically impure. It at one point was fairly well 
accepted as the right answer, since it's the one that tends to come out 
naturally . e.g. http://arxiv.org/abs/math/9205211 page 6 ("ripples") . This 
might explain why ints and floats so casually evaluate 0**0 to 1.

--

___
Python tracker 

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

[issue23201] Decimal(0)**0 is an error, 0**0 is 1, but Decimal(0) == 0

[Josh Rosenberg]

Josh Rosenberg added the comment:

Intentional, but really hard to justify from a consistency perspective. There 
appear to be several reasonable arguments to treat it as 1 regardless of the 
mathematical impurity ( 
https://www.math.hmc.edu/funfacts/ffiles/10005.3-5.shtml ), and since we 
clearly accept that for int and float, it seems reasonable to extend it to 
Decimal.

--
nosy: +josh.r

___
Python tracker 

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

[issue23201] Decimal(0)**0 is an error, 0**0 is 1, but Decimal(0) == 0

[Ezio Melotti]

Ezio Melotti added the comment:

In the code there is this comment:
# 0**0 = NaN (!), x**0 = 1 for nonzero x (including +/-Infinity)
and raising the error for this specific case seems intentional.

--
nosy: +ezio.melotti, facundobatista, mark.dickinson, rhettinger, skrah
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

[issue23201] Decimal(0)**0 is an error, 0**0 is 1, but Decimal(0) == 0

[Devin Jeanpierre]

Changes by Devin Jeanpierre :


--
type:  -> behavior

___
Python tracker 

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

[issue23201] Decimal(0)**0 is an error, 0**0 is 1, but Decimal(0) == 0

[Devin Jeanpierre]

New submission from Devin Jeanpierre:

>>> import decimal
>>> x = 0
>>> y = float(x)
>>> z = decimal.Decimal(x)
>>> x == y == z == x
True
>>> x ** x
1
>>> y**y
1.0
>>> z**z
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/decimal.py", line 2216, in __pow__
return context._raise_error(InvalidOperation, '0 ** 0')
  File "/usr/lib/python2.7/decimal.py", line 3872, in _raise_error
raise error(explanation)
decimal.InvalidOperation: 0 ** 0

This is PHP-like and confusing, and maybe not justified just by standards 
compliance. If it is justified by standards compliance, this deserves to be 
spelled out in big red letters in the documentation for the decimal module, 
along with any other inconsistencies.

--
components: Library (Lib)
messages: 233711
nosy: Devin Jeanpierre
priority: normal
severity: normal
status: open
title: Decimal(0)**0 is an error, 0**0 is 1, but Decimal(0) == 0
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

[issue23200] Clarify max_length and flush() for zlib decompression

[Martin Panter]

Martin Panter added the comment:

The processing of unconsumed_tail in flush() was introduced via Issue 16411. 
Before that I suspect flush() was assumed to only be called when max_length was 
not used.

The decompress() method changed from Z_NO_FLUSH to Z_SYNC_FLUSH in Feb 2001; 
see revision 01c2470eeb2e. I guess previously flush() was necessary to get all 
your data. The max_length parameter was added later in October that year; see 
Issue 403753 and revision 60e12f83d2d2.

--

___
Python tracker 

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

[issue23200] Clarify max_length and flush() for zlib decompression

[Martin Panter]

New submission from Martin Panter:

This simple patch documents that max_length has to be non-zero. The 
implementation actually uses zero as a special value to indicate max_length was 
not specified.

Also, I wonder what the point of the Decompressor.flush() method is. Reading 
the module code and zlib manual, it looks like it would return the same data as 
decompressor.decompress(decompressor.unconsumed_tail), except that it uses the 
Z_FINISH flag instead of Z_SYNC_FLUSH, so that zlib can optimize by assuming no 
more data is to be processed. Since unconsumed_tail is read-only and only 
relevant when using max_length, and flush does not support max_length, I wonder 
if the flush() method should be deprecated.

To further test this theory, I modified the test_zlib.py file so that all 
appropriate flush() calls are equivalent to this:

self.assertFalse(dco.flush())

and the tests all still pass.

BTW, it looks to me like zlib_Decompress_flush_impl() is setting avail_out too 
high (blessing unallocated memory) when the total length is more than half of 
UNIT_MAX, but I am not in a position to test this.

--
assignee: docs@python
components: Documentation
files: max_length.patch
keywords: patch
messages: 233709
nosy: docs@python, vadmium
priority: normal
severity: normal
status: open
title: Clarify max_length and flush() for zlib decompression
versions: Python 3.4
Added file: http://bugs.python.org/file37650/max_length.patch

___
Python tracker 

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

[issue23025] ssl.RAND_bytes docs should mention os.urandom

[STINNER Victor]

STINNER Victor added the comment:

To be clear: rand.diff looks good to me, go ahead.

--

___
Python tracker 

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

[issue22038] Implement atomic operations on non-x86 platforms

[STINNER Victor]

STINNER Victor added the comment:

atomicv3.patch is wrong for GCC builtin atomic operations: the parenthesis is 
not closed. I fixed this typo in the commit.

Vitor & Gustavo: Thanks for the patch, it's now applied to Python 3.5.

I tested it on Fedora 21 (x86_64). I disabled manually HAVE_STD_ATOMIC in 
pyconfig.h to test the two new options (stdatomic header & GCC builtins).

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

___
Python tracker 

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

[issue22038] Implement atomic operations on non-x86 platforms

[Roundup Robot]

Roundup Robot added the comment:

New changeset fbe87fb071a6 by Victor Stinner in branch 'default':
Issue #22038: pyatomic.h now uses stdatomic.h or GCC built-in functions for
https://hg.python.org/cpython/rev/fbe87fb071a6

--
nosy: +python-dev

___
Python tracker 

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

[issue7676] IDLE shell shouldn't use TABs

[Terry J. Reedy]

Terry J. Reedy added the comment:

I believe I explained above the logical and technical factors that make the 
Idle shell inherently different from the console shell in this regard.  As the 
title says, this issue is about not using tabs and not about mixing tabs and 
spaces.  As I already said, my intended fix is to put the prompt in a sidebar 
(adapting the proposed editor line number code), which will allow use of space 
indents in the entry area, as in the editor.

--

___
Python tracker 

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

[issue22986] Improved handling of __class__ assignment

[Nathaniel Smith]

Nathaniel Smith added the comment:

I hereby invoke the one month ping rule! Patch, be pinged!

--

___
Python tracker 

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

[issue23197] asyncio: check if a future is cancelled before calling set_result/set_exception

[STINNER Victor]

STINNER Victor added the comment:

Oh, I forgot that the change in subprocess.py (check if waiter is cancelled 
before setting its result) is already part of the issue #23197 which comes with 
an unit test.

The changes on the SSL handshake are still needed.

--

___
Python tracker 

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

[issue23199] libpython27.a in amd64 release is 32-bit

[Zach Welch]

New submission from Zach Welch:

I tried to link a program against the libpython27.a provided by the latest 
2.7.9 amd64 installer, only to discover that the provided library is a 32-bit 
version.  I had to go through the gendef/dlltool dance in order to produce a 
useable 64-bit library from the DLL.

--
components: Library (Lib), Windows
messages: 233702
nosy: steve.dower, tim.golden, zach.ware, zwelch
priority: normal
severity: normal
status: open
title: libpython27.a in amd64 release is 32-bit
type: compile error
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

[issue7676] IDLE shell shouldn't use TABs

[Al Sweigart]

Al Sweigart added the comment:

There are three pieces of user-specified configuration: (1) the number of 
spaces for a tab set in IDLE's config, (2) the sys.ps1 value, and (3) the 
sys.ps2 value.

Currently IDLE's shell is ignoring (1) while the editor is not. IDLE's shell is 
ignoring (3) while the python shell isn't. I think the obvious solution is to 
make IDLE's shell follow the same behavior as IDLE's editor and the python 
shell.

The draw back comes from variable-pitch fonts, but I think using variable-pitch 
fonts is a minority use case and will create spacing issues regardless 
(compared pasting 8 spaces and pasting 1 tab into the editor with Lucida Sans 
Unicode). Special cases aren't special enough to break the rules.

This issue is concerned with mixed tabs and spaces in the IDLE shell, which has 
a simple fix. Putting the >>> and ... prompts in a separate space so that they 
are not copied can be done in a separate issue.

--

___
Python tracker 

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

[issue23198] asyncio: refactor StreamReader

[STINNER Victor]

New submission from STINNER Victor:

Attached patch refactors the asyncio.StreamReader class:

- use the value None instead of True or False to wake up the waiter
- add a new _wakeup_waiter() method
- replace _create_waiter() method with a _wait_for_data() coroutine function

The change adds a subgenerator (_wait_for_data), is it an issue in term of 
performances? (I don't think so.)

--
components: asyncio
files: refactor_streamreader.patch
keywords: patch
messages: 233700
nosy: gvanrossum, haypo, yselivanov
priority: normal
severity: normal
status: open
title: asyncio: refactor StreamReader
versions: Python 3.4, Python 3.5
Added file: http://bugs.python.org/file37649/refactor_streamreader.patch

___
Python tracker 

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

[issue23197] asyncio: check if a future is cancelled before calling set_result/set_exception

[STINNER Victor]

New submission from STINNER Victor:

set_result/set_exception methods of an asyncio.Future raise an exception if the 
future is cancelled.

Attached patch adds the check in 3 remaining places.

--
components: asyncio
files: asyncio.patch
keywords: patch
messages: 233699
nosy: gvanrossum, haypo, yselivanov
priority: normal
severity: normal
status: open
title: asyncio: check if a future is cancelled before calling 
set_result/set_exception
versions: Python 3.4, Python 3.5
Added file: http://bugs.python.org/file37648/asyncio.patch

___
Python tracker 

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

[issue23086] Add start and stop parameters to the Sequence.index() ABC mixin method

[Devin Jeanpierre]

Devin Jeanpierre added the comment:

I'm going to add a test case that changes the sequence length during .index(), 
and just do whatever list does in that case.

--

___
Python tracker 

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

[issue22560] Add loop-agnostic SSL implementation to asyncio

[STINNER Victor]

STINNER Victor added the comment:

For STARTTLS, see also this issue:
https://code.google.com/p/tulip/issues/detail?id=79

--

___
Python tracker 

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

[issue22970] Cancelling wait() after notification leaves Condition in an inconsistent state

[STINNER Victor]

STINNER Victor added the comment:

threading.Condition.wait() implementation is very similar to 
asyncio.Condition.wait(), and the threading code only call acquire() once, it 
doesn't loop or ignore exceptions.

Does it mean that threading.Condition.wait() has the same issue?

--

___
Python tracker 

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

[issue23086] Add start and stop parameters to the Sequence.index() ABC mixin method

[Josh Rosenberg]

Josh Rosenberg added the comment:

Note: index returns without the caller having a chance to execute code that 
would change the sequence length directly. But other threads could change it, 
as could a custom __eq__ on an object stored in the sequence (or a poorly 
implemented __getitem__ or __len__ on the sequence itself, but that's getting 
even more pathological). Thread consistency is the code's responsibility though 
(we just need to make sure we behave the best we can, and hope they use locks 
correctly), and the odds of equality of __getitem__ altering the sequence are 
much lower than the odds of someone iterating the sequence and changing it as 
they go (which is what __iter__'s implementation allows, responding with 
potentially incomplete results since items might be skipped due to the 
mutation), but keeping the sequence in a consistent state.

--

___
Python tracker 

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

[issue22970] Cancelling wait() after notification leaves Condition in an inconsistent state

[STINNER Victor]

STINNER Victor added the comment:

I don't like the idea of ignoring exceptions (CancelledError). An option may be 
to store the latest exception and reraise it when the condition is acquired.

I'm not sure that it's safe or correct to "retry" to acquire the condition.

I don't know what I should think about this issue. I don't see any obvious and 
simple fix, but I agree that inconsistencies in lock primitives is a severe 
issue.

--

___
Python tracker 

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

[issue23086] Add start and stop parameters to the Sequence.index() ABC mixin method

[Josh Rosenberg]

Josh Rosenberg added the comment:

I think it avoids len because the length might change during iteration due to 
side-effects of other code. Since a shrinking sequence would raise an 
IndexError anyway when you overran the end, it may as well not assume the 
length is static and just keep indexing forward until it hits an IndexError. 
It's less of an issue (though not a non-issue) with index, because index 
actually performs all the indexing without returning to user code; __iter__ 
pauses to allow user code to execute between each yield, so the odds of a 
length mutation are much higher.

You might be able to use len (and just say that if a side-effect of an equality 
comparison causes the sequence to change length, or another thread messes with 
it, that's your own fault), but you'd probably want  to catch and convert 
IndexError to ValueError to consistently respond to "we didn't find it" with 
the same exception.

--
nosy: +josh.r

___
Python tracker 

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

[issue23185] add inf and nan to math module

[STINNER Victor]

STINNER Victor added the comment:

Except of my small suggestion on the doc (see the review), math_inf_nan4.patch 
looks good to me.

--

___
Python tracker 

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

[issue23195] Sorting with locale (strxfrm) does not work properly with Python3 on BSD or OS X

[STINNER Victor]

STINNER Victor added the comment:

> The postresq discussion and some earlier Python issues suggest using ICU to 
> properly implement Unicode functions like collation across all platforms.

In my experience, the locale module is error-prone and not reliable, especially 
if you want portability. It just uses functions provided by the OS. And the 
locales (LC_CTYPE, LC_MESSAGE, etc.) are process-wide which become a major 
issue if you want to serve different clients using different locales... Windows 
supports a different locale per thread if I remember correctly.

It would be more reliable to use a good library like ICU. You may try:
https://pypi.python.org/pypi/PyICU

Link showing how to use PyICU to sort a Python sequence:
https://stackoverflow.com/questions/11121636/sorting-list-of-string-with-specific-locale-in-python
=> strings.sort(key=lambda x: collator[loc].getCollationKey(x).getByteArray())

--

___
Python tracker 

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

[issue23195] Sorting with locale (strxfrm) does not work properly with Python3 on BSD or OS X

[Ned Deily]

Changes by Ned Deily :


--
title: Sorting with locale (strxfrm) does not work properly with Python3 on 
Macos -> Sorting with locale (strxfrm) does not work properly with Python3 on 
BSD or OS X

___
Python tracker 

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

[issue23195] Sorting with locale (strxfrm) does not work properly with Python3 on Macos

[Ned Deily]

Ned Deily added the comment:

The initial difference appears to be a long-standing BSD (including OS X) 
versus GNU/Linux platform difference.  See, for example:
http://www.postgresql.org/message-id/18c8a481-33a6-4483-8c24-b8ce70db7...@eggerapps.at

Why there is no difference between en and fr UTF-8 is obvious when you look 
under the covers at the system locale definitions.  This is on FreeBSD 10, OS X 
10.10 is the same:

$ cd /usr/share/locale/fr_FR.UTF-8/
$ ls -l
total 8
lrwxr-xr-x  1 root  wheel   28 Jan 16  2014 LC_COLLATE -> 
../la_LN.US-ASCII/LC_COLLATE
lrwxr-xr-x  1 root  wheel   17 Jan 16  2014 LC_CTYPE -> ../UTF-8/LC_CTYPE
lrwxr-xr-x  1 root  wheel   30 Jan 16  2014 LC_MESSAGES -> 
../fr_FR.ISO8859-1/LC_MESSAGES
-r--r--r--  1 root  wheel   36 Jan 16  2014 LC_MONETARY
lrwxr-xr-x  1 root  wheel   29 Jan 16  2014 LC_NUMERIC -> 
../fr_FR.ISO8859-1/LC_NUMERIC
-r--r--r--  1 root  wheel  364 Jan 16  2014 LC_TIME

For some reason US-ASCII is used for UTF-8 collation; this is also true for 
en_US.UTF-8 and de_DE.UTF-8, the only other ones I checked.

The postresq discussion and some earlier Python issues suggest using ICU to 
properly implement Unicode functions like collation across all platforms.  But 
that has never been implemented in Python.  Nosing Marc-Andre.

--
nosy: +lemburg

___
Python tracker 

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

[issue23196] Greek letters not sorted properly

[R. David Murray]

R. David Murray added the comment:

Oops, I meant issue 23195.

--
superseder: Greek letters not sorted properly -> Sorting with locale (strxfrm) 
does not work properly with Python3 on Macos

___
Python tracker 

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

[issue23196] Greek letters not sorted properly

[R. David Murray]

R. David Murray added the comment:

This appears to be a duplicate of issue 23196 (the strxfrm issue).

--
nosy: +r.david.murray
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Greek letters not sorted properly

___
Python tracker 

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

[issue23195] Sorting with locale (strxfrm) does not work properly with Python3 on Macos

[R. David Murray]

Changes by R. David Murray :


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

[issue23195] Sorting with locale (strxfrm) does not work properly with Python3 on Macos

[R. David Murray]

Changes by R. David Murray :


--
title: Sorting with locale does not work properly with Python3 on Macos -> 
Sorting with locale (strxfrm) does not work properly with Python3 on Macos

___
Python tracker 

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

[issue23195] Sorting with locale does not work properly with Python3 on Macos

[STINNER Victor]

STINNER Victor added the comment:

locale.strxfrm() have a different implementation in Python 2 and in Python 3:
- Python 2 uses strxfrm(), so works on bytes strings
- Python 3 uses wcsxfrm(), so works on multibyte strings ("unicode" strings)

It looks like Python 2 and 3 have the same behaviour on Mac OS X: the list is 
not sorted as expected. Test on Mac OS X 10.9.2.

Imac-Photo:~ haypo$ cat collate2.py 
#coding:utf8
import locale, random
locale.setlocale(locale.LC_ALL, "fr_FR.UTF-8")
print("LC_COLLATE = %s" % locale.setlocale(locale.LC_COLLATE, None))
a = ["A", "E", "Z", "\xc9", "a", "e", "\xe9", "z"]
random.shuffle(a)
print(sorted(a))
print(sorted(a, key=locale.strxfrm))

Imac-Photo:~ haypo$ cat collate3.py 
#coding:utf8
import locale, random
locale.setlocale(locale.LC_ALL, "fr_FR.UTF-8")
print("LC_COLLATE = %s" % locale.setlocale(locale.LC_COLLATE, None))
a = ["A", "E", "Z", "\xc9", "a", "e", "\xe9", "z"]
random.shuffle(a)
print(ascii(sorted(a)))
print(ascii(sorted(a, key=locale.strxfrm)))

Imac-Photo:~ haypo$ LC_ALL=fr_FR.utf8 python collate2.py 
LC_COLLATE = fr_FR.UTF-8
['A', 'E', 'Z', 'a', 'e', 'z', '\xc9', '\xe9']
['A', 'E', 'Z', 'a', 'e', 'z', '\xc9', '\xe9']

Imac-Photo:~ haypo$ LC_ALL=fr_FR.utf8 ~/prog/python/default/python.exe 
~/collate3.py 
LC_COLLATE = fr_FR.UTF-8
['A', 'E', 'Z', 'a', 'e', 'z', '\xc9', '\xe9']
['A', 'E', 'Z', 'a', 'e', 'z', '\xc9', '\xe9']

On Linux, I get the expected order with Python 3:

LC_COLLATE = fr_FR.UTF-8
['A', 'E', 'Z', 'a', 'e', 'z', '\xc9', '\xe9']
['a', 'A', 'e', 'E', '\xe9', '\xc9', 'z', 'Z']

On Linux, Python 2 gives me a strange order. It's maybe an issue in my program:

haypo@selma$ python x.py 
LC_COLLATE = fr_FR.UTF-8
['A', 'E', 'Z', 'a', 'e', 'z', '\xc9', '\xe9']
['\xe9', '\xc9', 'a', 'A', 'e', 'E', 'z', 'Z']

--

___
Python tracker 

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

[issue23196] Greek letters not sorted properly

[Pierre Nugues]

New submission from Pierre Nugues:

Greek letters are not properly sorted when a locale is set. I tested a French 
and a Greek locales. Here is an output obtained from the Python interactive 
shell available from the python.org home page:

In [22]: a
Out[22]: 
('Ά',
 'Γ',
 'Η',
 'Κ',
 'Ν',
 'Ο',
 'έ',
 'ί',
 'α',
 'β',
 'γ',
 'δ',
 'ε',
 'ζ',
 'ι',
 'κ',
 'λ',
 'μ',
 'ν',
 'ο',
 'ς',
 'τ',
 'φ',
 'χ',
 'ό',
 'ϐ',
 'Ἀ',
 'ῖ')
In [26]: sorted(a, key=locale.strxfrm)
Out[26]: 
['Ἀ',
 'ῖ',
 'α',
 'Ά',
 'β',
 'ϐ',
 'Γ',
 'γ',
 'δ',
 'ε',
 'έ',
 'ζ',
 'Η',
 'ι',
 'ί',
 'Κ',
 'κ',
 'λ',
 'μ',
 'Ν',
 'ν',
 'Ο',
 'ο',
 'ό',
 'ς',
 'τ',
 'φ',
 'χ']

The letter 'ῖ' is wrongly sorted. You can try to sort the same character list 
with the ICU demonstration to see the correct ordering here: 
http://demo.icu-project.org/icu-bin/locexp?_=el&d_=fr&x=col

--
components: Unicode
messages: 233686
nosy: ezio.melotti, haypo, pnugues
priority: normal
severity: normal
status: open
title: Greek letters not sorted properly
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

[issue23195] Sorting with locale does not work properly with Python3 on Macos

[Ned Deily]

Changes by Ned Deily :


--
nosy: +ned.deily

___
Python tracker 

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

[issue23195] Sorting with locale does not work properly with Python3 on Macos

[Pierre Nugues]

New submission from Pierre Nugues:

The sorted() function does not work properly with macosx.
Here is a script to reproduce the issue:

import locale
locale.setlocale(locale.LC_ALL, "fr_FR.UTF-8")
a = ["A", "E", "Z", "a", "e", "é", "z"]
sorted(a)
sorted(a, key=locale.strxfrm)


The execution on MacOsX produces:
pierre:Flaubert pierre$ sw_vers -productVersion
10.10.1
pierre:Flaubert pierre$ python3
Python 3.4.2 (v3.4.2:ab2c023a9432, Oct  5 2014, 20:42:22) 
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
import locale
locale.setlocale(locale.LC_ALL, "fr_FR.UTF-8")
'fr_FR.UTF-8'
a = ["A", "E", "Z", "a", "e", "é", "z"]
sorted(a)
['A', 'E', 'Z', 'a', 'e', 'z', 'é']
sorted(a, key=locale.strxfrm)
['A', 'E', 'Z', 'a', 'e', 'z', 'é']


while it produces this on your interactive shell (python.org):
In [10]: import locale
In [11]: locale.setlocale(locale.LC_ALL, "fr_FR.UTF-8")
Out[11]: 'fr_FR.UTF-8'
In [12]: a = ["A", "E", "Z", "a", "e", "é", "z"]
In [13]: sorted(a)
Out[13]: ['A', 'E', 'Z', 'a', 'e', 'z', 'é']
In [14]: sorted(a, key=locale.strxfrm)
Out[14]: ['a', 'A', 'e', 'E', 'é', 'z', 'Z']

which is correct.

--
components: Unicode
messages: 233685
nosy: ezio.melotti, haypo, pnugues
priority: normal
severity: normal
status: open
title: Sorting with locale does not work properly with Python3 on Macos
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

[issue23086] Add start and stop parameters to the Sequence.index() ABC mixin method

[Devin Jeanpierre]

Devin Jeanpierre added the comment:

Are you sure? I noticed that __iter__ went out of its way to avoid calling 
len().

--

___
Python tracker 

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

[issue23194] Antigravity prints osascript errors in OS X Yosemite

[Ned Deily]

Ned Deily added the comment:

P.S. See https://discussions.apple.com/thread/4355847?start=0&tstart=0

--

___
Python tracker 

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

[issue23194] Antigravity prints osascript errors in OS X Yosemite

[Ned Deily]

Ned Deily added the comment:

The solution is to either remove or update /Library/ScriptingAdditions/Adobe 
Unit Types.osax/Contents/MacOS/Adobe Unit.

--
resolution:  -> third party
stage:  -> resolved
status: open -> closed

___
Python tracker 

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

[issue23194] Antigravity prints osascript errors in OS X Yosemite

[Ned Deily]

Ned Deily added the comment:

My guess is that you have an older 32-bit-only Scripting Addition from Adobe 
installed.  This has nothing to do with Python.

--

___
Python tracker 

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

[issue23194] Antigravity prints osascript errors in OS X Yosemite

[Ezio Melotti]

Ezio Melotti added the comment:

Does anything change if you use open/open_new/open_new_tab, and/or use 
different urls (http and https)?

--
nosy: +hynek, ned.deily, ronaldoussoren

___
Python tracker 

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

[issue23194] Antigravity prints osascript errors in OS X Yosemite

[Jim Kubicek]

Jim Kubicek added the comment:

No, the behavior is the same in all cases

--

___
Python tracker 

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

[issue23194] Antigravity prints osascript errors in OS X Yosemite

[Jim Kubicek]

Jim Kubicek added the comment:

I do. I was just coming back here to post that very thing.

--

___
Python tracker 

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

[issue23194] Antigravity prints osascript errors in OS X Yosemite

[Ezio Melotti]

Ezio Melotti added the comment:

Do you see the same messages if you use the webbrowser module directly?

--
components: +Library (Lib) -Extension Modules
nosy: +ezio.melotti

___
Python tracker 

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

[issue23194] Antigravity prints osascript errors in OS X Yosemite

[Jim Kubicek]

New submission from Jim Kubicek:

Python 3.4.2 (default, Dec 29 2014, 14:03:16) 
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import antigravity
2015-01-08 10:45:03.771 osascript[47250:12135049] Error loading 
/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit 
Types:  dlopen(/Library/ScriptingAdditions/Adobe Unit 
Types.osax/Contents/MacOS/Adobe Unit Types, 262): no suitable image found.  Did 
find:
/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe 
Unit Types: no matching architecture in universal wrapper
osascript: OpenScripting.framework - scripting addition 
"/Library/ScriptingAdditions/Adobe Unit Types.osax" declares no loadable 
handlers.

The import command appears to work correctly (the proper XKCD opens), so I 
think this issue is just cosmetic.

--
components: Extension Modules
messages: 233676
nosy: jkubicek
priority: normal
severity: normal
status: open
title: Antigravity prints osascript errors in OS X Yosemite
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

[issue22411] Embedding Python on Windows

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
nosy: +steve.dower, tim.golden, zach.ware

___
Python tracker 

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

[issue22411] Embedding Python on Windows

[Rickard Englund]

Rickard Englund added the comment:

I have also had this problem. 
The way I solved it was to undef _DEBUG before including python and then 
redefine it again:

#undef _DEBUG //Prevent linking debug build of python
#include 
#define _DEBUG 1

This is just a hack though and it would be interesting to know if there is a 
correct way to do it.

--
nosy: +r-englund

___
Python tracker 

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

[issue23187] Segmentation fault, possibly asyncio related

[Rickard Englund]

Changes by Rickard Englund :


--
nosy: +r-englund

___
Python tracker 

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

[issue23185] add inf and nan to math module

[Mark Dickinson]

Mark Dickinson added the comment:

New patch, addressing review comments.

--
Added file: http://bugs.python.org/file37647/math_inf_nan4.patch

___
Python tracker 

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

[issue23192] Generator return value ignored in lambda function

[Chris Angelico]

Chris Angelico added the comment:

I'm not sure what to look for in the code generation. In compile.c lines 3456 
and following, there's a LOAD_CONST None coming through, in the else branch of 
"if (e->v.Yield.value)", but nothing talking about lambda functions. There are 
constants COMPILER_SCOPE_LAMBDA and COMPILER_SCOPE_FUNCTION, but the only place 
where they're used is compiler_set_qualname() and I can't see anything obvious 
there. Hopefully someone more familiar with the code internals will be able to 
figure this out!

--

___
Python tracker 

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

[issue23193] Please support "numeric_owner" in tarfile

[STINNER Victor]

STINNER Victor added the comment:

"(...) if there is a chance that this patch goes in I'm happy to write the 
required test (mocking os.chown()) for this to go in."

We don't accept changes without test. So you must write a test.

Implementing the feature in Python makes sense.

--
nosy: +haypo

___
Python tracker 

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

[issue22919] Update PCBuild for VS 2015

[Steve Dower]

Steve Dower added the comment:

Just emailed Jeremy about the buildbot. It looks like the last time tests were 
run something didn't clean up properly and left the build output locked. 
There's nothing wrong with the project files.

--

___
Python tracker 

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

[issue23119] Remove unicode specialization from set objects

[Ezio Melotti]

Ezio Melotti added the comment:

Without changesets information (not included in the git format) rietveld will 
try to apply the patch on default and if it applies clearly it will work, so 
creating the patch against an up to date py3 clone should work even with the 
git format.

--

___
Python tracker 

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

[issue23119] Remove unicode specialization from set objects

[STINNER Victor]

STINNER Victor added the comment:

@Raymond: Please disable git format for patches, because Rietveld doesn't 
support such patch and so we don't get the "review" button.

--
nosy: +haypo

___
Python tracker 

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

[issue23192] Generator return value ignored in lambda function

[STINNER Victor]

Changes by STINNER Victor :


--
nosy: +haypo

___
Python tracker 

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

[issue23192] Generator return value ignored in lambda function

[Guido van Rossum]

Guido van Rossum added the comment:

Hm, looks like nobody bothered to update the lambda code generation to use the 
value from yield. I almost feel like there is some unnecessary check "if we are 
in a lambda" in the code generation for yield. Have you looked through the code 
generation yet?

--

___
Python tracker 

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

[issue23119] Remove unicode specialization from set objects

[Ezio Melotti]

Changes by Ezio Melotti :


--
nosy: +ezio.melotti

___
Python tracker 

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

[issue23189] Set docstrings to empty string when optimizing with -OO.

[Barry A. Warsaw]

Barry A. Warsaw added the comment:

That's a backward compatibility break since existing code may be expecting 
None.  At least it needs to be carefully considered, and should have no 
possibility of be applied to anything before Python 3.5.

--
nosy: +barry
versions:  -Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.6

___
Python tracker 

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

[issue23119] Remove unicode specialization from set objects

[Marc-Andre Lemburg]

Marc-Andre Lemburg added the comment:

On 08.01.2015 15:46, Serhiy Storchaka wrote:
> 
>> Sets of strings are very common when trying to create a unique set of 
>> strings or optimizing "name in set_of_names" lookups.
> 
> This is not nearly so common as attributes or globals access, or passing 
> keyword arguments.

Not at the interpreter level, but unlike dicts, sets are not used
much to implement interpreter logic. Their use cases are more based
in application code where you basically find two major use cases:

1. check for flag in set of numeric codes

2. check for string in unique set of strings

(and their associated set operations, i.e. checking for subsets,
superset, etc.)

This is why I don't follow Raymond's reasoning. Of course, if
he comes up with a patch that makes both cases faster, I'd be
+1 ;-)

--

___
Python tracker 

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

[issue23192] Generator return value ignored in lambda function

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
nosy: +benjamin.peterson, gvanrossum, serhiy.storchaka

___
Python tracker 

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

[issue22906] PEP 479: Change StopIteration handling inside generators

[Chris Angelico]

Chris Angelico added the comment:

Okay! I think I have something here. DEFINITELY needs more eyeballs, but all 
tests pass, including a new one that tests StopIteration leakage both with and 
without the __future__ directive. Some docs changes have been made (I grepped 
for 'stopiteration' and 'generator' case insensitively, and changed anything 
that caught my eye). It'd be nice if the entire test suite and standard library 
could be guaranteed to work in a post-3.7 world, but I don't know of an easy 
way to do that, short of peppering the code with unnecessary __future__ 
directives.

--
Added file: http://bugs.python.org/file37646/pep0479.patch

___
Python tracker 

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

[issue23193] Please support "numeric_owner" in tarfile

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
nosy: +lars.gustaebel, serhiy.storchaka
stage:  -> patch review
versions: +Python 3.5

___
Python tracker 

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

[issue23119] Remove unicode specialization from set objects

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

> Sets of strings are very common when trying to create a unique set of strings 
> or optimizing "name in set_of_names" lookups.

This is not nearly so common as attributes or globals access, or passing 
keyword arguments.

--

___
Python tracker 

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

[issue23193] Please support "numeric_owner" in tarfile

[Michael Vogt]

New submission from Michael Vogt:

Please consider adding a option to extract a tarfile with the uid/gid instead 
of the lookup for uname/gname in the tarheader (i.e. what tar --numeric-owner 
provides).

One use-case is if you unpack a chroot tarfile that contains a 
/etc/{passwd,group} file with different uid/gid for user/groups like zope that 
may be present in both host and chroot but have different numbers. With the 
current approach files owned by this user will get the host uid/gid instead of 
the uid/gid of the chroot.

Attached is a patch to outline what I have in mind - if there is a chance that 
this patch goes in I'm happy to write the required test (mocking os.chown()) 
for this to go in.

Thanks for your consideration,
 Michael

--
components: Library (Lib)
files: tarfile-numeric-owner.diff
keywords: patch
messages: 233663
nosy: mvo
priority: normal
severity: normal
status: open
title: Please support "numeric_owner" in tarfile
type: enhancement
Added file: http://bugs.python.org/file37645/tarfile-numeric-owner.diff

___
Python tracker 

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

[issue23192] Generator return value ignored in lambda function

[Chris Angelico]

Changes by Chris Angelico :


--
type:  -> behavior

___
Python tracker 

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

[issue23192] Generator return value ignored in lambda function

[Chris Angelico]

New submission from Chris Angelico:

As yield is an expression, it's legal in a lambda function, which then
means you have a generator function. But it's not quite the same as
the equivalent function made with def:

$ python3
Python 3.5.0a0 (default:1c51f1650c42+, Dec 29 2014, 02:29:06)
[GCC 4.7.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> f=lambda: (yield 5)
>>> x=f()
>>> next(x)
5
>>> x.send(123)
Traceback (most recent call last):
  File "", line 1, in 
StopIteration
>>> def f(): return (yield 5)
...
>>> x=f()
>>> next(x)
5
>>> x.send(123)
Traceback (most recent call last):
  File "", line 1, in 
StopIteration: 123
>>> x = (lambda: print((yield 1)) or 2)()
>>> next(x)
1
>>> x.send(3)
3
Traceback (most recent call last):
  File "", line 1, in 
StopIteration

The last example demonstrates that send() is working, but the return value is 
not getting propagated. Disassembly shows this:

>>> dis.dis(lambda: (yield 5))
  1   0 LOAD_CONST   1 (5)
  3 YIELD_VALUE
  4 POP_TOP
  5 LOAD_CONST   0 (None)
  8 RETURN_VALUE
>>> def f(): return (yield 5)
... 
>>> dis.dis(f)
  1   0 LOAD_CONST   1 (5)
  3 YIELD_VALUE
  4 RETURN_VALUE

I'm sure this is a bug that will affect very approximately zero people, but 
it's still a peculiar inconsistency!

Verified with 3.5 and 3.4.

--
components: Interpreter Core
messages: 233662
nosy: Rosuav
priority: normal
severity: normal
status: open
title: Generator return value ignored in lambda function
versions: Python 3.4, Python 3.5

___
Python tracker 

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

[issue15955] gzip, bz2, lzma: add option to limit output size

[Martin Panter]

Martin Panter added the comment:

It turns out that GzipFile.read() etc is also susceptible to 
decompression bombing. Here is a patch to test and fix that, making use of the 
existing “max_length” parameter in the “zlib” module.

--
Added file: http://bugs.python.org/file37644/gzip-bomb.patch

___
Python tracker 

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

[issue23119] Remove unicode specialization from set objects

[Marc-Andre Lemburg]

Marc-Andre Lemburg added the comment:

I'm not sure I follow:

Sets of strings are very common when trying to create a unique set of strings 
or optimizing "name in set_of_names" lookups.

Regarding your benchmark numbers: I have a hard time following how they work. A 
simply "word in set_of_one_word" certainly doesn't make a good benchmark for 
these sort of tests :-)

You should at least test with sets of various sizes and include the 
non-matching checks as well.

--
nosy: +lemburg

___
Python tracker 

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

[issue23191] fnmatch regex cache use is not threadsafe

[M. Schmitzer]

M. Schmitzer added the comment:

@serhiy.storchaka: My thoughts exactly, especially regarding the caching being 
implicit. From the outside, fnmatch really doesn't look like it could have 
threading issues.
The patch also looks exactly like what I had in mind.

--

___
Python tracker 

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

[issue23119] Remove unicode specialization from set objects

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

+1 for removing unicode specialization. Dictionaries with string keys is a part 
of the language, but sets of strings are not special.

--
nosy: +serhiy.storchaka

___
Python tracker 

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

[issue23188] Exception chaining should trigger for non-normalised exceptions

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

_PyErr_ChainExceptions() was added because exceptions raised in C code are not 
implicitly chained. The code for explicit chaining is error prone, so it was 
extracted in separate function. Even with _PyErr_ChainExceptions() chaining 
exceptions look complex. May be implicit chaining all exceptions would be 
better.

--
nosy: +serhiy.storchaka

___
Python tracker 

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

[issue23191] fnmatch regex cache use is not threadsafe

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

It is easy to make fnmatch caching thread safe without locks. Here is a patch.

The problem with fnmatch is that the caching is implicit and a user don't know 
that any lock are needed. So either the need of the lock should be explicitly 
documented, or fnmatch should be made thread safe. The second option looks more 
preferable to me.

In 3.x fnmatch is thread safe because thread safe lru_cache is used.

--
keywords: +patch
nosy: +serhiy.storchaka
stage:  -> patch review
Added file: http://bugs.python.org/file37643/fnmatch_threadsafe.patch

___
Python tracker 

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

[issue23191] fnmatch regex cache use is not threadsafe

[STINNER Victor]

STINNER Victor added the comment:

It would be nice to fix the issue, but I don't know how it is handled in other 
stdlib modules.

--

___
Python tracker 

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

[issue23191] fnmatch regex cache use is not threadsafe

[M. Schmitzer]

M. Schmitzer added the comment:

Ok, if that is the attitude in such cases, feel free to close this.

--

___
Python tracker 

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

[issue23152] fstat64 required on Windows

[Steve Dower]

Steve Dower added the comment:

I prefer your patch too. (I've posted on the other thread about the build 
problems, and I'll test this when I get a chance.)

--

___
Python tracker 

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

[issue22919] Update PCBuild for VS 2015

[Steve Dower]

Steve Dower added the comment:

You will need Windows 7 *SP1*, as I don't think VS will run without the 
updates. There is also a service pack for VS 2010 that may enable opening the 
newer solution - it certainly worked for me.

We decided not to keep the old project files as they weren't being maintained.

Community edition is free, but you need a Microsoft account (also free) to 
register it. I don't know why this is necessary, but that's the way they set it 
up.

I'll check out that buildbot when I get a chance (Trent's one is known to be 
busted). The stable buildbots and the one with VS 2015 were doing fine last 
time I looked.

I haven't tried with the SDK compilers, but it should be possible to build with 
them now. VS is no longer required to build from the command line.

--

___
Python tracker 

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

[issue23191] fnmatch regex cache use is not threadsafe

[STINNER Victor]

STINNER Victor added the comment:

I guess that a lot of stdlib modules are not thread safe :-/ A workaround is to 
protect calls to fnmatch with your own lock.

--
nosy: +haypo

___
Python tracker 

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

[issue23191] fnmatch regex cache use is not threadsafe

[M. Schmitzer]

New submission from M. Schmitzer:

The way the fnmatch module uses its regex cache is not threadsafe. When 
multiple threads use the module in parallel, a race condition between 
retrieving a - presumed present - item from the cache and clearing the cache 
(because the maximum size has been reached) can lead to KeyError being raised.

The attached script demonstrates the problem. Running it will (eventually) 
yield errors like the following.

Exception in thread Thread-10:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
self.run()
  File "/usr/lib/python2.7/threading.py", line 763, in run
self.__target(*self.__args, **self.__kwargs)
  File "fnmatch_thread.py", line 12, in run
fnmatch.fnmatchcase(name, pat)
  File "/home/marc/.venv/modern/lib/python2.7/fnmatch.py", line 79, in 
fnmatchcase
return _cache[pat].match(name) is not None
KeyError: 'lYwrOCJtLU'

--
components: Library (Lib)
files: fnmatch_thread.py
messages: 233650
nosy: mschmitzer
priority: normal
severity: normal
status: open
title: fnmatch regex cache use is not threadsafe
type: crash
versions: Python 2.7
Added file: http://bugs.python.org/file37642/fnmatch_thread.py

___
Python tracker 

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

[issue7676] IDLE shell shouldn't use TABs

[Al Sweigart]

Changes by Al Sweigart :


--
nosy: +Al.Sweigart

___
Python tracker 

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

[issue23190] OpenSSL fails building with build.bat

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
resolution:  -> rejected
status: open -> closed

___
Python tracker 

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

[issue23190] OpenSSL fails building with build.bat

[Antoine Pitrou]

Antoine Pitrou added the comment:

Hmm, probably the svn export had failed for some reason. I deleted the OpenSSL 
directory, re-ran get_externals.bat and then everything went fine.

--

___
Python tracker 

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

[issue22919] Update PCBuild for VS 2015

[Mark Lawrence]

Mark Lawrence added the comment:

@Victor I don't know what version you need for Windows 7 or earlier but I can 
tell you that VS 2013 Community edition is *NOT* free, I fell into that trap 
myself, you need the Express edition.

--

___
Python tracker 

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

[issue23190] OpenSSL fails building with build.bat

[Antoine Pitrou]

Antoine Pitrou added the comment:

Z:\cpython\default>dir Z:\cpython\default\externals\openssl-1.0.1j\
 Volume in drive Z is antoine
 Volume Serial Number is 2FA8-F31C

 Directory of Z:\cpython\default\externals\openssl-1.0.1j

01/08/2015  11:59 AM  .
01/08/2015  12:10 PM  ..
01/08/2015  11:59 AM  tmp32
   0 File(s)  0 bytes
   3 Dir(s)  49,764,913,152 bytes free

Z:\cpython\default>dir Z:\cpython\default\externals\openssl-1.0.1j\tmp32
 Volume in drive Z is antoine
 Volume Serial Number is 2FA8-F31C

 Directory of Z:\cpython\default\externals\openssl-1.0.1j\tmp32

01/08/2015  11:59 AM  .
01/08/2015  11:59 AM  ..
01/08/2015  11:59 AM  ssleay
01/08/2015  12:17 PM  libeay
   0 File(s)  0 bytes
   4 Dir(s)  49,764,913,152 bytes free

--

___
Python tracker 

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

[issue23190] OpenSSL fails building with build.bat

[Antoine Pitrou]

New submission from Antoine Pitrou:

With "PCbuild\build.bat -d -e", OpenSSL fails building:

  nasm: fatal: unable to open input file `Z:\cpython\default\externals\openssl-
  1.0.1j\tmp32\aes-586.asm'

Detailed build log is:

"Z:\cpython\default\PCbuild\libeay.vcxproj" (default target) (32:3) ->
(BuildNasmFiles target) -> 
  Z:\cpython\default\PCbuild\openssl.props(61,5): error MSB3073: The command 
"setlocal [Z:\cpython\default\PCbuild\libeay.vcxproj]
Z:\cpython\default\PCbuild\openssl.props(61,5): error MSB3073: set 
PATH=%PATH%;Z:\cpython\default\externals\\nasm-2.11.06\ 
[Z:\cpython\default\PCbuild\libeay.vcxproj]
Z:\cpython\default\PCbuild\openssl.props(61,5): error MSB3073: nasm.exe -f 
win32 -o "Z:\cpython\default\externals\openssl-1.0.1j\tmp32\libeay\aes-586.obj" 
"Z:\cpython\default\externals\openssl-1.0.1j\tmp32\aes-586.asm"" exited with 
code 1. [Z:\cpython\default\PCbuild\libeay.vcxproj]

"Z:\cpython\default\PCbuild\pcbuild.proj" (Rebuild target) (1) ->
"Z:\cpython\default\PCbuild\_ssl.vcxproj" (Build target) (31:2) ->
"Z:\cpython\default\PCbuild\ssleay.vcxproj" (default target) (33:3) ->
(ClCompile target) -> 
  c1 : fatal error C1083: Cannot open source file: 
'Z:\cpython\default\externals\openssl-1.0.1j\ssl\d1_both.c': No such file or 
directory [Z:\cpython\default\PCbuild\ssleay.vcxproj]

[etc.]


It seems there are problems with how the file paths are computed? Also, I have 
no file "aes-586.asm", how is it supposed to be generated?

--
components: Build, Windows
messages: 233646
nosy: pitrou, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: OpenSSL fails building with build.bat
type: behavior
versions: Python 3.5

___
Python tracker 

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

[issue22906] PEP 479: Change StopIteration handling inside generators

[Chris Angelico]

Chris Angelico added the comment:

Nick, any particular reason for pointing to 
https://hg.python.org/cpython/annotate/bbf16fd024df/Lib/__future__.py rather 
than https://hg.python.org/cpython/annotate/tip/Lib/__future__.py ? I'm looking 
at both, anyhow.

--

___
Python tracker 

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

[issue22919] Update PCBuild for VS 2015

[STINNER Victor]

STINNER Victor added the comment:

> Visual Studio 2013 Professional works fine under Windows 7 SP1 here.

Ok, good to know. But is it correct that the free version of VS 2013 
(community) requires Windows 8.1 or newer? It's not cool to require to upgrade 
Windows to being able to freely compile Python.

My MSDN account is probably outdated, I don't think that I have access to the 
Professional version.

Would it be possible to build Python with the light Windows SDK which basically 
only includes the C compiler and the CRT?

--

___
Python tracker 

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

[issue22919] Update PCBuild for VS 2015

[Antoine Pitrou]

Antoine Pitrou added the comment:

Visual Studio 2013 Professional works fine under Windows 7 SP1 here.

--
nosy: +pitrou

___
Python tracker 

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

[issue19102] Add tests for CLI of the tabnanny module

[Al Sweigart]

Al Sweigart added the comment:

Since tabnanny is also a module in the standard library (it is imported by the 
idle code), wouldn't moving it to lib/test/test_tools make it un-importable? 
This would be a good case for leaving it where it is.

--
nosy: +Al.Sweigart

___
Python tracker 

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

[issue22919] Update PCBuild for VS 2015

[STINNER Victor]

STINNER Victor added the comment:

Oh by the way, 2 Windows buildbot slaves are no more able to compile Python. I 
don't know if it's related to this issue or not.


Builder "AMD64 Windows7 SP1 3.x", owned by Jeremy Kloth:
http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.x

2>LINK : fatal error LNK1104: cannot open file 
'C:\buildbot.python.org\3.x.kloth-win64\build\PCBuild\amd64\python35_d.dll' 
[C:\buildbot.python.org\3.x.kloth-win64\build\PCbuild\pythoncore.vcxproj]


Builder "x86 Windows Server 2003 [SB] 3.x" managed by Snakebite.org (trent):
http://buildbot.python.org/all/builders/x86%20Windows%20Server%202003%20%5BSB%5D%203.x

E:\Data\buildslave\cpython\3.x.snakebite-win2k3r2sp2-x86\build\Tools\buildbot\..\..\build\TEEB4C~1
 - The process cannot access the file because it is being used by another 
process.
(...)
 
2>E:\Data\buildslave\cpython\3.x.snakebite-win2k3r2sp2-x86\build\PCbuild\pythoncore.vcxproj(415,5):
 warning : Toolset v100 is not used for official builds. Your build may have 
errors or incompatibilities.
(...)
 C:\Program 
Files\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32\Microsoft.Cpp.Win32.Targets(147,5):
 error MSB6006: "CL.exe" exited with code 128. 
[E:\Data\buildslave\cpython\3.x.snakebite-win2k3r2sp2-x86\build\PCbuild\pythoncore.vcxproj]


Both slaves are part of the group of "3.x stable" buildbots :-(

--

___
Python tracker 

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

[issue22906] PEP 479: Change StopIteration handling inside generators

[Chris Angelico]

Changes by Chris Angelico :


Added file: http://bugs.python.org/file37641/stopiter.py

___
Python tracker 

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

[issue22906] PEP 479: Change StopIteration handling inside generators

[Chris Angelico]

Chris Angelico added the comment:

PyErr_Restore doesn't seem to trigger exception chaining. But thanks for the 
tip about explicitly setting the traceback; not sure how I missed that, but now 
the StopIteration traceback is visible.

Minor point: The previous patch was setting the __context__ of the 
RuntimeError, whereas it ought to have been setting __cause__. Have corrected 
that.

So here, before I move further forward, is a new POC patch; I've removed the 
patches that rhettinger applied already, and fixed up tracebacks. So now it's a 
better-behaved POC, at least.

--
Added file: http://bugs.python.org/file37640/pep0479.patch

___
Python tracker 

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