Re: i am using angular2 as frontend and django as backend. i am getting error zone already loaded.

You shouldn't use this mailing list for that, try django-users@ instead. Also, your problem is probably not related to Django, > On 18 Jul 2017, at 09:24, Shivam Khare wrote: > > Uncaught Error: Zone already loaded. > at :25:15 > at :638:3 > at

Re: Django 2.0 Python version support (Python 3.6+ only?)

> I do not think this matters, first off there is no commitment from our side > on type hinting or anything. We do not have any DEP or something related and > didn't even discuss if we actually want type hinting. Personally I am kinda > against it anyways, since it clutters the code for not

Re: No 'Content-Type' header in response

es them. Do I need to do anything to fix those tests in my PR? Merging felixmm's PR in my fork doesn't seem right. > On 27 Dec 2016, at 06:36, roboslone <robosl...@gmail.com> wrote: > > Oh, nevermind. Instructions are attached to the ticket. I'll start to work on > this. >

Re: No 'Content-Type' header in response

Oh, nevermind. Instructions are attached to the ticket. I'll start to work on this. > On 27 Dec 2016, at 06:33, roboslone <robosl...@gmail.com> wrote: > > So how can I help resolve this? Should I just fork Django on GitHub and make > a pull-request? > >> On 26

Re: No 'Content-Type' header in response

proscribed. > > Any metadata (I.e. headers) are about the resource just accessed... So a > Content-Type would, IMHO, be acceptable but not essential. > > > > On 26 December 2016 9:47:02 PM AEDT, roboslone <robosl...@gmail.com> wrote: > Thanks, that was an old s

Re: No 'Content-Type' header in response

Thanks, that was an old setting in Mail.app =/ I've made a pull-request to DRF: https://github.com/tomchristie/django-rest-framework/pull/4768 But it seems to me that fixing it in Django would be more appropriate. On the subject

Re: Simulating timeouts on client with django.test.client.Client

г., 19:59:40 UTC+3 пользователь roboslone написал: > > Hi! > > I'm trying to simulate timeouts on client to test my app's behaviour with > requests, that take too much time. I want to use Django's test client for > that and supply timeout arg for each request (like in req