On Nov/26, Hilko Bengen wrote: > The plaso and dfvfs packages are maintained by me and are affected by > the API breakage. > [...] > I think I am going to package construct-legacy, based upon > <https://pypi.python.org/pypi/construct-legacy>.
This makes the most sense: I don't think it's reasonable to keep an older version forever because some upstream authors don't, or can't, move on to the new API. At any rate, I should have coordinated with you so construct > 2.8 and construct-legacy would have entered sid around the same time: please accept my apologies about that. > It looks like mitmproxy and bdfproxy are also affected Well, no: the newer construct was uploaded specifically so a recent mitmproxy can be packaged and re-enter testing. Cheers, --Seb
