On 13 February 2015 at 22:49, Zachary Ware wrote:
> It's strange that
> you're getting modifications, though; I can't reproduce on Linux (and
> don't have quick access to Windows right now). Make sure you're
> definitely at tip, and if it's still changing please open an issue.
Definitely at tip.
On Fri, Feb 13, 2015 at 4:56 PM, Eric Snow wrote:
> On Fri, Feb 13, 2015 at 3:49 PM, Zachary Ware
> wrote:
>> Yes, importlib.h changes should never be included in a patch (it would
>
> Unless they should. :) E.g. you modified importlib/_bootstrap.py, the
> marshal format, bytecodes, etc.
If I'm
On Fri, Feb 13, 2015 at 3:49 PM, Zachary Ware
wrote:
> On Fri, Feb 13, 2015 at 4:09 PM, Paul Moore wrote:
>> I'm working on a patch for the Python launcher. I built Python
>> (current tip, on MS Windows, with VS 2015), and I've just noticed that
>> hg status shows:
>>
hg status -mard
>> M Doc
On Fri, Feb 13, 2015 at 4:09 PM, Paul Moore wrote:
> I'm working on a patch for the Python launcher. I built Python
> (current tip, on MS Windows, with VS 2015), and I've just noticed that
> hg status shows:
>
>>>hg status -mard
> M Doc\using\windows.rst
> M PC\launcher.c
> M Python\importlib.h
>
I'm working on a patch for the Python launcher. I built Python
(current tip, on MS Windows, with VS 2015), and I've just noticed that
hg status shows:
>>hg status -mard
M Doc\using\windows.rst
M PC\launcher.c
M Python\importlib.h
I didn't change importlib.h, and I don't see that the changes I did
