[PATCH] D38016: [lit] Make lit stop writing .pyc files

[Zachary Turner via llvm-commits]

I would think so. I understood it before because I reverted the creation of
the directory (which didn't delete it since pyc files were there so it
wasn't empty) then readded, which was a conflict because it was already
there.

But an hour or so ago it conflicted on a simple update, so at this point
I'm at a loss
On Mon, Sep 18, 2017 at 6:35 PM Shoaib Meenai via Phabricator <
reviews at reviews.llvm.org> wrote:

> smeenai accepted this revision.
> smeenai added a comment.
> This revision is now accepted and ready to land.
>
> This seems fine as a workaround, though I'm curious about the root cause.
> Shouldn't there only be conflicts during an update if the update is
> bringing in pyc files of its own (i.e. if pyc files got committed to svn)?
>
>
> https://reviews.llvm.org/D38016
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20170919/e3f53b5c/attachment.html>