Re: Fellow Reports - August 2018
Week ending August 11, 2018 Triaged --- https://code.djangoproject.com/ticket/29647 - "Please correct the error below." when saving edit model form with inline formset and space at the end of primary key value (invalid) https://code.djangoproject.com/ticket/29653 - Using GenericRelation.related_query_name through an inherited abstract class crashes (accepted) https://code.djangoproject.com/ticket/29651 - MemoryError while deleting object with huge amount of related objects (duplicate) Reviewed/committed -- https://github.com/django/django/pull/10269 - Fixed #29616 -- Fixed createsuperuser for user models that don't have a password field https://github.com/django/django/pull/8973 - Fixed #28529 -- Fixed VariableDoesNotExist warnings in admin templates. https://github.com/django/django/pull/10274 - Fixed #29648 -- Fixed crash when using subqueries inside datetime truncation functions. https://github.com/django/django/pull/10270 - Fixed #29244 -- Prevented Paginator.count() from silencing TypeError and AttributeError. https://github.com/django/django/pull/10255 - Fixed #29623 -- Fixed translation failure of DurationField's "overflow" error message. https://github.com/django/django/pull/10281 - Fixed #29637 -- Fixed admin change form crash if the user doesn’t have the add permission to a TabularInline. -- 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/bfd2bb60-2758-4d42-abb3-c4ef3a9a42bb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: HTML5 and XHTML5 documents
Another discussion about HTML vs XHTML is https://groups.google.com/d/topic/django-developers/EdwwxxqcKVU/discussion. I think if you want to use XHTML, Django should make is possible, but as it seems the majority of projects use HTML5, I would stick to that as the default. Have you tried creating custom widget templates for XHTML? https://docs.djangoproject.com/en/stable/ref/forms/renderers/ On Sunday, August 12, 2018 at 3:16:43 PM UTC-4, Nils Fredrik Gjerull wrote: > > Den 12. aug. 2018 20:06, skrev Jon Dufresne: > > Django started adopting HTML5 features since before 2.1. I found > > changes as early as 1.11. From the release notes: > > > > https://docs.djangoproject.com/en/dev/releases/1.11/#miscellaneous > > Perhaps, but I have run my project on Django 2.0 without being affected > by it. > > > > > > The checked and selected attribute rendered by form widgets now uses > > HTML5 boolean syntax rather than XHTML’s checked='checked' and > > selected='selected'. > > > > FWIW, I prefer the concise syntax of HTML5 over XHTML and seems to be > > the de facto preferred style across much of the web. Style guides such > > as Google's recommend it. From > > https://google.github.io/styleguide/htmlcssguide.html#HTML: > > HTML5 is not a replacement for XHTML as a XML serialization. In XML > empty attributes are not allowed, so the value has to be something (even > if just en empty string). In place of using true/false the standard says > that is must be either the same as the attribute name or an empty string > (for XHTML5). This is what we are stuck with for XML serialization of > HTML5. > > I think a framework should rate compatibility over conciseness. And > adding a value to a boolean attribute I think is a very minor hassle. In > our own application code we are free to choose. > > > > > > Document Type > > > > > > Use HTML5. > > > > > > HTML5 (HTML syntax) is preferred for all HTML documents: > html>. > > > > > > (It’s recommended to use HTML, as text/html. Do not use XHTML. > > XHTML, as application/xhtml+xml, lacks both browser and infrastructure > > support and offers less room for optimization than HTML.) > > > > > > Although fine with HTML, do not close void elements, i.e. write > > , not . > > I will say that this time is the best time ever to serve pages with > application/xhtml+xml, because all browsers supports it. IE was the road > blocker for year, but since IE9 it supports it as well. The points about > infrastructure and optimization are so vague I can hardly guess what the > writer thought about. > > Se a list of the default value of the Accept header for various browsers > from Mozilla: > > https://developer.mozilla.org/en-US/docs/Web/HTTP/Content_negotiation/List_of_default_Accept_values > > > All except IE8 supports application/xhtml+xml. > > Regards > > -- > Nils Fredrik Gjerull > - > "Ministry of Eternal Affairs" > Computer Department > ( Not an official title :) ) > > > -- 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/ffacbfbc-b559-4dee-832a-7989633a61d8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Fellow Reports -- August 2018
Hi all, Calendar Week 32 -- ending 12 August. Triaged: https://code.djangoproject.com/ticket/29649 -- admin readonly_fields with unique_together raises IntegrityError (Duplicate of #13091) https://code.djangoproject.com/ticket/29643 -- Hashing list in Q objects when using __in lookup (needsinfo) https://code.djangoproject.com/ticket/29642 -- Add check for signatures of custom error views. (Accepted) https://code.djangoproject.com/ticket/29641 -- Add support for unique constraints to Meta.constraints (Accepted) https://code.djangoproject.com/ticket/29640 -- Document (deprecate?) Paginator._get_page (Accepted.) Reviewed: https://code.djangoproject.com/ticket/29653 -- Using GenericRelation.related_query_name through an inherited abstract class crashes https://code.djangoproject.com/ticket/29644 -- String representation of SearchQuery gives inaccurate results https://code.djangoproject.com/ticket/29612 -- Add prefetch_related() cache invalidation for GenericRelations https://github.com/django/django/pull/10259 -- added VSTS hosted CI https://code.djangoproject.com/ticket/28661 -- Auto-truncate indexes on MySQL when max index size is reached https://code.djangoproject.com/ticket/28598 -- BCC addresses are ignored in the console and file email backends Kind Regards, Carlton -- 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/13bce8c2-7f2b-42bf-a006-5dbf99a51ba8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to add an unsupported language in Django
Hi Deniz, Please do not cross-post your issues over several mailing lists, we are already talking about your issue in gnome-i18n. Thanks. https://groups.google.com/forum/#!topic/django-i18n/xSlv7gD7F4Y Claude Le lundi 13 août 2018 01:59:14 UTC+2, Deniz Bazan a écrit : > > Dear Django Developers, > I'm writing from Germany. I'm almost finishing developing my website but > at the end I got to a huge problem. The site should be also in Kurdish > language but this I realized isn't supported by Django. I've already looked > for help in many platforms but still didn't get any solution yet. > Does someone have already the same issue and could maybe give me a > suggestion how to solve this? It's really urgent ! > > Thank you so much > -- 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/f71efb6f-a558-4b98-890c-11a55a7e5bbc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
