pingu_98/MrDraw
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Don't mark "can't clean" messages from setup.py clean as error

Browse source 
Might confuse users to see that marked up like an error when it's
perfectly normal for some kinds of installs simply because the
specific build folders never were created in the first place.
This commit is contained in:
Gina Häußge 2017-03-10 11:15:52 +01:00
parent b38884db63
commit 6e793c2ba3
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
src/octoprint/plugins/softwareupdate/static/js/softwareupdate.js
View file

@ -705,7 +705,10 @@ $(function() {
}
};
self._forcedStdoutLine = /You are using pip version .*?, however version .*? is available\.|You should consider upgrading via the '.*?' command\./;
self._forcedStdoutPatterns = ["You are using pip version .*?, however version .*? is available\.",
"You should consider upgrading via the '.*?' command\.",
"'.*?' does not exist -- can't clean it"];
self._forcedStdoutLine = new RegExp(self._forcedStdoutPatterns.join("|"));
self._preprocessLine = function(line) {
if (line.stream == "stderr" && line.line.match(self._forcedStdoutLine)) {
line.stream = "stdout";