I'm sorry you've seized the opportunity to use my effort to put a little
joy and humor in my message to push me on the slope, sorry that it's been
misinterpreted and that I just don't understand at all your technical
explanation. I guess there is always that risk.
Best
James
Le 7 avr. 2017 10:43 P
Tobias, Adam, I have "imagined" you this dialogue where you're helping
people deploy an open source citizen lobbying tool in Django in an NGO was
not to make you look bad of course, the intention was rather the inverse of
that. This situation, and exact dialogue, I have actually had, see the
source
Usually people tell me that type(self) is better than self.__class__, so
you might prepare to change that too.
But yeah, it seems like a very reasonable change to me, reading lists of
indistinct have always required extra steps to figure out
what models they are.
Thanks for your effort,
Best
I have no idea what is the best way, just say that comment. this is the
original PR
https://github.com/django/django/commit/d2a26c1a90e83dabdf3d67ceec4d2a70fb86
I think you should submit the PR to change the __str__ method, and maybe
open a new discussion regarding __repr__
sexta-feira, 7 d
just saw that __repr__ is now under discusion here
https://groups.google.com/forum/#!topic/django-developers/UNKFMg6DO5s
sábado, 8 de Abril de 2017 às 17:06:05 UTC+1, Marco Silva escreveu:
>
> I have no idea what is the best way, just say that comment. this is the
> original PR
>
> https://github
going in the python docs we find this
> If at all possible, this should look like a valid Python expression that
> could be used to recreate an object with the same value (given an
> appropriate environment).
so maybe something that returned ModelName(field1=value1, field2=value2
...) where fi
tl;dr
I'm not debating deployment here: my automated deployments are fine
the way it is today: I love linux and env vars, shells and subshells
and so on.
I'm /reporting/ that users have been fighting the lack for
DJANGO_SETTINGS_FILE for as long as I can remember.
In many case, they loose the fi
I just made a pull request.
https://github.com/django/django/pull/8336
(1) is my first choice, pk=1 is my second choice. I'd be fine with either.
On Sat, Apr 8, 2017 at 12:08 PM, Marco Silva
wrote:
> just saw that __repr__ is now under discusion here
> https://groups.google.com/forum/#!topic/dj
On Sat, Apr 8, 2017, James Pic wrote:
>I'm sorry you've seized the opportunity to use my effort to put a little
>joy and humor in my message to push me on the slope, sorry that it's been
>misinterpreted and that I just don't understand at all your technical
>explanation. I guess there is always t
Triaged
---
https://code.djangoproject.com/ticket/28011 - Correct Field.hidden docs
regarding what fields are hidden (created)
https://code.djangoproject.com/ticket/28027 - UTF-8 in help_text in
models.ManyToManyField doesn't work anymore (invalid)
https://code.djangoproject.com/ticket/
10 matches
Mail list logo