mbed CLI 0.7.x fixes

[screamerbg]

Fixes:

• Set default toolchain/target (if not set) only after successful compile/test/export mbed compile -t GCC_ARM -m K64F --tests should set the default toolchain and target #207
• Update the help for mbed compile --tests to point to mbed test --compile
• mbed --version shows version instead of error mbed --version #222
• mbed update --clean doesn't delete untracked files. Now it does with --clean-files switch mbed update --clean did not delete .pyc files causing error #215

[jupe]

why version number jump to 0.7.17 instead of 0.8.0? what rules you use for these numbers? at least it doesnt follow semantic versioning..

[screamerbg]

No major functionality or behavior was introduced, no refactoring etc. Only fixes and cosmetics, e.g. mbed --version

[ghost]

Application version

-ver = '0.7.13'
+ver = '0.7.17'

No major functionality or behavior was introduced. Only fixes and cosmetics, e.g. mbed —v

Given this organizations history with semver (with yotta) it makes sense to version consistently across the
organization and stick with semver in other contexts.

Major functionality aside, if minor features (ie none bug fixes) are added the minor version should be stepped.

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[screamerbg]

Nothing was pushed to PyPI after 0.7.13. The changes between 0.7.13 and 0.7.17 are exactly 4 changesets which reflect the number of issues that were fixed, not the number of commits.