Re: Management of static assets

Le mercredi 22 avril 2020 17:22:02 UTC+2, Carlton Gibson a écrit : > > ... > *Not sure* how much of this we need to pull into Django itself? > compressor, say, does the whole combine and compress thing well. If we pull > that in are we going to do the same for image optimization? Or pull in >

Re: New Merger nomination.

Hello, I trust Claude to act as a Merger as described in DEP 10. I vote in favor. With apologies for the late answer! -- Aymeric. > On 21 Apr 2020, at 20:11, Andrew Godwin wrote: > > I also vote in favour of Claude becoming a Merger! > > Andrew > > On Tuesday, April 21, 2020 at 4:28:41

Re: Deadlock bug in logging? Reproducible case

This is more an issue at the file system level and the hardware not being able to keep up rather than anything Django is doing. It's the same fundamental principal for why you may turn off webserver logging to increase performance, writing to disk is expensive and so when dealing with high

Re: Deadlock bug in logging? Reproducible case

Sorry - that message was sent as a 'reply' in error - my colleague uses ajax with Django a lot and I was trying to forward this to him. Kind Regards, Dave On Wed, 22 Apr 2020 at 18:23, Brian Tiemann wrote: > Hi all, > > I was directed here after getting corroboration on #django and

Re: Deadlock bug in logging? Reproducible case

FYI Sent from my iPhone > On 22 Apr 2020, at 18:23, Brian Tiemann wrote: > >  > Hi all, > > I was directed here after getting corroboration on #django and elsewhere. > > I have what appears to be a bug in which a Django app can deadlock if you hit > it with a lot (>3) of AJAX requests

Re: [FEATURE] Allow squashmigrations to squash the whole project

Sounds great Andrew, i'm going to say this up front: 1. You're awesome, thank you for making south and migrations. 2. I'm inevitably need your help on this one, there were a lot of hacks I did because I couldn't come up with a better way. I'll get started, as a v1 to just port all the work done

Deadlock bug in logging? Reproducible case

Hi all, I was directed here after getting corroboration on #django and elsewhere. I have what appears to be a bug in which a Django app can deadlock if you hit it with a lot (>3) of AJAX requests within a short time (i.e. all triggered in parallel from a single HTML page). I have a

Re: [FEATURE] Allow squashmigrations to squash the whole project

I definitely think this is worth pursuing - the reason I didn't do it back in the day was that squashing the entire project involved solving some rather nasty dependency graph issues if there were any cycles of apps depending on models from other apps. If we can overcome that, though, and squash

[FEATURE] Allow squashmigrations to squash the whole project

This comes from a place of headaches: we're a large team, and our sprint are a month long, in that month we generate a lot of migrations, after a couple of sprints we see our tests take a real toll when running migrations, this is due to constantly adding columns/deleting columns, moving data

Re: Remove automatic date-naming of migrations (00XX_auto_YYYMMDD)

I am a little mixed on this change - the behaviour during the initial development was indeed to concatenate names like this, albeit only for adding fields or models; I thought it looked unwieldy, which is why I added the "auto" name. That said, the number is the only part that actually matters,

Re: Management of static assets

Hi David. Wowser. Good work! (A cup of tea indeed — I should have replied to the first question better ) (Inter alia) You raised five questions. These were the last three: - Should there be better support for front end JS frameworks - Should we have support for webpack - We should support

Re: Remove automatic date-naming of migrations (00XX_auto_YYYMMDD)

> I'd like to propose using this new full coverage of operation naming to remove the "auto_MMDD" behaviour +1 on this proposal. As you've noted in your blog post, I find the default auto name extremely opaque. Projects I work on normally have an internal policy to change these names to

Re: Providing inline "force_login" if "user" keyword argument provided to TestClient. calls (or TestClient.generic)

Hi Pavel I think this is a reasonable suggestion to allow tests to be written quickly. It should be noted django-webtest supports this argument already. I'm not sure it's as simple as a force_login before the request though. Take these tests:

Re: Remove automatic date-naming of migrations (00XX_auto_YYYMMDD)

I Like the idea of Claude. Asif On Wednesday, April 22, 2020 at 7:23:22 PM UTC+6, Claude Paroz wrote: > > Le mercredi 22 avril 2020 15:06:12 UTC+2, Adam Johnson a écrit : >> >> I'd like to propose using this new full coverage of operation naming to >> remove the "auto_MMDD" behaviour, and

Re: Uwsgi not sending parallel all(except one) tasks to celery

Hi! I think you've found the wrong mailing list for this post. This mailing list is for discussing the development of Django itself, not for support using Django. This means the discussions of bugs and features in Django itself, rather than in your code using it. People on this list are unlikely

Re: While executing a Celery Task , Error Occured: 'AsyncResult' object is not iterable

Hi! I think you've found the wrong mailing list for this post. This mailing list is for discussing the development of Django itself, not for support using Django. This means the discussions of bugs and features in Django itself, rather than in your code using it. People on this list are unlikely

Re: Generate JWTs with Django

Hi Claude JWT's are indeed popular for API's. I think if Django was being created "from the ground up" today, JWT's would be a no-brainer to include, so it seems reasonable to add some support. I've had a look at the PR, and yes it is indeed a small amount of code - and thanks for the

Re: Remove automatic date-naming of migrations (00XX_auto_YYYMMDD)

Le mercredi 22 avril 2020 15:06:12 UTC+2, Adam Johnson a écrit : > > I'd like to propose using this new full coverage of operation naming to > remove the "auto_MMDD" behaviour, and instead always combine > operations' "suggested migration names" up until a limit of say 60 > characters. I

Uwsgi not sending parallel all(except one) tasks to celery

Hi, Im facing issue like I'm trying to send 30 parallel tasks to the celery and trying to get back the result using apply_async() but uwsgi is sending only one task to celery and not giving back the result to python code. Thing is it is working fine with flask development server but when i

While executing a Celery Task , Error Occured: 'AsyncResult' object is not iterable

I am Using Celery to perform a task in the background on form submission. As soon as form is submitted during POST request, I have created a task to execute in the back ground using delay method. This task processes some click operations on some other web using selenium web driver and return

Re: Remove automatic date-naming of migrations (00XX_auto_YYYMMDD)

I think making it possible to customize how migration names are generated has a great value. Changing something from “auto” to some better/descriptive name has its value, but I can also see people creating their own strategies for naming migrations. I work on a project where migration names

Remove automatic date-naming of migrations (00XX_auto_YYYMMDD)

Hi djangonauts, In a blog post earlier this year I outlined my technique to prevent Django creating migration files with automatic date names. I had a lot of response with other techniques and ended up adding two more techniques to the post. It's at

Providing inline "force_login" if "user" keyword argument provided to TestClient. calls (or TestClient.generic)

Hi all, As a long time Django user, I often found the requirement to use login or force_login somewhat cumbersome. In comparison, pylons' WebTest has a user keyword argument e.g in their get method, which does that authentication inline. I am suggesting we make a call to login or force_login

Re: Generate JWTs with Django

For your information, I now added docs to the tentative patch: https://github.com/django/django/pull/12728 Claude Le 15.04.20 à 21:26, Claude Paroz a écrit : > Thanks Abhijeet for the pointer, I know there are some rather complete > JWT libs around, but my proposal is not about a complete