-
Notifications
You must be signed in to change notification settings - Fork 100
WISH: Output messages and progress to stderr (instead of stdout) #217
Copy link
Copy link
Open
Labels
pending::discussioncontains some ongoing discussion that needs to be resolved prior to proceedingcontains some ongoing discussion that needs to be resolved prior to proceedingsource::communitycatch-all for issues filed by community memberscatch-all for issues filed by community membersstale::recovered[bot] recovered after being marked as stale[bot] recovered after being marked as staletype::featurerequest for a new feature or capabilityrequest for a new feature or capability
Metadata
Metadata
Assignees
Labels
pending::discussioncontains some ongoing discussion that needs to be resolved prior to proceedingcontains some ongoing discussion that needs to be resolved prior to proceedingsource::communitycatch-all for issues filed by community memberscatch-all for issues filed by community membersstale::recovered[bot] recovered after being marked as stale[bot] recovered after being marked as staletype::featurerequest for a new feature or capabilityrequest for a new feature or capability
It looks like
conda-packoutputs messages and progress to standard output;I think it would be more in line with the Unix-philosophy for such output, meant for human consumption, to go to standard error, and leave output to stdout to be consumed by software, e.g. via Unix pipe and likes. This way, you can safely do things such as:
mytool() { conda-pack echo "DONE" }As it is now,
rescontains also those messages and the progress bar.