Fellow Report - January 16, 2015
Triaged --- https://code.djangoproject.com/ticket/26069 - Docs for MyModel._meta.get_fields_with_model() missing info about 'is_relation' (accepted) https://code.djangoproject.com/ticket/26066 - Admin changelist could handle a table wider than the screen more elegantly (accepted) https://code.djangoproject.com/ticket/26068 - Django 1.8: KEY constraint for parent model missing in m2m [regression] (worksforme) https://code.djangoproject.com/ticket/26073 - Last-Modified http header not set to the latest last-mod in multi-maps sitemaps (duplicate) https://code.djangoproject.com/ticket/26080 - Add field.on_delete to all relational fields (wontfix) https://code.djangoproject.com/ticket/26076 - SessionBase's _hash method's variable key_salt need add a dot to be a complete class path (wontfix) Authored https://github.com/django/django/pull/5968 - Fixed #26048 -- Made admin selenium tests use implicitly_wait() https://github.com/django/django/pull/5971 - Fixed #23868 -- Added support for non-unique django-admin options in docs. https://github.com/django/djangoproject.com/pull/618 - Added CorporateMember.notes field. https://github.com/django/djangoproject.com/pull/620 - Alphabetized corporate members page. https://github.com/django/djangoproject.com/pull/622 - Added 'donation amount' to the corporate member signup form. https://github.com/django/djangoproject.com/pull/623 - Limited docs to building only if source files have changed. Reviewed/committed -- https://github.com/django/django/pull/5560 - Fixed #25684 -- Made runserver use logging for request/response output. https://github.com/django/django/pull/5951 - Fixed #25385 -- Allowed importing views.generic.View from views.View. https://github.com/django/django/pull/5967 - Fixed #26071 -- Fixed crash with __in lookup in a Case expression. https://github.com/django/django/pull/5602 - Fixed #25697 -- Made default error views error when passed a nonexistent template_name. Reviews of core dev work https://github.com/django/django/pull/5964 - Fixed #25858 -- Bound abstract model application relative relationships. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1189233b-c064-4ffd-af60-4b20d2b0f614%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: db.models.options help with a piece of code analysis.
Hi Elton, >From a quick look this branch seems to handle attributes inherited from possible `Meta` bases. e.g. class Foo(models.Model): class Meta: app_label = 'app' class Bar(models.Model): class Meta(Foo.Meta): pass assert 'app_label' not in Bar.Meta.__dict__ assert Bar.Meta.app_label == 'app' Cheers, Simon Le vendredi 15 janvier 2016 10:36:45 UTC-5, Elton Pereira de Lima a écrit : > > What's up guys! > > I am studying the core of django and I came across a piece of code that > confused me. > > > https://github.com/django/django/blob/master/django/db/models/options.py#L192-L194 > > If meta_attr is a copy of self.meta .__ dict__, then when will the marked > section will run? > > Thanks! > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/192e9289-ea1d-43c5-b711-7b9111328878%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Form field labels change proposal
It has been said before but CSS was made for this and we should not mix content with design. I'd like to see this implemented with or without the deprecation path. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/024bd636-be28-4fd3-8a6f-d1a07f88b423%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
db.models.options help with a piece of code analysis.
What's up guys! I am studying the core of django and I came across a piece of code that confused me. https://github.com/django/django/blob/master/django/db/models/options.py#L192-L194 If meta_attr is a copy of self.meta .__ dict__, then when will the marked section will run? Thanks! -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/14d213ab-679d-4199-925d-7600b55e687f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
