Le jeudi 24 avril 2014 15:10:20 UTC+2, guettli a écrit :
>
> Hello,
>
> I want to improve this method:
>
> django/forms/forms.py: Form.get_changed_data()
>
There are no get_changed_data() method currently, I suppose you meant
Form.changed_data (property).
>
> I need to have access to the old
Hello,
I want to improve this method:
django/forms/forms.py: Form.get_changed_data()
I need to have access to the old data, and would like to have a triple list
like this:
(field_name, old_value, new_value)
Code: https://github.com/django/django/blob/master/django/forms/forms.py#L415
My cur
On Wed, Apr 23, 2014 at 5:43 PM, Shai Berger wrote:
> We are limiting the breaking of backwards compatibility as much as we can.
Fair enough.
> On the contrary, my
> intuition is that people using select_related are generally aware of the form
> of generated SQL, and should expect locking as the
Hi,
Since 1.4.11/1.5.6/1.6.3 introduced the reverse regression, and it was fixed
already -- are we planning another release soon?
Thanks,
Shai.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Kamil,
I started another thread related to JS linting:
https://groups.google.com/forum/#!topic/django-developers/GUgRMnnC0dM
Here is a related pull request: https://github.com/django/django/pull/2577
I have not yet changed the code style of any J
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the information Jannis. I hadn't realized that project got
to the point of a pull request.
Personally I prefer running unit tests without LiveServerTestCase. It
seems like LiveServerTestCase should be used for functional tests (using
sele