aaron.ballman added a comment. In D64454#1601439 <https://reviews.llvm.org/D64454#1601439>, @nickdesaulniers wrote:
> In D64454#1600922 <https://reviews.llvm.org/D64454#1600922>, @aaron.ballman > wrote: > > > I use svn in-tree, so I tried it out and it does not seem to work for me. > > > > c:\llvm\tools\clang\tools\extra\docs\clang-tidy\checks>python > > gen-static-analyzer-docs.py > > Traceback (most recent call last): > > File "gen-static-analyzer-docs.py", line 120, in <module> > > main() > > File "gen-static-analyzer-docs.py", line 109, in main > > checkers = get_checkers() > > File "gen-static-analyzer-docs.py", line 23, in get_checkers > > result = subprocess.run(["llvm-tblgen", "--dump-json", "-I", > > AttributeError: 'module' object has no attribute 'run' > > > > c:\llvm\tools\clang\tools\extra\docs\clang-tidy\checks>python --version > > Python 2.7.16 > > > > > Via: http://llvmweekly.org/issue/289 > > > Tom Stellard reminds us that LLVM's subversion is scheduled to be retired > > by Oct 21 2019, and enourages everyone to move their workflow to GitHub as > > soon as possible. See the GitHub migration status for more info. > > @aaron.ballman should we really be spending time supporting a workflow that > is deprecated and due for removal? Yes -- svn is still an official way to work with our repositories and it must continue to work until we retire it. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D64454/new/ https://reviews.llvm.org/D64454 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
