In a recent PR (https://github.com/python/cpython/pull/18057), I received
the following error message in the Azure Pipelines build results:
##[error]We stopped hearing from agent Azure Pipelines 5. Verify the agent
machine is running and has a healthy network connection. Anything that
terminates a
On 2020-01-31 19:58, Ethan Furman wrote:
On 01/31/2020 10:47 AM, Mike Miller wrote:
On 2020-01-23 07:20, Victor Stinner wrote:
Python 3.9 introduces many small incompatible changes which broke tons
There's a well-known and established way of signaling breaking changes in
software platforms
On 1/31/2020 1:27 PM, mailer@app.tempr.email wrote:
Couldn't help but notice that there are quite a few stalled
issues/patches, some of them for years even. :-/ So I thought, it might
help to bump them here on the mailing list.
https://bugs.python.org/issue28053
https://github.com/python/cpyth
On 01/31/2020 10:47 AM, Mike Miller wrote:
On 2020-01-23 07:20, Victor Stinner wrote:
Python 3.9 introduces many small incompatible changes which broke tons
There's a well-known and established way of signaling breaking changes in
software platforms—it is to increment the major version numb
On 2020-01-23 07:20, Victor Stinner wrote:
> Python 3.9 introduces many small incompatible changes which broke tons
There's a well-known and established way of signaling breaking changes in
software platforms—it is to increment the major version number.
Rather than debating the merits of bre
Couldn't help but notice that there are quite a few stalled issues/patches,
some of them for years even. :-/ So I thought, it might help to bump them here
on the mailing list.
https://bugs.python.org/issue28053https://github.com/python/cpython/pull/9959https://github.com/python/cpython/pull/15058
ACTIVITY SUMMARY (2020-01-24 - 2020-01-31)
Python tracker at https://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open7300 (+15)
closed 43962 (+52)
total 51262 (+67)
Open issues wi
Hi all,
I may be thinking in the wrong direction, but right now
`PyType_Type.tp_new` will resolves the `metaclass` from the bases and
call:
type = (PyTypeObject *)metatype->tp_alloc(metatype, nslots);
where `metatype` is actually resolved from the metatype of the bases.
In contrast `PyType_
I think this particular mess was caused by the hiding of
“DeprecationWarning”s by default: If you don’t see any warnings cropping up
in your production code, you don’t know you have to fix something.
Some languages handle it like this:
1. Silent deprecation warning (deprecated in docs and/or h