Determining the repository path from a model repository

Currently it is possible to look at the python code repository file tree to determine the location of the root __init__.py file and use this to set the repository path and entry point of a model.

However according to [this ](https://stackoverflow.com/questions/448271/what-is-init-py-for) post it is no longer needed in Python 3.3+. This means that there will be no method to extract the repository path and entry point of a model.

The issue is to ensure that the repository path and entry point will work both for Python 3.3+ and before. For example if an installation is using Python 3.3 and no __init__.py file exists to denote the root Python package directory can the repository path be set to null and the entry point to the full path to the .py file (with the class).

Start by tracing the model repository file-tree logic that finds the root __init__.py and sets the repository path and entry point. Check how Python 3.3+ namespace packages differ from older packages, then verify that both supported cases produce a usable repository path and entry point, including the proposed null path and full .py-file path behavior.

Written by the indexing model from the issue text.