I have never tried PEP0523 before so I have just did a quick look and
pushed what I got to https://github.com/sklam/etude_py36_custom_jit.
If you run
https://github.com/sklam/etude_py36_custom_jit/blob/master/test.py, you
should get the following printouts:
Hello
Hey
Yes
** myjit is evaluating fr
Hi,
The CPython repository was converted from Mercurial to Git. Before
with Mercurial, we used extensively merges. For example, a bug was
fixed in branche 3.5, merged into 3.6 and then merged into master.
With the conversion to Git, some merges commit are removed, some
others are kept.
My questio
Can you try
git log master ^3.6
I think it will give what's on master and not in 3.6
On Mar 31, 2017 8:47 AM, "Victor Stinner" wrote:
> Hi,
>
> The CPython repository was converted from Mercurial to Git. Before
> with Mercurial, we used extensively merges. For example, a bug was
> fixed in b
ACTIVITY SUMMARY (2017-03-24 - 2017-03-31)
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:
open5855 ( -8)
closed 35854 (+65)
total 41709 (+57)
Open issues wit
On Mar 31, 2017 10:48 AM, "Victor Stinner" wrote:
Hi,
The CPython repository was converted from Mercurial to Git. Before
with Mercurial, we used extensively merges. For example, a bug was
fixed in branche 3.5, merged into 3.6 and then merged into master.
With the conversion to Git, some merges c
2017-03-31 18:36 GMT+02:00 Ryan Gonzalez :
> I think you want:
>
> git log --no-merges --first-parent
Oh, I mised --first-parent: it seems like it fixed my issue, thanks!
But --no-merges is not what I want. I want to see merge commits which
are only in the master branch.
Victor
_
On 31 March 2017 at 05:22, Nathaniel Smith wrote:
>>> On Mon, Mar 20, 2017 at 11:30 AM, Oleg Nesterov wrote:
>>> > [Aborting "yield" in a "for" loop leaves a sub-generator open, but
>>> > aborting "yield from" cleans up the sub-generator]
>
> In any case the short answer to your original questio