Feedback on v2.0.0rc0 In my particular case taking out the

coverage

field from

test.pytest

is producing a lot of extra work in making the jump to the new version. I'm going to edit the 111 files, but to save someone else some work that could be spread out over time, couldn't this be a

WARN

that gets depreciated in 2.1.0dev0? It is a similar change as the simplification of

pants_requirement('tornado==1.1')

. I guess you could make it not do anything but still exist so we don't get stopped by the "Unrecognized field" error.

Yes, it can be. I can add this back for rc1 tomorrow. Please save yourself the time from doing it tonight!