Hi,
I'm jumping in the discussion as I've tried - hard - to do something similar in
the past.
However, I'll second what has been said: mixins should be on the left side.
Is there a reason your code can't be similar to:
#class View(object):
#def __init__(self):
#print "View init"
cla
Sorry, I had problems to get to my google account, but finally I'm here :).
I wrote to the ticket meanwhile, but you probably not in CC, so I paste it
here, too:
Having this example:
class View(object):
def __init__(self):
print "View init"
#super(View, self).__init__()
cl
On Wednesday, October 2, 2013 1:29:10 PM UTC-4, Zev Benjamin wrote:
> What kind of additional configuration? One advantage of not specifying
> the type of the db_index_type field is that you could instantiate an object
> that encapsulates the configuration.
>
That's true. I am partial to openi
On Wed, Oct 2, 2013 at 11:16 AM, Tom Evans wrote:
> Tracking what login keys are assigned to a specific instance of an
> application is the entire purpose of configuration management. The
> reason we keep code in VCS is so that we can be assured what is
> deployed is coherent and consistent, the
What kind of additional configuration? One advantage of not specifying the
type of the db_index_type field is that you could instantiate an object
that encapsulates the configuration.
Zev
On Wednesday, October 2, 2013 1:19:31 PM UTC-4, Alex Burgel wrote:
>
> This is something that I'd also b
This is something that I'd also be interested in. For the Google App Engine
backend, you have the ability to create indexes that require more
configuration than just on/off. But I don't think a single additional field
would do the trick for my case.
Another option would be to open up the Meta c
Hi Simon,
It may be a viable idea, but looking at the code, it's not obvious to me
how it would be done. Perhaps you could provide some additional details
about what you had in mind.
Tim
On Monday, September 30, 2013 10:51:58 PM UTC-4, Simon Litchfield wrote:
>
> Contrib redirects is still a h
There's nothing that prevents anyone to track the configuration of the
environment in a VCS.
The guideline that it shouldn't be in the repository of the application
source code is not against that.
Deployment systems should be able to set-up the environment automatically,
(by generating a setti
On Tue, Oct 1, 2013 at 6:42 PM, Tino de Bruijn wrote:
> To all of you who don't see benefit in putting certain (definitely not all!)
> settings in the environment, I would like to say: try it. It will finally
> make sense that you set DJANGO_SETTINGS_MODULE in the first place. I never
> understood
