Greetings,

A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location:

http://trac.chirp.danplanet.com/chirp_daily/daily-20150228

A list of the changes included in this build (since the last daily) follows:

Changes for Build #329 [Dan Smith dsmith@danplanet.com] Run pep8 in a virtualenv with a pep8==1.4.6

This makes our test runner generate a virtualenv, install pep8==1.4.6 inside, and run our pep8 test using it.

Fallout from issue #2355

[Zach Welch zach@mandolincreekfarm.com] Allow run_tests to be run from anywhere (#2343)

Find the path to run_tests, then chdir into the tests directory.

[Zach Welch zach@mandolincreekfarm.com] Fix style issues in setup.py (#2355)

This patch brings setup.py into conformance with PEP8 rules and removes it from the blacklist. It also rewrites the staticify_chirp_module routine to be more idiomatic.

[Zach Welch zach@mandolincreekfarm.com] Fix style issues (4/4) (#2355)

More low-hanging style issues.

[Zach Welch zach@mandolincreekfarm.com] Fix style issues (3/4) (#2355)

This patch fixes more low-hanging style issues. For the most part, these are all whitespace changes, but there were a handful of idiomatic changes flagged by the pep8 tool too: "x.has_key(y)" is now "y in x".

[Zach Welch zach@mandolincreekfarm.com] Fix style issues (2/4) (#2355)

This patch fixes the style in a handful of files and removes them from pep8.blacklist.

[Zach Welch zach@mandolincreekfarm.com] Fix style issues (1/4) (#2355)

This patch contains whitespace-only changes that eliminate all of the PEP8 style warnings in the CLI and GUI scripts.

[Zach Welch zach@mandolincreekfarm.com] Add pep8 checker script (#2355)

This patch adds a new script that runs the pep8 tool on the CHIRP source code files. This script is intended to be included in the repository pre-commit hook, preventing patches from causing style regressions.

The script checks a blacklist of files that are not yet compliant with the style standards, and those files will not be scanned (unless -a is given). Since no new files should ever be added to the blacklist, it should eventually shrink to empty, and the script will check the entire codebase.

The blacklist makes it safe to begin using this tool immediately, so this patch also adds a call to it from run_all_tests.sh.

[Zach Welch zach@mandolincreekfarm.com] Suppress startup debugging messages (#2347)

This patch changes the verbose startup messages to use LOG.info calls. This change is required to make the CLI remotely usable, as it's unreasonable to print so much information in that context.

I kept this separate from the last patch, because I can imagine that this might impact the automated/buildbot testing. To avoid regressions, the previous output can be generated by setting 'CHIRP_DEBUG=info' in the environment.

[Zach Welch zach@mandolincreekfarm.com] Use new logger module (#2347)

This patch chases down all references to CHIRP_DEBUG, converting the wrapped print calls to LOG.debug calls. It also eliminates a few plain DEBUG variables and a couple of other one-off variants.

[Zach Welch zach@mandolincreekfarm.com] Fix chirp.logger module (#2347)

This patch addresses some issues with the chirp.logger module in order to use it in chirpc and chirpw. It prints the version string when logging at DEBUG level.

In addition, it embraces and extends the "debug.log" support that was present in chirpw, ensuring all log messages and output end up in that file when running on Win32 or MacOS hosts. It also allows that feature to be tested on Linux by setting CHIRP_DEBUG_LOG in the environment.

[K. Arvanitis kosta@alumni.uvic.ca] [FT-60] Adding support for PMS channels.

Added special channel support for yasue programmable memory scan channels: L1 - L50 and U1 - U50.

Bug #2367