Progress & metadata goes to stderr instead of stdout

This may be related to #428 (which is now closed)

I'm executing tippecanoe from within a Python application (see snippet below) and the progress metadata is being piped to stderr instead of stdout.

cmd = ['/opt/tippecanoe', '-Z0', '-z3', '--drop-rate=1', '--no-tile-size-limit', '--no-feature-limit',
           '--read-parallel', '--no-progress-indicator', '--force', '-l', event['indexType'], '-o', event['tileFile'], event['geojsonFile']]

r = run(cmd, stdout=PIPE, stderr=PIPE, text=True)
LOG.debug('StdOut: ' + (r.stdout or "No stdout"))
LOG.error('Error: ' + (r.stderr or "No stderr"))

Below is the resulting output:

DEBUG:Tippecanoe-3uehZ-Lambda:StdOut: No stdout
ERROR:Tippecanoe-3uehZ-Lambda:Error:                               
6782 features, 320098 bytes of geometry, 8 bytes of separate metadata, 155120 bytes of string pool

Is there a way to have the progress metadata sent to stdout and leave stderr for only errors?

Reproduce the reported tippecanoe command with stdout and stderr captured separately, including --no-progress-indicator, and inspect where the progress metadata is emitted. Done means progress metadata is available on stdout while stderr contains only errors; verify the behavior from the Python subprocess example.