[issue40937] Remove deprecated functions marked for removal in 3.10

[Rémi Lapeyre]

Change by Rémi Lapeyre :


--
nosy: +serhiy.storchaka

___
Python tracker 

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

[issue40946] SuppressCrashReport should set SEM_FAILCRITICALERRORS in Windows

[Eryk Sun]

Change by Eryk Sun :


--
keywords: +easy

___
Python tracker 

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

[issue40946] SuppressCrashReport should set SEM_FAILCRITICALERRORS in Windows

[Eryk Sun]

New submission from Eryk Sun :

In test.support, suppress_msvcrt_asserts sets the process error mode to include 
SEM_FAILCRITICALERRORS, SEM_NOGPFAULTERRORBOX, SEM_NOALIGNMENTFAULTEXCEPT, and 
SEM_NOOPENFILEERRORBOX. In contrast, the SuppressCrashReport context manager in 
the same module only sets SEM_NOGPFAULTERRORBOX. It should also set 
SEM_FAILCRITICALERRORS (i.e. do not display the critical-error-handler message 
box).

Including SEM_NOOPENFILEERRORBOX wouldn't hurt, but it's not of much value 
since it only affects the deprecated OpenFile function. 
SEM_NOALIGNMENTFAULTEXCEPT may not be appropriate in a context manager, since 
it's a one-time setting that can't be reverted, plus x86 and x64 processors 
aren't even configured by default to generate alignment exceptions; they do 
fixups in hardware.

---
Discussion

SEM_FAILCRITICALERRORS suppresses normal "hard error" reports sent by the 
NtRaiseHardError system call -- or by ExRaiseHardError or IoRaiseHardError in 
the kernel. If reporting a hard error isn't prevented by the error mode, the 
report gets sent to the ExceptionPort of the process. Normally this is the 
session's API port (e.g. "\Sessions\1\Windows\ApiPort"). A thread in the 
session server process (csrss.exe) handles requests sent to this port. In the 
case of a hard error, ultimately it creates a message box via 
user32!MessageBoxTimeoutW.

For example:

NtRaiseHardError = ctypes.windll.ntdll.NtRaiseHardError
response = (ctypes.c_ulong * 1)()

With the default process error mode, the following raises a hard error dialog 
for STATUS_UNSUCCESSFUL (0xC001), with abort/retry/ignore options:

>>> NtRaiseHardError(0xC000_0001, 0, 0, None, 0, response)
0
>>> response[0]
2

The normal response value for the above call is limited to abort (2), retry 
(7), and ignore (4). The response is 0 if the process is set to fail critical 
errors: 

>>> msvcrt.SetErrorMode(msvcrt.SEM_FAILCRITICALERRORS)
0
>>> NtRaiseHardError(0xC000_0001, 0, 0, None, 0, response)
0
>>> response[0]
0

SEM_FAILCRITICALERRORS doesn't suppress all hard-error reporting. The system 
also checks for an override flag (0x1000_) in the status code. This flag is 
used in many cases, such as WinAPI FatalAppExitW. For example, the following 
will report a hard error regardless of the process error mode:

>>> NtRaiseHardError(0xC000_0001 | 0x1000_, 0, 0, None, 0, response)
0
>>> response[0]
2

A common case that doesn't use the override flag is when the loader fails to 
initialize a process.

For the release build of Python 3.10, for example, if "python310.dll" can't be 
found, the loader tries to raise a hard error with the status code 
STATUS_DLL_NOT_FOUND (0xC135). If the process error mode allows this, the 
NtRaiseHardError system call won't return until the user clicks on the "OK" 
button.

>>> os.rename('amd64/python310.dll', 'amd64/python310.dll.bak')
>>> # the following returns after clicking OK
>>> hex(subprocess.call('python'))
'0xc135'

With SEM_FAILCRITICALERRORS set, which by default gets inherited by a child 
process, sending the hard error report is suppressed (i.e. NtRaiseHardError 
returns immediately with a response of 0), and the failed child process 
terminates immediately with the status code STATUS_DLL_NOT_FOUND.

>>> msvcrt.SetErrorMode(msvcrt.SEM_FAILCRITICALERRORS)
0
>>> # the following returns immediately
>>> hex(subprocess.call('python'))
'0xc135'

--
messages: 371257
nosy: eryksun
priority: normal
severity: normal
stage: needs patch
status: open
title: SuppressCrashReport should set SEM_FAILCRITICALERRORS in Windows
type: enhancement
versions: Python 3.10

___
Python tracker 

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

[issue40275] test.support has way too many imports

[hai shi]

Change by hai shi :


--
pull_requests: +19993
pull_request: https://github.com/python/cpython/pull/20797

___
Python tracker 

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

[issue31082] reduce takes iterable, not just sequence

[Zackery Spytz]

Change by Zackery Spytz :


--
keywords: +patch
nosy: +ZackerySpytz
nosy_count: 6.0 -> 7.0
pull_requests: +19992
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/20796

___
Python tracker 

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

[issue40924] Recent importlib change breaks most recent certifi == 2020.4.5.2

[Jason R. Coombs]

Jason R. Coombs  added the comment:

Thanks for the thorough and considerate response.

I do think your original recommendation of reverting the broken feature is the 
best approach at this point. That is, keep resources.files with the fallback 
shim and eliminate support for loaders supplying that behavior. That will avoid 
users relying on that protocol but enable the files feature for Source and Zip 
importers.

That will buy time for the remaining functionality, mainly the provider 
interface, to mature and possibly evolve further, for eventual adoption in a 
future Python release.

Some planning will need to be dialed back, but I don’t have confidence in the 
implementation to say that it’s the best one. Better to defer that effort.

I’ll put together a patch for 3.9 to remove the loader support (backward 
incompatible with b1/2 but compatible with 3.8 but only for custom loaders), 
and put together a hot fix for master so it’s no longer broken.

--

___
Python tracker 

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

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

[miss-islington]

miss-islington  added the comment:


New changeset e3ce3bba9277a7c4cfde5aaf6269b6c68f334176 by Miss Islington (bot) 
in branch '3.9':
bpo-40847: Consider a line with only a LINECONT a blank line (GH-20769)
https://github.com/python/cpython/commit/e3ce3bba9277a7c4cfde5aaf6269b6c68f334176


--

___
Python tracker 

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

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

[Pablo Galindo Salgado]

Change by Pablo Galindo Salgado :


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

___
Python tracker 

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

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

[miss-islington]

Change by miss-islington :


--
nosy: +miss-islington
nosy_count: 7.0 -> 8.0
pull_requests: +19991
pull_request: https://github.com/python/cpython/pull/20795

___
Python tracker 

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

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:


New changeset 896f4cf63f9ab93e30572d879a5719d5aa2499fb by Lysandros Nikolaou in 
branch 'master':
bpo-40847: Consider a line with only a LINECONT a blank line (GH-20769)
https://github.com/python/cpython/commit/896f4cf63f9ab93e30572d879a5719d5aa2499fb


--

___
Python tracker 

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

[issue40275] test.support has way too many imports

[STINNER Victor]

STINNER Victor  added the comment:


