I understand what you mean. Here's a proposal. Instead of removing the default test runner altogether, I can work on adding a *TESTING_BACKEND *variable in *settings.py *with possible values being *'django.testing.backends.pytest' *(default) or *'django.testing.backends.DefaultRunner'*. This way we need not compromise on the features that the default runner provides over pytest. Meanwhile I could work on some the issues pytest has by contributing to pytest-dev.
One small question- will a contribution to repositories such as *pytest-dev *or *graphene-django *count as contributions to the Django organization in GSoC? Best Diptesh PS: I am also conducting a small survey about the same. I will post the results here once I get sufficient responses. It would be interesting to see how to common public reacts to such a change. On Tuesday, December 15, 2020 at 10:56:37 PM UTC+5:30 Adam Johnson wrote: > except the first one- this can be easily solved using a pytest hook > > > It's not easy at all. I tried 4 years ago and failed to find a > satisfactory way of running the checks at the appropriate time since the > pytest lifecycle (db setup, reporting, etc.) is so different from unittest: > https://github.com/pytest-dev/pytest-django/pull/414 > > Instead they are kind of addons that'd be nice to have. >> > > That's not how we treat stability in Django. These features are necessary, > core features for the projects that use them, and we treat them as > necessary. Please read the Deprecation Policy: > https://docs.djangoproject.com/en/3.1/internals/release-process/#internal-release-deprecation-policy > > . > > I appreciate your willingness to improve things and I agree generally > pytest is a better test runner experience. But please channel some of your > energy into understanding where Django is, where pytest is, how > contributions work etc. You will get further than having a long back and > forth where you keep asserting that it would be easy to implement. > > On Tue, 15 Dec 2020 at 16:58, Diptesh Choudhuri <diptesh....@gmail.com> > wrote: > >> *Adam,* >> Thanks for your detailed feedback. >> I will be honest, I couldn't understand any of the points you mentioned >> (except the first one- this can be easily solved using a pytest hook). As >> you said, these are very rare cases indeed. As a django and pytest user for >> some time, I would have encountered atleast one of them when I wrote my >> tests. However I never have and hence I would say that these are very rare >> cases indeed. >> What I am trying to say is that if we include pytest in django core, the >> development of these features will only be accelerated. The default runner >> advantages you mentioned are not really features that are missing in >> pytest. Instead they are kind of addons that'd be nice to have. But the >> advantages that I mention of pytest over the default runner are significant >> and can tremendously improve developer experience while writing tests. >> >> Please don't think I am disregarding your points. I respect and value >> your opinions. >> >> Best >> Diptesh >> >> On Tuesday, December 15, 2020 at 10:10:06 PM UTC+5:30 Diptesh Choudhuri >> wrote: >> >>> > A case could be made along the same lines as was made for South. >>> >>> Could you please elaborate a bit on this? Maybe provide the relevant >>> tickets? I am quite new to this community. >>> >>> Thanks! >>> Best >>> Diptesh >>> >>> On Tuesday, December 15, 2020 at 10:01:03 PM UTC+5:30 >>> arvind...@gmail.com wrote: >>> >>>> A case could be made along the same lines as was made for South. >>>> >>>> Get Outlook for Android <https://aka.ms/ghei36> >>>> >>>> ------------------------------ >>>> *From:* django-d...@googlegroups.com <django-d...@googlegroups.com> on >>>> behalf of Mariusz Felisiak <felisiak...@gmail.com> >>>> *Sent:* Tuesday, December 15, 2020 9:58:56 PM >>>> *To:* Django developers (Contributions to Django itself) < >>>> django-d...@googlegroups.com> >>>> *Subject:* Re: Replace the default django test runner to a more robust >>>> testing framework (like pytest) >>>> >>>> Hi, >>>> >>>> I agree with René and Adam, pytest and pytest-django already exist, >>>> and I don't see why we should copy it to Django or change the default test >>>> runner. >>>> >>>> Best, >>>> Mariusz >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Django developers (Contributions to Django itself)" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to django-develop...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/django-developers/60a4a090-8ff5-477e-9651-db1fbf5c397bn%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/django-developers/60a4a090-8ff5-477e-9651-db1fbf5c397bn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-develop...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/39dc54fb-43e9-424f-9ca3-10938741d733n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-developers/39dc54fb-43e9-424f-9ca3-10938741d733n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > Adam > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/578b10db-0084-4d40-82dc-2a1af6aa8547n%40googlegroups.com.
