Merge lp:~mandel/ubuntuone-dev-tools/add_tests_batch into lp:ubuntuone-dev-tools
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Approved by: | Manuel de la Peña on 2010-12-20 | ||||
| Approved revision: | 18 | ||||
| Merged at revision: | 16 | ||||
| Proposed branch: | lp:~mandel/ubuntuone-dev-tools/add_tests_batch | ||||
| Merge into: | lp:ubuntuone-dev-tools | ||||
| Diff against target: |
57 lines (+52/-0) 1 file modified
run-tests.bat (+52/-0) |
||||
| To merge this branch: | bzr merge lp:~mandel/ubuntuone-dev-tools/add_tests_batch | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| dobey (community) | 2010-12-20 | Approve on 2010-12-20 | |
| Roberto Alsina (community) | Approve on 2010-12-20 | ||
|
Review via email:
|
|||
Commit Message
Added a .bat that will find the path where python is installed and will ran the tests so that lp:692494 is fixed.
Description of the Change
Added a .bat that will find the path where python is installed and will ran the tests so that lp:692494 is fixed.
- 16. By Manuel de la Peña on 2010-12-20
-
Fixed typo. Check for 2.7 before than 2.6
| dobey (dobey) wrote : | # |
The comments I mentioned previously still have some errors. It looks like you only fixed a couple of spelling errors, and not the grammar or other issues in the comments. The ones I suggested are much better to use there, as they more clearly describe what's going on.
- 17. By Manuel de la Peña on 2010-12-20
-
Use sensible comments.
| dobey (dobey) wrote : | # |
Actually, let's just rename the file to run-tests.bat instead. There's no need for the -windows, as the .bat pretty much indicates that much; and it will keep consistency with other platforms.
- 18. By Manuel de la Peña on 2010-12-20
-
Renaming script to be consistent with the linux naming currently used.

22 +:: We coudl have python 2.6 or 2.7 on windows, to in order to find which one we
23 +:: have, we will first try to get the path to 2.6, if found we will move to
24 +:: execute the tests, otherwhise we try to find 2.7 and move on
25 +SET PYTHONPATH=""
26 +:: This is very anoying, FOR /F will work differently depending on the output
27 +:: of reg which is not consistent between os (xp, 7) we have to choose the tokens
28 +:: according to the os
Spelling and grammar errors abound.
:: We could have Python 2.6 or 2.7 on Windows. In order to check availability,
:: we should first check for 2.7, and run the tests, otherwise fall back to 2.6.
:: This is very annoying; FOR /F will work differently depending on the output
:: of reg which is not consistent between OS versions (XP, 7). We must choose
:: the tokens according to OS version.
Also, as per the first comment, you should change the Python checks to look for 2.7 first, and then fall back to 2.6.