Possible method for managing out-of-tree Python-IVI device drivers in-tree.

Python-IVI repository changes:

• add folder for local drivers ivi/local
• add any templates such as ivi/local/__init__.py-template
• add local folder to ivi/__init__.py
• add local folder to setup.py

gitignore changes:

• ignore all files in the ivi/local folder
• negate any templated ivi/local files

this adds an 'empty' local instrument folder to python-ivi on equal footing with agilent, tek, etc, while being ignored by git.

• In-tree drivers can be copied from their standard location to the local folder and modified to meet local needs.
• Community drivers can be cloned locally then copied to the python-ivi/ivi/local folder.
• ivi/local drivers are compiled and installed along with formal drivers with python setup install
• ivi/local drivers are ignored by git status etc (ie maintained in their own repositories).

If 'python-ivi' and 'driver' topics were added to community driver repositories, then all community drivers can be found with a github search string of topic:python-ivi topic:driver or a specific driver hp3456 topic:driver

If this or something similar was thought to be of value, i would consider doing a pull request.

Regards.