Dima Tisnek writes:
> I thought that collections compatibility was kept up to 3.8
> specifically because py2 was alive.
> No that that requirement is gone, so should the shim, right?
Python 2 is still very much alive (even in a Python 3 venv :-þ):
(analysis.venv) 01 16:56$ /usr/bin/python
The Steering Council has considered Guido’s request for pronouncement on PEP
613 - Explicit Type Aliases, written by Shannon Zhu and sponsored by Guido van
Rossum.
The Council unanimously accepts PEP 613. Congratulations!
We’ll leave it to the sponsor and author to update the PEP accordingly.
Victor Stinner wrote:
> Hi,
> Is it ok to add a static inline function to the limited API? Can it
> cause ABI issue? Or is it safer to add a regular function? For
> example, is it safe to add the following function to the limited API?
> static inline PyObject
> _PyObject_CallOneArg(PyObject func,
Hi,
Is it ok to add a static inline function to the limited API? Can it
cause ABI issue? Or is it safer to add a regular function? For
example, is it safe to add the following function to the limited API?
static inline PyObject *
_PyObject_CallOneArg(PyObject *func, PyObject *arg)
{
...
r
On 2020-01-30 07:12, Dima Tisnek wrote:
On Fri, 24 Jan 2020 at 00:27, Victor Stinner wrote:
Miro and me consider that Python 3.9 is pushing too much pressure on
projects maintainers to either abandon Python 2.7 right now...
Let's not conflate py2 EOL with what-should-go-into-py39.
https://
