python broken on source install on Fedora

```
What steps will reproduce the problem?

source install of CORE on Fedora will put the python modules into
/usr/local/lib/python2.7/site-packages/core (while most everything else in
Fedora goes into /usr/lib).

Python seemingly cannot use this directory, even if PYTHONPATH is set to point
there and sys.path shows the core directory in its path.

import core
raises "ImportError: No module named core"

Even if I put a symlink into /usr/lib/python2.7/site-packages/core to point
there, then 'core' can be imported without exception, but other modules start
to fail to import (e.g. 'core.api').

I reproduced this on core-4.6, core-4.7, and svn snapshot on a Fedora 20 x86_64
box.

When I install the Fedora RPMs, it clears the problem.

I saw some other discussion in other forums about how /usr/local/lib may not be
an ideal place for Python site-packages for Fedora. I don't know if guidance
is available somewhere about the preferred prefix for out-of-tree python
modules in Fedora.

```

Original issue reported on code.google.com by `tomh....@gmail.com` on 10 Feb 2015 at 7:10

No source files or tests are named. Reproduce a source install on Fedora and inspect where the Python modules are installed and how Python resolves them; done means both `import core` and `import core.api` work without symlinks, as they do with the Fedora RPMs.

Written by the indexing model from the issue text.