[allura:tickets] #3905 Make an allura release on pypi

[Dave Brondsema <br...@users.sf.net>]

https://caremad.io/blog/setup-vs-requirements/ has some suggestions about managing setup.py dependencies vs requirements.txt dependencies.  Notably, using `-e .` in your requirements file (see end).  Also referenced from there is a tool to pull in your requirements.txt deps into setup.py automatically: https://pypi.python.org/pypi/pbr/#requirements


---

** [tickets:#3905] Make an allura release on pypi**

**Status:** open
**Created:** Sat Mar 17, 2012 10:22 PM UTC by Dave Brondsema
**Last Updated:** Thu Apr 18, 2013 05:49 PM UTC
**Owner:** Peter Hartmann

Goal: `pip install Allura`  To do:

* [#3883] make git & svn optional dependencies
* make setup.py use the same dependencies as requirements.txt
    * http://cburgmer.posterous.com/pip-requirementstxt-and-setuppy
    * http://stackoverflow.com/questions/4150423/can-pip-install-dependencies-not-specified-in-setup-py-at-install-time
* post AlluraTesting and ForgeWiki packages to pypi, since it is pretty hard to run Allura without them.  Maybe others, like ForgeHg, are needed too?
* provide installation instructions for this mode of installation - will be similar to README instructions, but not the same
* tag git with the release (v0.1?)


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.