drizzledump is blending INSERT statements when --skip-extended-insert is used

[Patrick Crews]

CREATE TABLE `t1` (
  `a` INT DEFAULT NULL,
  `b` VARCHAR(1) COLLATE utf8_general_ci DEFAULT NULL
) ENGINE=InnoDB COLLATE = utf8_general_ci;

INSERT INTO `t1` VALUES (1,'a'),(1,'a'),(1,'b'),(10,'z');

drizzledump will output this fine normally, but the output looks like this if we use --skip-extended-insert:
ALTER TABLE `t1` DISABLE KEYS;
INSERT INTO `t1` VALUES (1,'a'INSERT INTO `t1` VALUES (1,'a'INSERT INTO `t1` VALUES (1,'b'INSERT INTO `t1` VALUES (10,'z');
ALTER TABLE `t1` ENABLE KEYS;