PEP 7 requires CPython to use C code conforming to the venerable C89
standard. Traditionally, we've been stuck with C89 due to poor C support
in MSVC. However, MSVC 2013 and 2015 implement the key features of C99.
C99 does not offer anything earth-shattering; here are the features I
think we'd find
On Fri, 03 Jun 2016 23:21:25 +0100, MRAB wrote:
> On 2016-06-03 22:50, R. David Murray wrote:
> > I don't understand how it happened, but apparently I got a merge commit
> > backward and merged 3.6 into 3.5 and pushed it without realizing what
> > had happened. If anyone has any clue how to rever
On 2016-06-03 22:50, R. David Murray wrote:
I don't understand how it happened, but apparently I got a merge commit
backward and merged 3.6 into 3.5 and pushed it without realizing what
had happened. If anyone has any clue how to reverse this cleanly,
please let me know. (There are a couple peo
I don't understand how it happened, but apparently I got a merge commit
backward and merged 3.6 into 3.5 and pushed it without realizing what
had happened. If anyone has any clue how to reverse this cleanly,
please let me know. (There are a couple people at the sprints looking
in to it, but the m
For those of you who follow python-ideas or were at the PyCon US 2016
language summit, you have already seen/heard about this PEP. For those of
you who don't fall into either of those categories, this PEP proposed a
frame evaluation API for CPython. The motivating example of this work has
been Pyji
ACTIVITY SUMMARY (2016-05-27 - 2016-06-03)
Python tracker at http://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:
open5537 ( +8)
closed 33416 (+52)
total 38953 (+60)
Open issues wit
