Thanks to those who have weighed in on this thus far. I've rewritten part
of the tutorial to use a more recent ticket from the "git era" to hopefully
make things less confusing.
I think the part that has the most potential to confuse new contributors is
the introduction of PYTHONPATH. Claude s
Currently, our only built-in management signal is post-syncdb.
I propose (and, notwithstanding objection, will build) post-collectstatic.
Is this reasonable? Is there another, less invasive way to hook logic into
collectstatic?
--
Justin Holmes
Chief Chocobo Breeder, slashRoot
slashRoot: Coff
What's the use case?
Alex
On Sat, Nov 10, 2012 at 8:48 PM, Justin Holmes wrote:
> Currently, our only built-in management signal is post-syncdb.
>
> I propose (and, notwithstanding objection, will build)
> post-collectstatic.
>
> Is this reasonable? Is there another, less invasive way to hook
On Sunday 11 November 2012, Tim Graham wrote:
>
> I think the part that has the most potential to confuse new contributors is
> the introduction of PYTHONPATH. Claude suggested we could simply instruct
> users to run the tests like so:
>
> PYTHONPATH=/path/to/django ./run_tests.py --settings=tes