New changeset 7f888c7ef905842bf7739cc03bd20398329951b5 by Hai Shi in branch 
'master':
bpo-40275: Add import_helper submodule in test.support (GH-20794)
https://github.com/python/cpython/commit/7f888c7ef905842bf7739cc03bd20398329951b5


--

___
Python tracker 

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

[issue40924] Recent importlib change breaks most recent certifi == 2020.4.5.2

[Łukasz Langa]

Łukasz Langa  added the comment:

I thought about this all day. Given the scope of the change you made I think no 
option looks ideal. If we revert the entire feature, it's a big bummer for 
everybody involved and it might be an overreaction. If we keep the feature at 
the state of Beta 1, it might become a maintenance nightmare for third-party 
users. If we agree to a the big change you now see necessary, we are 
reintroducing the same risk that I highlighted in previous comments.

Please note that this is in no way intended to make you feel terrible. Don't 
beat yourself up about it. Now, think as the core developer you are: if you are 
100% sure the change is worth pushing to 3.9, the best course of action at this 
point seems to be: find a champion within core who will work with you to 
quickly reassess the situation and give us an action plan as a team. 

Say, Barry seems like the perfect candidate. If such champion shares your 
opinion about it being important for 3.9, and is willing to work with you on 
finishing what you need changing (incl. review), *and* to ensure the existing 
users of importlib.resources don't see any breakage not documented as of Beta 
1, then we can talk about an exceptional late inclusion in 3.9.

--

___
Python tracker 

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

[issue40878] Use c99 on the aixtools bot

[Stefan Krah]

Stefan Krah  added the comment:

So it would still be interesting to see what happens if you compile
libmpdec with c99_r (emphasis mine):


"""
This command supports all ISO
C99 language features, but does
not support IBM language
extensions. Use this invocation for
*strict* conformance to the C99
standard.
"""

--

___
Python tracker 

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

[issue40878] Use c99 on the aixtools bot

[Stefan Krah]

Stefan Krah  added the comment:

Thanks for this information. The buildbot, however, fails to compile
C99 extern inline functions. Example:

ld: 0711-317 ERROR: Undefined symbol: .mpd_issnan


I understand the C99 extern inline feature like in this explanation:

https://www.greenend.org.uk/rjk/tech/inline.html


"""
In this example, one of the declarations does not mention inline:

// a declaration not mentioning inline
int max(int a, int b);

// a definition mentioning inline
inline int max(int a, int b) {
  return a > b ? a : b;
}

In either example, the function will be callable from other files.
"""



This is the scheme that libmpdec uses and that compilers understood
at the time I wrote it.

--

___
Python tracker 

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

[issue29847] Path takes and ignores **kwargs

[Rémi Lapeyre]

Change by Rémi Lapeyre :


--
versions: +Python 3.10, Python 3.8, Python 3.9

___
Python tracker 

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

[issue39385] Add an assertNoLogs context manager to unittest TestCase

[Rémi Lapeyre]

Change by Rémi Lapeyre :


--
versions: +Python 3.10 -Python 3.9

___
Python tracker 

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

[issue40902] Speed up PEG parser by using operator precedence for binary operators

[Pablo Galindo Salgado]

Change by Pablo Galindo Salgado :


--
resolution:  -> postponed

___
Python tracker 

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

[issue40902] Speed up PEG parser by using operator precedence for binary operators

[Pablo Galindo Salgado]

Change by Pablo Galindo Salgado :


--
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

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

[issue40680] thread_cputime isn't supported by AIX5

[STINNER Victor]

STINNER Victor  added the comment:

According to 
https://www.ibm.com/support/pages/aix-support-lifecycle-information I suggest 
to require AIX 7.1 and newer.

--

___
Python tracker 

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

[issue40680] thread_cputime isn't supported by AIX5

[STINNER Victor]

STINNER Victor  added the comment:

AIX 5 was released 16 years ago, do you we really care?

--

___
Python tracker 

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

[issue40275] test.support has way too many imports

[hai shi]

Change by hai shi :


--
pull_requests: +19990
pull_request: https://github.com/python/cpython/pull/20794

___
Python tracker 

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

[issue30064] BaseSelectorEventLoop.sock_{recv, sendall}() don't remove their callbacks when canceled

[Fantix King]

Fantix King  added the comment:

I'm checking now

--

___
Python tracker 

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

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

[Antoine Pitrou]

Change by Antoine Pitrou :


--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
type:  -> behavior
versions: +Python 3.7, Python 3.8, Python 3.9

___
Python tracker 

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

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

[miss-islington]

miss-islington  added the comment:


New changeset 972aba86ede0bf254e16a760639a1ff8df298578 by Antoine Pitrou in 
branch '3.8':
[3.8] bpo-40895: Update weakref documentation to remove old warnings (GH-20687) 
(GH-20792)
https://github.com/python/cpython/commit/972aba86ede0bf254e16a760639a1ff8df298578


--

___
Python tracker 

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

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

[miss-islington]

miss-islington  added the comment:


New changeset 049039832da3d02592d680cebf71ab8a665a6564 by Antoine Pitrou in 
branch '3.7':
[3.7] bpo-40895: Update weakref documentation to remove old warnings (GH-20687) 
(GH-20793)
https://github.com/python/cpython/commit/049039832da3d02592d680cebf71ab8a665a6564


--

___
Python tracker 

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

[issue40680] thread_cputime isn't supported by AIX5

[Batuhan Taskaya]

Batuhan Taskaya  added the comment:

@vstinner what are your thoughts on this? I can propose a patch that introduces 
a build value to generate this conditionally depending on if the system has it 
or not. But I am not sure about if our motivation behind this is going to be 
supporting (very) old versions of AIX.

--
nosy: +vstinner

___
Python tracker 

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

[issue40906] Unable to import module due to python unable to resolve dependecies

[Steve Dower]

Steve Dower  added the comment:

add_dll_directory can be safely used within your library, so if you have any 
.py files that will be imported first (such as your package __init__.py), you 
can add it then. The safest way is to use something like:

with os.add_dll_directory(THE_DIR):
import the_module

As this won't leave your directory on the search path for anyone else's DLLs.

The most correct fix is to put your DLL alongside your .pyd file. But I suspect 
in your case, the DLLs can't be moved, so using the search directory is likely 
best. (Or you could put your .pyd with the DLLs and update sys.path for when 
you import it.)

