Hi, Adam
Thanks for your reply.
I added limitations to GitHub.
https://github.com/Arisophy/django-compositepk-model/blob/main/README.md#limitations
For now, that's what I'm aware of.
And , I posted my blog about my implementation and opinion.
Hello Muskan,
"We're still going to be strict with what we accept - you'll need to
provide a *strong use case* for your idea and show that it would be *useful
to a majority of developers* or *significantly improve* the development of
Django itself."
This is from the wiki page
>
> because I think the number of tests inside a PR is small enough that you
> probably do not see isolation failures, but you really want to see progress
> in a PR without random failures due to isolation.
>
I think it's the opposite - most isolation problems are best detected at
the time
>
> Would we need to run “gc.collect” after each test to make it deterministic?
>
Not particularly. In CPython, most objects are deterministically deleted
when they go out of scope. Only circular references are gathered by the
garbage collector, and I think it's okay to leave them as-is - the
Hello again, I am Muskan and I have a few questions regarding GSoC 2021.
Are contributions to django/djangoproject (the tickets trac) considered in
GSoC. While the dashboard itself is mentioned on the wiki page I was
wondering if it extends to the issue tracker itself to. If so, then would
If someone wants to use the step attribute as provided by the HTML field
, she/he has to specify that using for instance
FloatField(widget=NumberInput(attrs={'step': 0.5})).
Since the HTML standard offers a step attribute on input fields of type
number,
from my point of view, this feature shall
Hi Jacob,
That sounds like a sensible feature. Do you want to open a ticket and maybe
implement it?
Cheers
Markus
On Wed, Mar 17, 2021, at 12:45 AM, Jacob Rief wrote:
> If someone wants to use the step attribute as provided by the HTML field
> , she/he has to specify that using for instance
