IIRC, python will generate byte-compiled ".pyc" versions of the ".py" files automatically (and helpfully leave them in the CWD...) We turned that off for the testsuite through some Python magic I don't think I ever knew, but if I did I've certainly forgotten it... Anyway, sounds like that got turned back on again, and we should turn it off again...
Jim > On Apr 18, 2016, at 11:01 AM, Zachary Turner via lldb-commits > <lldb-commits@lists.llvm.org> wrote: > > It seems very strange to me to be changing a .pyc filename to a .py filename. > I think we should try to understand where the .pyc filename is coming from > to begin with, and this is just masking the real error. > > On Mon, Apr 18, 2016 at 10:10 AM Pavel Labath via lldb-commits > <lldb-commits@lists.llvm.org> wrote: > labath accepted this revision. > labath added a comment. > This revision is now accepted and ready to land. > > Ok, makes sense then, thanks for making sure it's necessary. > > I don't quite understand how the string makes it's way there though, as the > only place setting this field in the entire repository seems to be > lldbinline.py > > > http://reviews.llvm.org/D19215 > > > > _______________________________________________ > lldb-commits mailing list > lldb-commits@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits > _______________________________________________ > lldb-commits mailing list > lldb-commits@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
