Using a custom command with defined options will work quite nicely and be
much clearer. Thanks for the suggestion!
At the very least, the existing --template option shows an interesting
example of using the template engine to render arbitrary files.
On Friday, June 8, 2012 4:37:38 AM UTC-5, Jan
On 9 kesä, 13:37, Andrew Godwin wrote:
> Eugh, autogenerated python files full of imports? Plus, you'd
> potentially need more than one (for different migration versions), and I
> don't see what improvement this is over full paths, which is what Luke
> proposed, what South currently does, and it w
On 10 kesä, 10:42, Russell Keith-Magee
wrote:
> I'm not sure I see why. This looks to me like *exactly* what apps are
> designed to achieve. By way of implementation, it might make sense to
> introduce this as a 'sub app' - i.e., contrib.auth.improveduser would
> be an installable app in itself; t
On Fri, Jun 8, 2012 at 7:50 PM, Anssi Kääriäinen
wrote:
> On 8 kesä, 13:43, Russell Keith-Magee wrote:
>> That's certainly an interesting use case. However, I can think of at
>> least 2 ways it could be mitigated.
>>
>> One way would be to treat this as part of the contract of a pluggble
>> app.
