Re: I did the tutorial successfully but couldn't find similar examples for small project (for better understanding of Django programming)

Hi! I think I found something. But it seems to be an very old example, couldn't find forms.py (and no word about where to create it) -> http://blog.e-shell.org/130 So if anybody here has an idea -> thank you! PS: "dynamic choices" seem to be the keywords here. -- You received this message bec

Re: I did the tutorial successfully but couldn't find similar examples for small project (for better understanding of Django programming)

Hi, Seems that you've on right track. Just don't chew up too big bites. I suggest that first you start mapping your real world ideas to models. Don't worry if you don't get it right at first try thats why migrations do exist. Also test driven development model could work nicely. Most of the thi

Re: I did the tutorial successfully but couldn't find similar examples for small project (for better understanding of Django programming)

Hi Jani! Am Sonntag, 18. Juni 2017 11:05:27 UTC+2 schrieb Jani Tiainen: > > Hi, > > Seems that you've on right track. Just don't chew up too big bites. > Thanks! Good to know that I'm not completely wrong :-) > I suggest that first you start mapping your real world ideas to models. > Don't wo

Re: I did the tutorial successfully but couldn't find similar examples for small project (for better understanding of Django programming)

Hi! Am Sonntag, 18. Juni 2017 10:23:26 UTC+2 schrieb softie...@gmail.com: Yes, wrong position in the thread, but I hope to reach people looking not that deep in my thread. Hi! > > I think I found something. But it seems to be an very old example, > couldn't find forms.py (and no word about whe

Re: I did the tutorial successfully but couldn't find similar examples for small project (for better understanding of Django programming)

Hi, > On 18 Jun 2017, at 14.47, softie.co...@gmail.com wrote: > > Hi Jani! > > Am Sonntag, 18. Juni 2017 11:05:27 UTC+2 schrieb Jani Tiainen: > Hi, > > Seems that you've on right track. Just don't chew up too big bites. > > Thanks! Good to know that I'm not completely wrong :-) > > I suggest

Re: Canonical way of handling multiple types of users? (Profiles vs subclassing django.contrib.auth.models.AbstractUser)

Aha, thanks for the good points. I could go down the route of using auth.groups. I'd still need a user profile to store the additional fields - are you thinking I should only have a single Profile class, and make all the fields nullable? The issue though is still - how do I integrate this with G

If you have multiple custom users - what should you set AUTH_USER_MODEL to?

Hi, Say you have multiple custom users, each inheriting from AbstractUser. The docs mention setting AUTH_USER_MODEL: https://docs.djangoproject.com/en/1.11/topics/auth/customizing/#substituting-a-custom-user-model However, what happens if you have *multiple* custom users - which would you set