How about we do pretend like we want to remove the backends from core and do
the homework and refactor the backends to be less intertwined but keep them in
the same repo/package. Maybe that’s how we can have the best of both worlds. It
is going to be harder to motivate people to put in the work
Thanks for chiming in Adam.
I think this is too much of an ask for backwards compatibility. Lots of
> things aren't deepcopy-able, as per its docs:
>
Right. Are these the kind of objects you assign during setUpTestData
though? They could be easily moved to setUpTestCase for example.
How about
Wow, time fly. I had taken part in the promotion activity 2 years ago.
while haven't seen any progress on this topic.
Is there on any progress on this topic?
在 2016年8月17日星期三 UTC+8下午12:08:48，Alex Hill写道：
>
> Hi all,
>
> I like the plan to include PEP 484 type hinting in Django, outlined in the
> P
Hi,
On Mon, 26 Nov 2018 00:57:04 -0800 (PST)
Johannes Hoppe wrote:
> I want to address a completely different point, and that
> *innovation*. I believe that 3rd party backends could lead to more
> innovation in the Django ORM.
> Currently if you want to introduce a new feature for your database,