Presumably in the past, you were relying on the DLLs being on the user's PATH, 
which makes your application vulnerable to DLL hijacking (malicious or 
accidental, we've seen both). Not having to worry about that is a good thing.

--

___
Python tracker 

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

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

[miss-islington]

miss-islington  added the comment:


New changeset 18e07ba931c68eb5ab5262d4e57fe58c302686de by Miss Islington (bot) 
in branch '3.9':
bpo-40895: Update weakref documentation to remove old warnings (GH-20687)
https://github.com/python/cpython/commit/18e07ba931c68eb5ab5262d4e57fe58c302686de


--

___
Python tracker 

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

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

[Antoine Pitrou]

Change by Antoine Pitrou :


--
pull_requests: +19989
pull_request: https://github.com/python/cpython/pull/20793

___
Python tracker 

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

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

[Antoine Pitrou]

Change by Antoine Pitrou :


--
nosy: +pitrou
nosy_count: 3.0 -> 4.0
pull_requests: +19988
pull_request: https://github.com/python/cpython/pull/20792

___
Python tracker 

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

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

[miss-islington]

Change by miss-islington :


--
pull_requests: +19987
pull_request: https://github.com/python/cpython/pull/20791

___
Python tracker 

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

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

[miss-islington]

miss-islington  added the comment:


New changeset 1642c0ef750f96664a98cadb09301d492098d2fb by Daniel Fortunov in 
branch 'master':
bpo-40895: Update weakref documentation to remove old warnings (GH-20687)
https://github.com/python/cpython/commit/1642c0ef750f96664a98cadb09301d492098d2fb


--
nosy: +miss-islington

___
Python tracker 

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

[issue30064] BaseSelectorEventLoop.sock_{recv, sendall}() don't remove their callbacks when canceled

[STINNER Victor]

STINNER Victor  added the comment:

Another kind of failure on x86 Gentoo Installed with X 3.x:
https://buildbot.python.org/all/#/builders/128/builds/1030

ERROR: test_sock_client_racing 
(test.test_asyncio.test_sock_lowlevel.EPollEventLoopTests)
--
Traceback (most recent call last):
  File 
"/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.installed/build/target/lib/python3.10/test/test_asyncio/test_sock_lowlevel.py",
 line 200, in _basetest_sock_send_racing
await self.loop.sock_sendall(sock, b'world')
  File 
"/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.installed/build/target/lib/python3.10/asyncio/selector_events.py",
 line 460, in sock_sendall
return await fut
asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.installed/build/target/lib/python3.10/asyncio/tasks.py",
 line 507, in wait_for
fut.result()
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File 
"/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.installed/build/target/lib/python3.10/test/test_asyncio/test_sock_lowlevel.py",
 line 256, in test_sock_client_racing
self.loop.run_until_complete(asyncio.wait_for(
  File 
"/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.installed/build/target/lib/python3.10/asyncio/base_events.py",
 line 642, in run_until_complete
return future.result()
  File 
"/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.installed/build/target/lib/python3.10/asyncio/tasks.py",
 line 509, in wait_for
raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError

--

___
Python tracker 

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

[issue40680] thread_cputime isn't supported by AIX5

[Michael Felt]

Michael Felt  added the comment:

No, it is not supported - asin there are no new patches - but there are
organizations that use it.

imho - those organizations are not likely to be using the latest Python
- but I have been packaging Python on AIX 5.3 and AIX 6.1 - as these
packages run unmodified on AIX 7.1 and AIX 7.2 (AIX binary compatibility).

FYI.

On 19/05/2020 13:57, Batuhan Taskaya wrote:
> Batuhan Taskaya  added the comment:
>
> Does AIX 5.3 officially supported by IBM? As far as I can locate, it is 
> deprecated long time ago.
>
> --
> nosy: +BTaskaya
>
> ___
> Python tracker 
> 
> ___
>

--

___
Python tracker 

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

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

[STINNER Victor]

STINNER Victor  added the comment:

> Why doesn't SuppressCrashReport suppress the hard error dialog (i.e. 
> SEM_FAILCRITICALERRORS)? This dialog gets created by the NtRaiseHardError 
> system call.

Would you mind to open a separated issue?

--

___
Python tracker 

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

[issue40878] Use c99 on the aixtools bot

[Michael Felt]

Michael Felt  added the comment:

Actually, iirc - xlc is c99 plus a few extra settings.

The configuration files for xlc are, traditionally, in /etc (the later
versions of the compiler have moved them into /opt/show/where so that
multiple versions of the compiler can be installed.

buildbot@x064:[/home/buildbot]ls -l /etc/*vac*
-rw-r--r--    1 bin  bin   37731 Aug 02 2018  /etc/vac.cfg.53
-rw-r--r--    1 bin  bin   39672 Aug 02 2018  /etc/vac.cfg.61
-rw-r--r--    1 bin  bin   39681 Aug 02 2018  /etc/vac.cfg.71
-rw-r--r--    1 bin  bin   39611 Aug 02 2018  /etc/vac.cfg.72

Herein I see that xlc is "extc99" and some extras:

* -qlanglvl=extc99 C compiler with common extensions, UNIX headers
xlc:    use    = DEFLT_C
    crt    = /lib/crt0.o
    mcrt   = /lib/mcrt0.o
    gcrt   = /lib/gcrt0.o
    libraries  = -L/usr/vac/lib,-lxlopt,-lxlipa,-lxl,-lc
    proflibs   = -L/lib/profiled,-L/usr/lib/profiled
    options    =
-qlanglvl=extc99,-qcpluscmt,-qkeyword=inline,-qalias=ansi

I have chosen the xlc_r variant - for thread_safe additions:

* standard c compiler aliased as xlc_r (61 Threads)
xlc_r:  use    = DEFLT_C
    crt    = /lib/crt0.o
    mcrt   = /lib/mcrt0.o
    gcrt   = /lib/gcrt0.o
    libraries  = -L/usr/vac/lib,-lxlopt,-lxlipa,-lxl,-lpthreads,-lc
    proflibs   = -L/lib/profiled,-L/usr/lib/profiled
    hdlibs = -L/usr/vac/lib,-lhmd
    options    =
-qlanglvl=extc99,-qcpluscmt,-qkeyword=inline,-qalias=ansi,-qthreaded,-D_THREAD_SAFE,-D__VACPP_MULTI__

So, what is c99 then? -> focus on it is 'stdc99' rather than 'extc99'

* Strict ANSI compiler, ANSI headers
c99:    use    = DEFLT_C
    crt    = /lib/crt0.o
    mcrt   = /lib/mcrt0.o
    gcrt   = /lib/gcrt0.o
    libraries  = -L/usr/vac/lib,-lxlopt,-lxlipa,-lxl,-lc
    proflibs   = -L/lib/profiled,-L/usr/lib/profiled
    options    =
-qlanglvl=stdc99,-D_ANSI_C_SOURCE,-D_ISOC99_SOURCE,-qalias=ansi,-qstrict_induction

Hope this helps clarify that both xlc and c99 are "c99" based.

Regards,

Michael

On 05/06/2020 21:34, Stefan Krah wrote:
> New submission from Stefan Krah :
>
> There appears to be an xlc buildbot with libmpdec failures.
>
> libmpdec uses C99 extern inline semantics. From the brief period that I had 
> access to xlc I remember that xlc was quite picky about C99.
>
> Actually all of Python uses C99. So I think xlc_r needs to be invoked as 
> c99_r.
>
> --
> messages: 370779
> nosy: Michael.Felt, skrah
> priority: normal
> severity: normal
> status: open
> title: Use c99 on the aixtools bot
>
> ___
> Python tracker 
> 
> ___
>

--

___
Python tracker 

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

[issue40945] TKinter.Tk.geometry(Tk.winfo_geometry()) should be idempotent

[Ben Li-Sauerwine]

Change by Ben Li-Sauerwine :


--
type:  -> behavior

___
Python tracker 

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

[issue40945] TKinter.Tk.geometry(Tk.winfo_geometry()) should be idempotent

[Ben Li-Sauerwine]

New submission from Ben Li-Sauerwine :

One would expect that calling TKinter.Tk.geometry(tk.winfo_geometry()) would be 
idempotent.  However, based on the system window frame, it is not and doing so 
moves the window down the screen.

Running the example below reproduces the issue.

--
components: Tkinter
files: tkinter_ex.py
messages: 371236
nosy: Ben Li-Sauerwine
priority: normal
severity: normal
status: open
title: TKinter.Tk.geometry(Tk.winfo_geometry()) should be idempotent
versions: Python 3.6
Added file: https://bugs.python.org/file49225/tkinter_ex.py

___
Python tracker 

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

[issue40913] time.sleep ignores errors on Windows

[Eryk Sun]

Eryk Sun  added the comment:

> is there any straightforward way to cause WaitForSingleObjectEx to fail?

The wait can fail for ERROR_INVALID_HANDLE or ERROR_ACCESS_DENIED (i.e. the 
handle lacks SYNCHRONIZE access). If _PyOS_SigintEvent were replaced with 
get/set functions, then a non-waitable handle could be set temporarily via 
ctypes.

--
nosy: +eryksun

___
Python tracker 

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

[issue40944] email.message.EmailMessage address parser fails to handle 'example@'

[Roundup Robot]

Change by Roundup Robot :


--
keywords: +patch
nosy: +python-dev
nosy_count: 3.0 -> 4.0
pull_requests: +19985
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/20790

___
Python tracker 

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

[issue40944] email.message.EmailMessage address parser fails to handle 'example@'

[Ivan Savin]

New submission from Ivan Savin :

How to reproduce:

>>> import email.message
>>> message = email.message.EmailMessage()
>>> message['From'] = 'hey@'
Traceback (most recent call last):
  File 
"/home/ivan/.pyenv/versions/3.9.0a5/lib/python3.9/email/_header_value_parser.py",
 line 1956, in get_address
token, value = get_group(value)
  File 
"/home/ivan/.pyenv/versions/3.9.0a5/lib/python3.9/email/_header_value_parser.py",
 line 1914, in get_group
raise errors.HeaderParseError("expected ':' at end of group "
email.errors.HeaderParseError: expected ':' at end of group display name but 
found '@'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/home/ivan/.pyenv/versions/3.9.0a5/lib/python3.9/email/_header_value_parser.py",
 line 1782, in get_mailbox
token, value = get_name_addr(value)
  File 
"/home/ivan/.pyenv/versions/3.9.0a5/lib/python3.9/email/_header_value_parser.py",
 line 1768, in get_name_addr
token, value = get_angle_addr(value)
  File 
"/home/ivan/.pyenv/versions/3.9.0a5/lib/python3.9/email/_header_value_parser.py",
 line 1693, in get_angle_addr
raise errors.HeaderParseError(
email.errors.HeaderParseError: expected angle-addr but found '@'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "", line 1, in 
  File "/home/ivan/.pyenv/versions/3.9.0a5/lib/python3.9/email/message.py", 
line 409, in __setitem__
self._headers.append(self.policy.header_store_parse(name, val))
  File "/home/ivan/.pyenv/versions/3.9.0a5/lib/python3.9/email/policy.py", line 
148, in header_store_parse
return (name, self.header_factory(name, value))
  File 
"/home/ivan/.pyenv/versions/3.9.0a5/lib/python3.9/email/headerregistry.py", 
line 596, in __call__
return self[name](name, value)
  File 
"/home/ivan/.pyenv/versions/3.9.0a5/lib/python3.9/email/headerregistry.py", 
line 191, in __new__
cls.parse(value, kwds)
  File 
"/home/ivan/.pyenv/versions/3.9.0a5/lib/python3.9/email/headerregistry.py", 
line 334, in parse
kwds['parse_tree'] = address_list = cls.value_parser(value)
  File 
"/home/ivan/.pyenv/versions/3.9.0a5/lib/python3.9/email/headerregistry.py", 
line 325, in value_parser
address_list, value = parser.get_address_list(value)
  File 
"/home/ivan/.pyenv/versions/3.9.0a5/lib/python3.9/email/_header_value_parser.py",
 line 1979, in get_address_list
token, value = get_address(value)
  File 
"/home/ivan/.pyenv/versions/3.9.0a5/lib/python3.9/email/_header_value_parser.py",
 line 1959, in get_address
token, value = get_mailbox(value)
  File 
"/home/ivan/.pyenv/versions/3.9.0a5/lib/python3.9/email/_header_value_parser.py",
 line 1785, in get_mailbox
token, value = get_addr_spec(value)
  File 
"/home/ivan/.pyenv/versions/3.9.0a5/lib/python3.9/email/_header_value_parser.py",
 line 1638, in get_addr_spec
token, value = get_domain(value[1:])
  File 
"/home/ivan/.pyenv/versions/3.9.0a5/lib/python3.9/email/_header_value_parser.py",
 line 1595, in get_domain
if value[0] in CFWS_LEADER:
IndexError: string index out of range

--
components: email
messages: 371234
nosy: Ivan Savin, barry, r.david.murray
priority: normal
severity: normal
status: open
title: email.message.EmailMessage address parser fails to handle 'example@'
type: behavior
versions: Python 3.9

___
Python tracker 

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

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

[Eryk Sun]

Eryk Sun  added the comment:

Why doesn't SuppressCrashReport suppress the hard error dialog (i.e. 
SEM_FAILCRITICALERRORS)? This dialog gets created by the NtRaiseHardError 
system call. For example:

>>> NtRaiseHardError = ctypes.windll.ntdll.NtRaiseHardError
>>> response = (ctypes.c_ulong * 1)()

With the default OS error mode, the following raises a hard error dialog for 
STATUS_UNSUCCESSFUL (0xC001), with abort/retry/ignore options:

>>> NtRaiseHardError(0xC000_0001, 0, 0, None, 0, response)
0
>>> response[0]
2

The response value is limited to abort (2), retry (7), ignore (4) -- or simply 
returned (0) when the process hard error mode is disabled: 

>>> msvcrt.SetErrorMode(msvcrt.SEM_FAILCRITICALERRORS)
0
>>> NtRaiseHardError(0xC000_0001, 0, 0, None, 0, response)
0
>>> response[0]
0

NtRaiseHardError also checks for an error-mode override flag (0x1000_) in 
the status code, which is used in cases such as WinAPI FatalAppExitW. For 
example, the following will raise the dialog regardless of the hard error mode:

>>> NtRaiseHardError(0xC000_0001 | 0x1000_, 0, 0, None, 0, response)
0
>>> response[0]
2

--

___
Python tracker 

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

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

[Brett Cannon]

Change by Brett Cannon :


--
nosy:  -brett.cannon

___
Python tracker 

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

[issue40927] ./python -m test test___all__ test_binhex fails

[STINNER Victor]

STINNER Victor  added the comment:

Rémi Lapeyre: Thanks for the bug report, it's now fixed!

--
versions: +Python 3.9

___
Python tracker 

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

[issue40927] ./python -m test test___all__ test_binhex fails

[STINNER Victor]

STINNER Victor  added the comment:


New changeset af6932575391bca10f4f2145b56e3edbe9765343 by Victor Stinner in 
branch '3.9':
bpo-40927: Fix test_binhex when run twice (GH-20764) (GH-20789)
https://github.com/python/cpython/commit/af6932575391bca10f4f2145b56e3edbe9765343


--

___
Python tracker 

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

[issue39679] functools: singledispatchmethod doesn't work with classmethod

[Viktor Roytman]

Viktor Roytman  added the comment:

Sorry to bump this after months of inactivity but is there something I need to 
do here?

--

___
Python tracker 

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

[issue39465] [subinterpreters] Design a subinterpreter friendly alternative to _Py_IDENTIFIER

[STINNER Victor]

STINNER Victor  added the comment:


New changeset 1bcc32f0620d2e99649a6d423284d9496b7b3548 by Victor Stinner in 
branch 'master':
bpo-39465: Use _PyInterpreterState_GET() (GH-20788)
https://github.com/python/cpython/commit/1bcc32f0620d2e99649a6d423284d9496b7b3548


--

___
Python tracker 

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

[issue40927] ./python -m test test___all__ test_binhex fails

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +19984
pull_request: https://github.com/python/cpython/pull/20789

___
Python tracker 

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

[issue40927] ./python -m test test___all__ test_binhex fails

[STINNER Victor]

STINNER Victor  added the comment:


New changeset 9c24e2e4c10705d95258558348417a28007dac66 by Victor Stinner in 
branch 'master':
bpo-40927: Fix test_binhex when run twice (GH-20764)
https://github.com/python/cpython/commit/9c24e2e4c10705d95258558348417a28007dac66


--

___
Python tracker 

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

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

[STINNER Victor]

Change by STINNER Victor :


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

___
Python tracker 

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

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

[STINNER Victor]

STINNER Victor  added the comment:


New changeset c7a6c7b5279f766e65b7cc9dc5bebb73acee6672 by Victor Stinner in 
branch '3.8':
bpo-40826: Fix test_repl.test_close_stdin() on Windows (GH-20779) (GH-20785) 
(GH-20787)
https://github.com/python/cpython/commit/c7a6c7b5279f766e65b7cc9dc5bebb73acee6672


--

___
Python tracker 

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

[issue39465] [subinterpreters] Design a subinterpreter friendly alternative to _Py_IDENTIFIER

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +19983
pull_request: https://github.com/python/cpython/pull/20788

___
Python tracker 

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

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +19982
pull_request: https://github.com/python/cpython/pull/20787

___
Python tracker 

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

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

[STINNER Victor]

STINNER Victor  added the comment:


New changeset 4a4f660cfde8b683634c53e6214a6baa51de43b1 by Victor Stinner in 
branch '3.9':
bpo-40826: Fix test_repl.test_close_stdin() on Windows (GH-20779) (GH-20785)
https://github.com/python/cpython/commit/4a4f660cfde8b683634c53e6214a6baa51de43b1


--

___
Python tracker 

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

[issue40913] time.sleep ignores errors on Windows

[Tim Golden]

Tim Golden  added the comment:

Thinking about testing here.. is there any straightforward way to cause 
WaitForSingleObjectEx to fail?

The code change would be fairly slight and amenable to inspection, but it would 
be good to actually test it ;)

--

___
Python tracker 

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

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

[STINNER Victor]

STINNER Victor  added the comment:

Thanks for the bug report David Bolen and thanks for the analysis Eryk Sun. The 
bug should be be fixed in the master branch, and backports to 3.8 and 3.9 are 
coming.

--

___
Python tracker 

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

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +19981
pull_request: https://github.com/python/cpython/pull/20785

___
Python tracker 

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

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

[STINNER Victor]

STINNER Victor  added the comment:


New changeset f6e58aefde2e57e4cb11ea7743955da53a3f1e80 by Victor Stinner in 
branch 'master':
bpo-40826: Fix test_repl.test_close_stdin() on Windows (GH-20779)
https://github.com/python/cpython/commit/f6e58aefde2e57e4cb11ea7743955da53a3f1e80


--

___
Python tracker 

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

[issue40943] PEP 353: Drop support for PyArg_ParseTuple() "#" formats when PY_SSIZE_T_CLEAN is not defined

[STINNER Victor]

Change by STINNER Victor :


--
title: PEP 353: Drop support for PyArg_ParseTuple() format when 
PY_SSIZE_T_CLEAN is not defined -> PEP 353: Drop support for PyArg_ParseTuple() 
"#" formats when PY_SSIZE_T_CLEAN is not defined

___
Python tracker 

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

[issue27499] PY_SSIZE_T_CLEAN conflicts with Py_LIMITED_API

[STINNER Victor]

STINNER Victor  added the comment:

See also bpo-40943: PEP 353: Drop support for PyArg_ParseTuple() format when 
PY_SSIZE_T_CLEAN is not defined.

--

___
Python tracker 

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

[issue27499] PY_SSIZE_T_CLEAN conflicts with Py_LIMITED_API

[STINNER Victor]

STINNER Victor  added the comment:

> Oh, I can avoid this problem by setting Py_LIMITED_API to 0x3030 or 
> greater.

Hum, maybe the behavior is different because of the following code in 
Include/modsupport.h:

/* Due to a glitch in 3.2, the _SizeT versions weren't exported from the DLL. */
#if !defined(PY_SSIZE_T_CLEAN) || !defined(Py_LIMITED_API) || Py_LIMITED_API+0 
>= 0x0303

--
nosy: +vstinner

___
Python tracker 

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

[issue40703] PyType_FromSpec*() overwrites the type's "__module__"

[Stefan Behnel]

Stefan Behnel  added the comment:


New changeset 9419158a3e67ba2eadf33215568003ed723b0a98 by Miss Islington (bot) 
in branch '3.9':
bpo-40703: Let PyType_FromSpec() set "type.__module__" only if it is not set 
yet. (GH-20273) (GH-20782)
https://github.com/python/cpython/commit/9419158a3e67ba2eadf33215568003ed723b0a98


--

___
Python tracker 

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

[issue40703] PyType_FromSpec*() overwrites the type's "__module__"

[Stefan Behnel]

Change by Stefan Behnel :


--
stage: patch review -> test needed

___
Python tracker 

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

[issue40943] PEP 353: Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not defined

[STINNER Victor]

STINNER Victor  added the comment:

I started to write a long rationale to explain why "#" variants of formats must 
be deprecated, before I noticed that they are already deprecated! To not lost 
it, here is my rationale :-)


The C code base of Python switched from int to Py_ssize_t with PEP 353. For not 
break the backward compatibility, C extension modules have to opt-in for 
Py_ssize_t by defining PY_SSIZE_T_CLEAN macro in their code base. It affects a 
few format PyArg_ParseTuple() and Py_BuildValue():
https://docs.python.org/dev/c-api/arg.html

Currently, the documentation says "This behavior will change in a future Python 
version to only support Py_ssize_t and drop int support. It is best to always 
define PY_SSIZE_T_CLEAN."

Continue to use int by default prevents to accept content larger than 2 GB and 
causes issues with limited C API: bpo-27499.

I propose to raise a DeprecationWarning on C extension modules built without 
the PY_SSIZE_T_CLEAN macro defined.

#warning could be used to emit a warning when building a C extension without 
PY_SSIZE_T_CLEAN. The problem is that the compiler output is hidden by "pip 
install", only few developers pay attention to such warnings, and also we 
should not bother C extensions which don't use PyArg_ParseTuple() and 
Py_BuildValue().

I prefer to raise a DeprecationWarning exception at runtime since this warning 
can be made an error when using -Werror: it eases detection of deprecated 
modules without preventing to build or use a C extension using the deprecated 
functions.

Two releases after the DeprecationWarning is introduced, we can consider to 
always raise an exception. Again, I dislike the idea of always require 
PY_SSIZE_T_CLEAN macro when including "Python.h" header file. I suggest to only 
raise an exception at runtime when the few affected functions are called.

For example, PyArg_ParseTuple(args, "y*", &buffer) always Py_buffer which uses 
Py_ssize_t: the behavior does not depend on PY_SSIZE_T_CLEAN.

An alternative is to even deprecate the few "#" formats which are affected by 
PY_SSIZE_T_CLEAN.

--

___
Python tracker 

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

[issue40943] PEP 353: Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not defined

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +19980
pull_request: https://github.com/python/cpython/pull/20784

___
Python tracker 

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

[issue40943] PEP 353: Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not defined

[STINNER Victor]

STINNER Victor  added the comment:


New changeset d36cf5f1d20ce9f111a8fc997104785086e8eee6 by Victor Stinner in 
branch 'master':
bpo-40943: Replace PY_FORMAT_SIZE_T with "z" (GH-20781)
https://github.com/python/cpython/commit/d36cf5f1d20ce9f111a8fc997104785086e8eee6


--

___
Python tracker 

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

[issue40925] Remove redundant macros used for stack manipulation in interpreter

[Dong-hee Na]

Change by Dong-hee Na :


--
keywords: +patch
pull_requests: +19979
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/20783

___
Python tracker 

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

[issue40943] PEP 353: Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not defined

[STINNER Victor]

Change by STINNER Victor :


--
title: Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not 
defined -> PEP 353: Drop support for PyArg_ParseTuple() format when 
PY_SSIZE_T_CLEAN is not defined

___
Python tracker 

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

[issue40925] Remove redundant macros used for stack manipulation in interpreter

[Dong-hee Na]

Dong-hee Na  added the comment:

AFAIK, SET_VALUE is not used in CPython master codebase.

--

___
Python tracker 

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

[issue40925] Remove redundant macros used for stack manipulation in interpreter

[Dong-hee Na]

Change by Dong-hee Na :


--
nosy: +corona10

___
Python tracker 

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

[issue40703] PyType_FromSpec*() overwrites the type's "__module__"

[miss-islington]

Change by miss-islington :


--
nosy: +miss-islington
nosy_count: 5.0 -> 6.0
pull_requests: +19977
pull_request: https://github.com/python/cpython/pull/20782

___
Python tracker 

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

[issue40943] Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not defined

[STINNER Victor]

New submission from STINNER Victor :

Follow-up of bpo-36381: In Python 3.8, PyArg_ParseTuple() and Py_BuildValue() 
formats using "int" when PY_SSIZE_T_CLEAN is not defined, but Py_ssize_t when 
PY_SSIZE_T_CLEAN is defined, were deprecated by:

commit d3c72a223a5f771f964fc34557c55eb5bfa0f5a0
Author: Inada Naoki 
Date:   Sat Mar 23 21:04:40 2019 +0900

bpo-36381: warn when no PY_SSIZE_T_CLEAN defined (GH-12473)

We will remove int support from 3.10 or 4.0.

I propose to drop support for these formats in Python 3.10. It is a backward 
incompatible change on purpose, to ensure that all C extensions are compatible 
with objects larger than 2 GB, and that all C extensions behave the same.

I'm not sure of the effects of this issue on bpo-27499 "PY_SSIZE_T_CLEAN 
conflicts with Py_LIMITED_API".

--
components: C API
messages: 371216
nosy: inada.naoki, serhiy.storchaka, vstinner
priority: normal
severity: normal
status: open
title: Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not 
defined
versions: Python 3.10

___
Python tracker 

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

[issue40943] Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not defined

[STINNER Victor]

Change by STINNER Victor :


--
keywords: +patch
pull_requests: +19978
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/20781

___
Python tracker 

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

[issue40703] PyType_FromSpec*() overwrites the type's "__module__"

[Stefan Behnel]

Stefan Behnel  added the comment:


New changeset 24b8bad6d30ae4fb37ee686a073adfa5308659f9 by scoder in branch 
'master':
bpo-40703: Let PyType_FromSpec() set "type.__module__" only if it is not set 
yet. (GH-20273)
https://github.com/python/cpython/commit/24b8bad6d30ae4fb37ee686a073adfa5308659f9


--

___
Python tracker 

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

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

[Stefan Krah]

Stefan Krah  added the comment:

> The first warning line in the initial message of this bug report tries to 
> allocate 872 petabyte.

Yes, that's for systems like Linux where you never know what overallocation is 
going to permit and subsequently freeze the system.


Special casing malloc() for OS X/large allocations sounds like a good plan.

--

___
Python tracker 

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

[issue36543] Remove old-deprecated ElementTree features (part 2)

[Stefan Behnel]

Stefan Behnel  added the comment:

The xml.etree.cElementTree module is restored. We'll see about what to do with 
it later. It hurts less to keep it around than to delete it.

I think this ticket can be closed.

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

___
Python tracker 

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

[issue36543] Remove old-deprecated ElementTree features (part 2)

[Stefan Behnel]

Stefan Behnel  added the comment:


New changeset 3b97d1becbe08cf56c58d9c740a4622cbf6285fd by Miss Islington (bot) 
in branch '3.9':
bpo-36543: Revert "bpo-36543: Remove the xml.etree.cElementTree module." 
(GH-20117) (GH-20780)
https://github.com/python/cpython/commit/3b97d1becbe08cf56c58d9c740a4622cbf6285fd


--

___
Python tracker 

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

[issue40942] BaseManager cannot start with local manager

[Mike Jarvis]

New submission from Mike Jarvis :

I had a function for making a logger proxy that could be safely passed to 
multiprocessing workers and log back to the main logger with essentially the 
following code:
```
import logging
from multiprocessing.managers import BaseManager

class SimpleGenerator:
def __init__(self, obj): self._obj = obj
def __call__(self): return self._obj

def get_logger_proxy(logger):
class LoggerManager(BaseManager): pass
logger_generator = SimpleGenerator(logger)
LoggerManager.register('logger', callable = logger_generator)
logger_manager = LoggerManager()
logger_manager.start()
logger_proxy = logger_manager.logger()

return logger_proxy

logger = logging.getLogger('test')

logger_proxy = get_logger_proxy(logger)
```
This worked great on python 2.7 through 3.7. I could pass the resulting 
logger_proxy to workers and they would log information, which would then be 
properly sent back to the main logger.

However, on python 3.8.2 (and 3.8.0) I get the following:
```
Traceback (most recent call last):
  File "test_proxy.py", line 20, in 
logger_proxy = get_logger_proxy(logger)
  File "test_proxy.py", line 13, in get_logger_proxy
logger_manager.start()
  File "/anaconda3/envs/py3.8/lib/python3.8/multiprocessing/managers.py", line 
579, in start
self._process.start()
  File "/anaconda3/envs/py3.8/lib/python3.8/multiprocessing/process.py", line 
121, in start
self._popen = self._Popen(self)
  File "/anaconda3/envs/py3.8/lib/python3.8/multiprocessing/context.py", line 
283, in _Popen
return Popen(process_obj)
  File 
"/anaconda3/envs/py3.8/lib/python3.8/multiprocessing/popen_spawn_posix.py", 
line 32, in __init__
super().__init__(process_obj)
  File "/anaconda3/envs/py3.8/lib/python3.8/multiprocessing/popen_fork.py", 
line 19, in __init__
self._launch(process_obj)
  File 
"/anaconda3/envs/py3.8/lib/python3.8/multiprocessing/popen_spawn_posix.py", 
line 47, in _launch
reduction.dump(process_obj, fp)
  File "/anaconda3/envs/py3.8/lib/python3.8/multiprocessing/reduction.py", line 
60, in dump
ForkingPickler(file, protocol).dump(obj)
AttributeError: Can't pickle local object 
'get_logger_proxy..LoggerManager'
```
So it seems that something changed about ForkingPickler that makes it unable to 
handle the closure in my get_logger_proxy function.

I don't know if this is an intentional change in behavior or an unintentional 
regression.  If the former, I would appreciate advice on how to modify the 
above code to work.

Possibly relevant system details:
```
$ uname -a
Darwin Fife 17.5.0 Darwin Kernel Version 17.5.0: Mon Mar  5 22:24:32 PST 2018; 
root:xnu-4570.51.1~1/RELEASE_X86_64 x86_64
$ python --version
Python 3.8.2
$ which python
/anaconda3/envs/py3.8/bin/python
$ conda info

 active environment : py3.8
active env location : /anaconda3/envs/py3.8
shell level : 2
   user config file : /Users/Mike/.condarc
 populated config files : /Users/Mike/.condarc
  conda version : 4.8.3
conda-build version : 3.18.5
 python version : 3.6.5.final.0
   virtual packages : __osx=10.13.4
   base environment : /anaconda3  (writable)
   channel URLs : https://conda.anaconda.org/conda-forge/osx-64
  https://conda.anaconda.org/conda-forge/noarch
  https://conda.anaconda.org/astropy/osx-64
  https://conda.anaconda.org/astropy/noarch
  https://repo.anaconda.com/pkgs/main/osx-64
  https://repo.anaconda.com/pkgs/main/noarch
  https://repo.anaconda.com/pkgs/r/osx-64
  https://repo.anaconda.com/pkgs/r/noarch
  package cache : /anaconda3/pkgs
  /Users/Mike/.conda/pkgs
   envs directories : /anaconda3/envs
  /Users/Mike/.conda/envs
   platform : osx-64
 user-agent : conda/4.8.3 requests/2.23.0 CPython/3.6.5 
Darwin/17.5.0 OSX/10.13.4
UID:GID : 501:20
 netrc file : /Users/Mike/.netrc
   offline mode : False

```

--
components: Library (Lib)
messages: 371211
nosy: Mike Jarvis
priority: normal
severity: normal
status: open
title: BaseManager cannot start with local manager
type: behavior
versions: Python 3.8

___
Python tracker 

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

[issue36543] Remove old-deprecated ElementTree features (part 2)

[miss-islington]

Change by miss-islington :


--
nosy: +miss-islington
nosy_count: 6.0 -> 7.0
pull_requests: +19976
pull_request: https://github.com/python/cpython/pull/20780

___
Python tracker 

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

[issue36543] Remove old-deprecated ElementTree features (part 2)

[Stefan Behnel]

Stefan Behnel  added the comment:


New changeset ec88e1bca81a167e6d5c0ac635e22f84298cb1df by Serhiy Storchaka in 
branch 'master':
bpo-36543: Revert "bpo-36543: Remove the xml.etree.cElementTree module." 
(GH-20117)
https://github.com/python/cpython/commit/ec88e1bca81a167e6d5c0ac635e22f84298cb1df


--

___
Python tracker 

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

[issue40940] How to update pip permanently for new venv?

[Zachary Ware]

Change by Zachary Ware :


--
components: +Library (Lib) -asyncio
nosy: +vinay.sajip -asvetlov, yselivanov

___
Python tracker 

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

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

[Ronald Oussoren]

Ronald Oussoren  added the comment:

I've filed a report with Apple about this (FB7731971), even though I expect 
that this behaviour will not change. That's something we should have done years 
ago.

BTW. The link to malloc_print_configure that Victor shared seems to indicate 
that the default for MallocDebugReport should be "none", instead of "stderr". 
The code on opensource.apple.com conforms this 
(https://opensource.apple.com/source/libmalloc/libmalloc-283.60.1/src/malloc_printf.c.auto.html).
  Apparently Apple uses a slightly different code when building macOS :-(

Note that this annoying message is only printed when the proces runs out of 
address space, which requires allocating an insane amount of memory (the first 
warning line in the initial message of this bug report tries to allocate 872 
petabyte).  

If this is something we want to avoid its probably easier to switch to a 
allocator that won't avoids calling malloc(3) on large enough allocations (for 
example return NULL for any allocation attempt above 4TB, which is comfortably 
above the max amount of memory in a Mac Pro).  This theoretically limits memory 
allocations, but in practice the system will be unusable with far smaller 
allocations (assuming the allocated memory is actually used).

--

___
Python tracker 

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

[issue40562] SEO: differentiate between Python 2 and Python 3 docs on Google SERP

[Pinto]

Pinto  added the comment:

I have the same problem on my site https://lesmarketing.fr I deactivated the 
breadcrumbs, you have found a solution ?

--
nosy: +khaled

___
Python tracker 

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

[issue17013] Allow waiting on a mock

[Ilya Kulakov]

Ilya Kulakov  added the comment:

> That is not true, is actually encouraged to check for singletons like True, 
> False and None.

You're right, just never used it as I never needed an identity check against 
True / False

The PR is re-done to use an additional property call_event instead of extending 
called for backwards compatibility.

--

___
Python tracker 

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

[issue39666] IDLE: Factor out similar code in editor and hyperparser

[Terry J. Reedy]

Terry J. Reedy  added the comment:

The quote from #32989 is from my msg313179, msg313179.

There are two levels of duplication.  First, between Hyperparser and 
EditorWindow.  Second between editor and shell branches.  While I said before 
to resolve the first with an EditorWindow method, as done in the patch, a 
hyperparser function, with 'self' replaced by 'editwin' would be possible.  I 
might prefer that.

The second level of duplication could be handled by a method in EditorWindow 
overridden by a method in PyShell.  But with duplication between the branches 
removed as in the patch, leaving the Shell branch so short, this does not seem 
as worthwhile.  I suspect/expect it would be even less so after future Shell 
changes.

--
nosy: +taleinat

___
Python tracker 

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

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +19975
stage: resolved -> patch review
pull_request: https://github.com/python/cpython/pull/20779

___
Python tracker 

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

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

[Stefan Krah]

Stefan Krah  added the comment:

And indeed, with the new decimal MAX_PREC feature, you should see
the misguided diagnostic as well on OS X:

>>> from decimal import *
>>> 
>>> c = getcontext()
>>> c.prec = MAX_PREC
>>> Decimal(4).sqrt()
Decimal('2')
>>> 


So it is real code, but extremely rarely used.

--

___
Python tracker 

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

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

[Stefan Krah]

Stefan Krah  added the comment:

But if malloc_print_configure() is not a public API, it should probably not be 
used.

--

___
Python tracker 

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

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

[Stefan Krah]

Stefan Krah  added the comment:

No, it does not cause real issues. Adding this feature would just suppress 
chatty diagnostics like this one, which are a bit unfriendly: 

>>> [0] * 1
python3(36633,0x110c08dc0) malloc: can't allocate region
:*** mach_vm_map(size=84096, flags: 100) failed (error code=3)
python3(36633,0x110c08dc0) malloc: *** set a breakpoint in malloc_error_break 
to debug
Traceback (most recent call last):
  File "", line 1, in 
MemoryError


So yes, users do occasionally see it outside the test suite.

--

___
Python tracker 

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

[issue17013] Allow waiting on a mock

[Ilya Kulakov]

Ilya Kulakov  added the comment:

As far as I understand it introduces 3 methods that may clash. It's unlikely 
but (I speculate)
is still more likely than an identity check with called.

That being said, the PR can be redone as a subclass. But that implementation 
will not play
as nicely with the planned `awaited` property for asyncio mocks (see 
description in the PR).

--

___
Python tracker 

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

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

[Ronald Oussoren]

Ronald Oussoren  added the comment:

I'm not sure if it is worthwhile to tweak CPython to work around this 
misfeature of libc on macOS (and likely iOS).  Is this something that causes 
issues in real code, or just in the test suite?  Looking at this particular 
test is seems to use a context that is not likely to occur in real code (due to 
using a lot of memory)


Note that malloc_print_configure is not a public API, using that can cause 
problems for folks that embed Python in apps that are shipped in the app store.

--

___
Python tracker 

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

[issue36439] Inconsistencies with datetime.fromtimestamp(t) when t < 0

[Paul Anton Letnes]

Paul Anton Letnes  added the comment:

I've encountered an issue on anaconda python on windows 10 v1909 which I 
suspect is related. It looks like no dates in 1970 can be converted to 
datetime.timestamp():

Python 3.8.2 (default, Apr 14 2020, 19:01:40) [MSC v.1916 64 bit (AMD64)]
Type 'copyright', 'credits' or 'license' for more information
IPython 7.13.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import datetime

In [2]: datetime.datetime(1970, 1, 2, 0, 0, 1, 123456).timestamp()
---
OSError   Traceback (most recent call last)
 in 
> 1 datetime.datetime(1970, 1, 2, 0, 0, 1, 123456).timestamp()

OSError: [Errno 22] Invalid argument

In [3]: datetime.datetime(1971, 1, 2, 0, 0, 1, 123456).timestamp()
Out[3]: 31618801.123456

--
nosy: +Paul Anton Letnes

___
Python tracker 

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

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

[Rémi Lapeyre]

Rémi Lapeyre  added the comment:

> But is it really an use case to log any memory allocation failure? Python is 
> very likely to raise a MemoryError exception in this case. It's well defined, 
> no?

Yes, we are not trying to log the allocation failure, we are just trying to 
suppress a dubious error message that occurs specifically on MacOS.

--

___
Python tracker 

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

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

[STINNER Victor]

STINNER Victor  added the comment:

> Would it be possible to wrap malloc_print_configure() 
> (https://github.com/PureDarwin/libmalloc/blob/e37056265821cd6e014ab911d9fe3b9d0da88e22/src/malloc_printf.c#L59)
>  in a context manager that we put in test.support? or to override 
> https://github.com/PureDarwin/libmalloc/blob/e37056265821cd6e014ab911d9fe3b9d0da88e22/src/malloc_printf.c#L36?

I don't see much benefit of having a feature which only works on macOS.

You can put a hook on memory allocations using PyMem_SetAllocator() to trigger 
any action you want when any memory allocation done by Python fails.

But is it really an use case to log any memory allocation failure? Python is 
very likely to raise a MemoryError exception in this case. It's well defined, 
no?

--

___
Python tracker 

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

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

[STINNER Victor]

STINNER Victor  added the comment:

> Ok, I will try to do this in the coming days. Is adding this kind of super 
> ugly, super specific code to pymain_init() ok?

Maybe _PyPreConfig_Write() would be a better place.

There is a very little risk that memory allocation done before 
_PyPreConfig_Write() (i.e. in _PyPreConfig_Read()) fail with out of memory.

--
nosy: +vstinner

___
Python tracker 

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

[issue17013] Allow waiting on a mock

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

> Current implementation relies on that:

Notice that this is a clear disadvantage over a subclass-based approach, which 
is backwards compatible and preserves the semantics of mock.

--

___
Python tracker 

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

[issue40941] Merge generator.gi_running and frame executing flag into single frame state

[Mark Shannon]

New submission from Mark Shannon :

Generators have a "gi_running" attribute (coroutines have an equivalent 
cr_running flag). Internally frame also has an executing flag.

We use these, plus the test `f_stacktop pointer == NULL`, to determine what 
state a generator or frame is in.

It would be much cleaner to maintain a single f_state field in the frame to 
track the state of a frame, reducing the change of ambiguity and error.

The possible states of a frame are:
CREATED -- Frame exists but has not been executed at all
SUSPENDED -- Frame has been executed, and has been suspended by a yield
EXECUTING -- Frame is being executed
RETURNED -- Frame has completed by a RETURN_VALUE instruction
RAISED -- Frame has completed as a result of an exception being raised
CLEARED -- Frame has been cleared, either by explicit call to clear or by the 
GC.

--
assignee: Mark.Shannon
components: Interpreter Core
messages: 371194
nosy: Mark.Shannon
priority: normal
severity: normal
stage: needs patch
status: open
title: Merge generator.gi_running and frame executing flag into single frame 
state
type: performance

___
Python tracker 

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

[issue17013] Allow waiting on a mock

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

> 1. called is almost never used in practice (people just use .assert*)

Sorry but saying "almost never used" is not good enough. Not only because you 
hold incomplete data but because backwards compatibility is mainly binary: it 
breaks or it does not, and this breaks.

> 2. The is True / False is discouraged and is rarely used by itself, let alone 
> in combination with .called

That is not true, is actually encouraged to check for singletons like True, 
False and None.

--

___
Python tracker 

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

[issue17013] Allow waiting on a mock

[Ilya Kulakov]

Ilya Kulakov  added the comment:

> Unfortunately, we take backwards compatibility very seriously in the core 
> team and this is a big downside of this proposal.

Current implementation relies on that:
1. called is almost never used in practice (people just use .assert*)
2. The is True / False is discouraged and is rarely used by itself, let alone 
in combination with .called

> Wouldn't that also break any mock that is mocking an object with a 
> "called_event" attribute?

It should break them in the same way as "called" breaks them now.

--

___
Python tracker 

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

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

[Stefan Krah]

Stefan Krah  added the comment:

Changing the title to get more input from others.

--
title: test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: 
can't allocate region" on MacOS -> OS X: malloc(): set default diagnostics to 
DEBUG_WRITE_ON_CRASH

___
Python tracker 

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