Actually, tachandler.py broke badly (at least from lp-buildd's perspective) and got a cleaned-up shiny copy of it's own, sitting next to tachandler.py in the same wrong-for-packaging directory, just so that lp-buildd has a file to copy in and use for itself.
The clean solution is to move the file into lp-buildd, and get out of the tree entirely.
The code is not rolled out as part of LP rollouts, is really a separate tree of code that happens to be glommed onto the side of the existing (unrelated) code base we call "launchpad"
Actually, tachandler.py broke badly (at least from lp-buildd's perspective) and got a cleaned-up shiny copy of it's own, sitting next to tachandler.py in the same wrong-for-packaging directory, just so that lp-buildd has a file to copy in and use for itself.
The clean solution is to move the file into lp-buildd, and get out of the tree entirely.
The code is not rolled out as part of LP rollouts, is really a separate tree of code that happens to be glommed onto the side of the existing (unrelated) code base we call "launchpad"