Initial go at moving into a proper packaged format ref #8

[jflasher]

I think this is in line with what was being looked for. The result is on the PyPI test server here. The package is installable via

pip install -i https://testpypi.python.org/pypi pricespaidgui

Unfortunately I don't have any familiarity with the project and haven't gone through and got it running, so I am not sure if this matches the structure that'd be needed. Any necessary packages needed for the package to run can be included via the install_requires array in setup.py.

To build a package, I'd recommend starting a new virtualenv, installing something like the following

pip install -U "pip>=1.4" "setuptools>=0.9" "wheel>=0.21"

and then running

python setup.py sdist bdist_wheel

to generate the files. Form there they can be uploaded via command line or manually to PyPI.

Let me know if this seems like the right direction.

[RobertLRead]

Thanks, Joe, I appreciate your effort.

However, I'm not sure I'm not sure this is the right direction for this repo. I hate to be ungracious, and I'm not really a python packaging expert (as you can probably tell!) but I'm not sure PyPI is correct for this repo.

In the first place, PricesPaidGUI is a website, not really a reusable software library (like request), so installing it with PyPI is convenient but tends to put it in the wrong place. This is particularly true since you have to point Apache or some other WSGI web server at the files.

Secondly, PricesPaidGUI doesn't really server any function without its sibling projects, P3Auth, PricesPaidAPI, and MorrisDataDecorator. So by itself this doesn't advance our state of operations much.

[jflasher]

No problem, I agree it seems a little weird for this to be a package. I just saw #8 and figured I'd try to point the way to how it could be done. Are the other 3 projects more discrete libraries that might fall more in line with a package? If so, they could be wrapped into packages and then included in a requirements.txt file in this project. At that point, a new person could grab everything they need with a simple pip install of the requirements.txt file (the requirements.txt can also just pull from GH repos, but that doesn't seem as elegant).

Failing all that, maybe moving towards something using Vagrant/VirtualBox would be the right setup? That'd be a nice way to give people an easy starting point to see the system in action.

[RobertLRead]

P3Auth is a stand alone library, but most of it concerns CAS
authentication, which is less used than OAuth. The other repos are also
web hosted.

I have in fact never studied Vagrant, but I suppose now I must---some sort
of virtual deployment is the right approach for this collection of code.
Let me read about it. In fact I just stood up a private instance
specifically so that the City of Hoston can evaluate PricesPaid, and it
took me 3-4 hours to get everything installed correctly. If that could be
made more efficient, it would be nice----but I intend to make that sever
public once I have removed some of the GSA branding, so that users can see
what PricesPaid does. In think that is actually more important than
improving the installation, because the mean reason to install is to see if
you want to use it, which can be partially satisfied by the demo server.

But thanks of the tip---it is difficult for me to keep up with all of the
latest technology (and I am working on 3 other projects right now.)

On Sun, Apr 6, 2014 at 2:12 PM, jflasher notifications@github.com wrote:

No problem, I agree it seems a little weird for this to be a package. I
just saw #8 #8 and figured
I'd try to point the way to how it could be done. Are the other 3 projects
more discrete libraries that might fall more in line with a package? If so,
they could be wrapped into packages and then included in a requirements.txt
file in this project. At that point, a new person could grab everything
they need with a simple pip install of the requirements.txt file (the
requirements.txt can also just pull from GH repos, but that doesn't seem as
elegant).

Failing all that, maybe moving towards something using Vagrant/VirtualBox
would be the right setup? That'd be a nice way to give people an easy
starting point to see the system in action.

Reply to this email directly or view it on GitHubhttps://github.com//pull/10#issuecomment-39675525
.

Robert L. Read, PhD
Presidential Innovation Fellow, 2013