brash-baker-91190
02/12/2021, 12:44 AMhundreds-father-404
02/12/2021, 1:06 AMbrash-baker-91190
02/12/2021, 1:08 AMhundreds-father-404
02/12/2021, 1:11 AMbrash-baker-91190
02/12/2021, 1:16 AM--verbose
to mypy) I get the same failures as under Pants. When I remove the files that are part of my pytype-only package, it works (and I can configure the run to ignore imports for that package). If I even add one file of my pytype-only package, that's enough to blow things up in a way that I can't seem to filter out. So, I think passing just the files from the targeted packages seems like the right thing to do. It seems that this will work better with Pants' filtering (e.g., tags, target globbing, etc), and will also allow you to adopt mypy incrementally. This is all caveated by the fact that I've personally only started using mypy this week, so I'm certainly open to the idea that I've missed something important 😅hundreds-father-404
02/12/2021, 2:01 AMmypy project/app.py project/dep.py
vs. mypy project/app.py
? not based on whether the file is present in the chroot?brash-baker-91190
02/12/2021, 2:20 AMhundreds-father-404
02/12/2021, 2:26 AM--no-process-execution-cleanup-local-dirs
. There will be something like mypy.pex
in it, and the chroot of all the relevant files. You can then do ./mypy.pex arg1 arg2
brash-baker-91190
02/12/2021, 3:11 AM__run.sh
file and/or the __files.txt
file. When I ran __run.sh
pointed to a version of __files.txt
that I had removed my pytest-only library files from, I get the behavior I'm after. I didn't change any of the files that were in the chroot. So, I think that is fairly strong support for this theory 😄hundreds-father-404
02/12/2021, 3:12 AMbrash-baker-91190
02/12/2021, 3:12 AMmypy.pex
directly failed because I didn't have the environment present in __run.sh)hundreds-father-404
02/12/2021, 3:49 AMbrash-baker-91190
02/12/2021, 1:36 PMhundreds-father-404
03/12/2021, 7:49 PMbrash-baker-91190
03/12/2021, 8:02 PMhundreds-father-404
03/12/2021, 8:04 PMbrash-baker-91190
03/12/2021, 8:05 PM