Reverting

Reverting back to 1.1.9 state. Bugs are causing too many issues during PyCon2019 sprints.

Bug Fix - Part Two

Seems a part of my previous bug fix didn't get merged. Quite possibly due my lack of committing it... 😃

Bug Fix

There was an argument name mismatch between Click and build_bundles() for the package_folder_prefix argument.

Include `__init__.py` During mpy-cross; Include Subfolders; Modularize Package Search

• Removes the exclusion of compiling __init__.py with mpy-cross, for packaged libraries. Zero-byte files are still excluded.

• When creating the list of files to bundle, subfolders weren't traversed inside of a packaged library. This release now includes subfolders (to include subfolders in the examples folder; for now)

• Modularize Package Search

  • Adds a command line argument package_folder_prefix to use for determining which folder(s) to include with packaged libraries. This changes from an exclusive approach to an inclusive approach, while still allowing some flexibility. (could be expanded to use a list of prefixes in the future)

Folder Name Tweaks & Font File Inclusion

• Tweaks the top level folder names a little.

• Includes a standard font file for the adafruit_framebuf library. font5x8.bin will be included in the examples folders.

Re-Enable 2.x Bundles [For Now]

We're re-enabling 2.x bundle builds to allow for a softer landing on 2.x deprecation.

Updated Bundle Versions; Bug Fixes

• Version Updates:

  • Removed 2.x
  • Added 4.x

• Fixed placement of README.txt in bundle zip files

• Fixed mpy-cross build

Now Includes Library Example Files!

CircuitPython Build Tools now includes example files from each library!

Change Log:

• Folder structure was changed to include a top level folder with the same name as the .zip file.
• Examples:
  • A standalone examples bundle is now built.
  • .py & .mpy bundles now include an examples folder.
  • The example files come from each library's /examples/ folder. This allows users to quickly test devices with the documented examples; simply use import examples.<filename>. This further allows users to have an easily accessible local copy of all examples, to use as reference or build upon
  • All included example files are in the raw .py format. On memory-constrained platforms, it may be necessary to utilize mpy-cross to reduce memory impact.

Use x.x lib names but use a fixed version for mpy-cross builds

I missed that the tag value specified the CPy version.

Updated lib bundle names.

Updated lib bundle names to 2.x and 3.x from more specific version numbers to alleviate issues with users being confused about whether they were downloading the correct library.