Jason Novinger@programming.devM to Python@programming.dev · 2 years agojendrikseipp/vulture: Find dead Python codegithub.comexternal-linkmessage-square7linkfedilinkarrow-up116arrow-down10file-text
arrow-up116arrow-down1external-linkjendrikseipp/vulture: Find dead Python codegithub.comJason Novinger@programming.devM to Python@programming.dev · 2 years agomessage-square7linkfedilinkfile-text
minus-squareDaniel Quinn@lemmy.calinkfedilinkEnglisharrow-up1·2 years agoIf you ensure 100% test coverage, you don’t need this ;-)
minus-squaregedhrel@lemmy.worldlinkfedilinkarrow-up3·2 years agoWhat if your test is the only thing that calls a function?
minus-squareDaniel Quinn@lemmy.calinkfedilinkEnglisharrow-up1·2 years agoMaybe I’m misunderstanding vulture. My impression was that it’s meant to be run in your CI, which would mean it’s only privy to code executed by your tests. If it actually attached to production sessions, then yeah that’s pretty handy.
If you ensure 100% test coverage, you don’t need this ;-)
What if your test is the only thing that calls a function?
Maybe I’m misunderstanding vulture. My impression was that it’s meant to be run in your CI, which would mean it’s only privy to code executed by your tests. If it actually attached to production sessions, then yeah that’s pretty handy.