For global constants, I would second the strategy that Mike outlined, and rename your constants in a more specific way, such as TASK_CANCELLED, TASK_COMPLETE, etc. unless of course CANCELLED can apply to more than just tasks.
The use of a separate class to store such constants is of course viable, but seems like a bit of unnecessary complication if all it does is hold values. I wouldn't recommend it unless the class had other purposes such as returning computed values based on those stored constants. I usually store model choices directly in the model, since they don't generally apply anywhere else. Whatever you do, try to keep it consistent. -James On Feb 23, 2015 12:07 AM, "Mike Dewhirst" <mi...@dewhirst.com.au> wrote: > On 23/02/2015 5:23 PM, Frankline wrote: > >> Hi all, >> >> I am getting confused regarding the use of constants and would be keen to >> know how the rest of you handle constants in your models. Ofcourse I could >> handle it easily similar to how it has been handled here: >> https://docs.djangoproject.com/en/1.7/ref/models/fields/# >> django.db.models.Field.choices >> >> > I have many many constants which are used across a number of modules and > apps. > > I store them in the __init__.py file of the namespace in which they are > used. Sensible naming of constants is vital of course and I'm careful to > store them alphabetically so I can find them easily enough scrolling > quickly through the file. > > At the top of my modules I say ... > > from <namespace> import CONST1, CONST2 etc > > Works for me > > Mike > > But I wanted to put the constants in a separate class on their own. This >> is >> what I hav so far: >> >> models.py >> >> class TaskStatus(models.Model): >> >> CANCELLED = 0 >> REQUIRES_ATTENTION = 1 >> WORK_IN_PROGRESS = 2 >> COMPLETE = 3 >> >> STATUS_TYPES = ( >> (CANCELLED, 'Cancelled'), >> (REQUIRES_ATTENTION, 'Requires attention'), >> (WORK_IN_PROGRESS, 'Work in progress'), >> (COMPLETE, 'Complete'), >> ) >> >> status = models.IntegerField(choices=STATUS_TYPES, >> default=REQUIRES_ATTENTION) >> class Task(models.Model): >> status = models.ManyToManyField(TaskStatus, >> default=TaskStatus.REQUIRES_ATTENTION) >> >> >> In my case, a Task can have one or more TaskStatus. I do not wish to store >> the TaskStatus in the database since they are simply constants. >> >> Does anyone have a better way of how I can approach this? >> >> > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-users/54EADFC3.3020301%40dewhirst.com.au. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2Be%2BciVgDVT2vreL41GjKBUV5MmxDWhwMWSM8Pg92-YCeNMrng%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
