Pulp

I'm marking this as Pulp3 since practically speaking the python package layout is changing considerably with pulp3.

After a bit of research, I'm convinced that our current path is going to lead to issues later. We have a lot of setup.py files and this is going to be a problem when we go to publish on PyPI since each setup.py will be its own python package. These will all have to be published and also pip installing from a url will become pip installing from a bunch of urls. I don't know of a good reason to motivate this structure.

I believe we should have exactly 1 setup.py and it should be in the root. For example look at the way Django lays out their repository[0].

Also the Django root is a lot cleaner than the pulp root. We could have a 'pulp' folder with all of the subpackages that live at pulp.<packagehere> as subfolders of Pulp. This would both clean up the root and reduce the depth of the folder tree. We should probably file this as a separate task though.

I'm removing the documentation tag since this is a lot more than docs.

[0]: https://github.com/django/django

This issue is being purposed to capture the setup.py requirements going forward. The consolidation and reorganization is being created as a separate issue.

The documentation requirements should include:

• That Python requirements be expressed in the setup.py
• That one setup.py exists for the entire pulp package, but two additional setup.py files are needed. One for pulp.common and another for the pulp CLI.

Revised the checklist item based on discussion.