Hi,
On Dec/22/2020, Benny M wrote:
> I’ve ran into some unexpected behavior while testing a ModelForm with
> a MultipleChoiceField and am trying to determine if this is a bug, or
> if maybe I’m doing something out of the ordinary.
I think that I might guess what it is. If I could see the code it might
be easier.
Are you doing something like:
class SomeForm(forms.ModelForm):
some_field_options = a_dynamic_expression_that_queries_the_DB
def __init__(*args, **kwargs):
your code
So using a class variable instead of an instance variable?
Class variables are initialised on "startup" (I'm simplifying) and only
once (and might be used via __new__ on ModelFormMetaclass probably, read
and validated).
Either way, if it's not what I've guessed and you paste some code it
might help me / someone else to understand it better.
I had once a bug because of using datetime.now() in a class variable
when I wanted it the "now" that the view was used not the "now" when the
application was started up.
--
Carles Pina i Estany
https://carles.pina.cat
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/20201222153133.GA31856%40pina.cat.
