That should be removed.
(appears to be fixed in 2.0.0, which is packaged and ready to go after the test2 freeze; will close this bug when 2.0.0 hits rawhide)