behavior: Use #!/usr/bin/env python to call python
For tools that are intended to be executed make sure python2 is called
via the current environment rather than expect the correct python to
always be located at /usr/bin/python.
Note: several tools were already using #!/usr/bin/env - this only makes
the style uniform - and updates the docs with this convention
behavior: Use #!/usr/bin/env python to call python
For tools that are intended to be executed make sure python2 is called
via the current environment rather than expect the correct python to
always be located at /usr/bin/python.
Note: several tools were already using #!/usr/bin/env - this only makes
the style uniform - and updates the docs with this convention
Note: python2 is being specified. As tools are verified to run
regardless of version - this could be changed to python
behavior: Use #!/usr/bin/env python to call python
For files that are intended to be executed make sure python is called
via the current environment rather than expect the correct python to
always be located at /usr/bin/python.
Note: several tools were already using this convention - this only makes
the style uniform - and updates the docs with this convention
behavior: Use #!/usr/bin/env python to call python
For tools that are intended to be executed make sure python2 is called
via the current environment rather than expect the correct python to
always be located at /usr/bin/python.
Note: several tools were already using #!/usr/bin/env - this only makes
the style uniform - and updates the docs with this convention
Note: python2 is being specified for one tool that is not yet python3 ready
behavior: Use #!/usr/bin/env python to call python
For tools that are intended to be executed make sure python2 is called
via the current environment rather than expect the correct python to
always be located at /usr/bin/python.
Note: several tools were already using #!/usr/bin/env - this only makes
the style uniform - and updates the docs with this convention
Note: python2 is being specified. As tools are verified to run
regardless of version - this could be changed to python
behavior: Use #!/usr/bin/env python to call python
For files that are intended to be executed make sure python is called
via the current environment rather than expect the correct python to
always be located at /usr/bin/python.
Note: several tools were already using this convention - this only makes
the style uniform - and updates the docs with this convention
tests: remove executable bit on test_net, so it runs, and fix it.
The test_user_data_normalize and test_net files had gotten
the executable bit set, and thus are skipped by nose by default.
We could set run with the --exe flag, but they should not have
gotten this way.
Other changes here:
* replace TempDirTestCase with CiTestCase, which has some nice
tmp_dir() and tmp_path() functions. Going forward the intent
is to have CiTestCase be the base test case for tests.
* test_net: switch to CiTestCase and fix usage that was
silently broken, because of exe bit.
* populate_dir: return the list of files that it writes rather
than having no return value.
* CiTestCase:
* support tmp_path("foo") that returns a full path to 'foo'
under a tmpdir.
* add tmp_dir() to get a temp dir and clean up.
