how to get selectd checkboxes values in django from html?

HOBBIES Drawing Singing Dancing Sketching

Future of the development server's auto-reloading

Hello, While writing some horrific code [1] related to the development server’s auto-reloading, I realized that its design is fundamentally flawed and I think that we should reconsider it. The current implementation walks through the list of all imported Python modules, attempts to figure out

Re: FAQ on Model-View-Controller

Dan, please offer a pull request if you are able. On Saturday, August 8, 2015 at 12:03:06 PM UTC-4, Dan S wrote: > > Hello Aymeric, > > I apologize for using an aggressive tone, it is not my intent to insult > anyone, just to request that content be updated. xkcd/386 on the other > hand makes

Re: FAQ on Model-View-Controller

Hi Dan, On 8 août 2015, at 18:03, Dan S wrote: > So I humbly suggest that the wording of the FAQ be adjusted to make clear > that the "meaning" of V and C are not debatable, that templates and > template-feeding code always serve the purpose of Viewing the model, and that > Controller code can

Re: Feature idea: Add support for PostgreSQL's COPY command in contrib.postgres

+1 for this integration. This is a great feature that I've been using on projects as well. I'd love to be able to do it within django rather than hack my own sql scripts around it. The efficiency/speed up is very real. This solves the problem that when working with data where people replicate

Re: FAQ on Model-View-Controller

Hello Aymeric, I apologize for using an aggressive tone, it is not my intent to insult anyone, just to request that content be updated. xkcd/386 on the other hand makes it personal, referring to some*one*, not some*thing* :-) I suppose I intended to say that MVC is not defined within the cont

Fellow Report - August 8, 2015

Report for week ending August 8, 2015: Triaged --- https://code.djangoproject.com/ticket/17914 - reverse() does not support namespaced view references when passed a callable (won’t fix) https://code.djangoproject.com/ticket/25217 - cleanup - M2M shouldn't take a 'default' kwarg (duplica

Re: FAQ on Model-View-Controller

Hello Dan, Depending on the size and complexity of a Django project, there are two ways to implement MVC. (I’m talking of a traditional Django project, not Django-as-an-API-for-a-JS-app.) 1) Small project: the straightforward way M = models.py V = template.html C = thick views.py: most of the

Re: Deprecating old keyword syntax in DTL

We could accept a patch to remove usage of the legacy syntax in Django templates right away (I just merged the same for ifequal/ifnotequal). Does removing this improve performance for the affected tags or is the main benefit simpler code? I don't see a need for an accelerated deprecation. On Sa

Re: Deprecating old keyword syntax in DTL

For reference, the old PR is here : https://github.com/django/django/pull/1619/files Unfortunately, it doesn't rebase cleanly onto master... some very odd stuff shows up... but it wouldn't take much to regenerate this work. -- Curtis On Saturday, 8 August 2015 21:33:22 UTC+10, Curtis Maloney w

FAQ on Model-View-Controller

The Django FAQ says: *Django appears to be a MVC framework, but you call the Controller the “view”, and the View the “template”. How come you don’t use the standard names?*¶

Re: Allow custom "BoundFields" on forms and make BoundField public API

Here is a ticket for making BoundField a public API: https://code.djangoproject.com/ticket/12856 Writing that documentation seems like a good place to start. I would suggest not to move around so much code in your branch as that makes it difficult to tell what (if anything) has changed. On Satu

Allow custom "BoundFields" on forms and make BoundField public API

Hello, I'd like to propose a new feature for forms. Currently if you need a form field with some extra features you can just subclass from django.forms.Field and add all the features you need. However as soon as you're in a template and want to access the field you will get a BoundField instead

Deprecating old keyword syntax in DTL

Long ago, the keyword syntax in Django templates was: expr as name but was changed to look more like Python as: name=expr However, the facility to parse the old syntax is still there, but will silently fail unless you pass "support_legacy" to token_kwargs. In fact, it is enabled for "wi