Re: What do you think about unify templates feature?

2019-01-17 Thread shiva kumar
Could you please explain about it. I hadn't understood ur idea. On Thu 17 Jan, 2019 2:32 pm J. Pablo Martín Cobos Hi, > > From one year ago, I am using an own command for Django templates that > unify them. With an example it is easy to see. If I am to render for > example a template call

Re: Potential suspension of Channels development

2019-01-17 Thread Michael Martinez
Hi Andrew, We have a pretty active Django channel in our Slack group if you would like to direct all support requests there in the meantime. Many of us including myself are using Django Channels in production can help with basic support questions. Take care of yourself and thanks for

Re: Potential suspension of Channels development

2019-01-17 Thread sibasish mohanty
Hi , I also can help in maintaining the projects. On Thu, 17 Jan 2019, 11:40 p.m. Nasir Hussain Hi andrew, I can help in maintaining the projects. Kindly let me know what > are the next steps. > > Thanks > > On Thu, Jan 17, 2019, 11:07 PM Andrew Godwin >> Hi all, >> >> I'm writing to you all to

Re: Potential suspension of Channels development

2019-01-17 Thread Andrew Godwin
Hi Nasir, I'm looking for help from people with a strong history of open source maintenance and Django/Python/async contributions, since I can't really guide people through it and I need to be able to trust those who I give access to. If you think you meet that, email me personally and I'll

Re: Potential suspension of Channels development

2019-01-17 Thread Nasir Hussain
Hi andrew, I can help in maintaining the projects. Kindly let me know what are the next steps. Thanks On Thu, Jan 17, 2019, 11:07 PM Andrew Godwin Hi all, > > I'm writing to you all to update you on the current situation of Channels > and related libraries (channels-redis and Daphne) and

Potential suspension of Channels development

2019-01-17 Thread Andrew Godwin
Hi all, I'm writing to you all to update you on the current situation of Channels and related libraries (channels-redis and Daphne) and potentially ask for help. I've been the sole maintainer of these projects for quite a while and it has become unsustainable - all of my energy is taken up

Re: What do you think about unify templates feature?

2019-01-17 Thread Maciek Olko
Did you try to measure the difference in time of rendering standard and your way? Regards, Maciej czw., 17.01.2019, 10:02 użytkownik J. Pablo Martín Cobos napisał: > Hi, > > From one year ago, I am using an own command for Django templates that > unify them. With an example it is easy to see.

Re: [Looking for feedback] Make Admin raw_id_fields the default choice for FKs, or project-wide configurable

2019-01-17 Thread Santiago Basulto
Ok, sorry for the Fake News, seems like it's not so complicated to make one ModelAdmin parent class that provides this behavior. Here's a working example: from django.contrib import admin from django.contrib.admin import widgets class RawFieldModelAdmin(admin.ModelAdmin): def

Re: [Looking for feedback] Make Admin raw_id_fields the default choice for FKs, or project-wide configurable

2019-01-17 Thread Santiago Basulto
I think the proposed solution of "you can just extend/subclass ModelAdmin" doesn't work, because the fields on different models can have different names. I can't just write one global ModelAdmin and then use it for all my models, because they'll have different names for their fields. Or if it

Re: [Looking for feedback] Make Admin raw_id_fields the default choice for FKs, or project-wide configurable

2019-01-17 Thread Carlton Gibson
On Thursday, 17 January 2019 16:14:31 UTC+1, Collin Anderson wrote: > > One problem with any of the alternatives (besides making it readonly by > default) is that it requires the other model to be registered in the admin > Off-hand I don't follow you here. Can you explain. > I hope

Django 2.2 alpha 1 released

2019-01-17 Thread Carlton Gibson
We've made the first release on the way to Django's next major release, Django 2.2! With about two and a half months until the final release (scheduled for April 1), we'll need timely testing from the community to ensure an on time, stable release. Check out the blog post:

Re: [Looking for feedback] Make Admin raw_id_fields the default choice for FKs, or project-wide configurable

2019-01-17 Thread Collin Anderson
I agree that default load-all-options is an annoying default. I just ran into this problem again myself in the last few weeks. One problem with any of the alternatives (besides making it readonly by default) is that it requires the other model to be registered in the admin, which could be also be

Re: [Looking for feedback] Make Admin raw_id_fields the default choice for FKs, or project-wide configurable

2019-01-17 Thread ludovic coues
Django's admin default widget for foreign keys is a select. If you try to populate a select elements with 20,000 options, your page take at least a few seconds to load. Probably a minute or two, if it load at all. By configuring your model admin to display the foreign key as a raw_id_fields, you

Re: [Looking for feedback] Make Admin raw_id_fields the default choice for FKs, or project-wide configurable

2019-01-17 Thread Carlton Gibson
This topic has come up before. e.g. https://groups.google.com/d/topic/django-developers/md39xtT_JEM/discussion (In which Aymeric suggests something similar to Harro's suggestion here.) On Thursday, 17 January 2019 06:32:15 UTC+1, Harro wrote: > If you want it in your whole project you could

Re: [Looking for feedback] Make Admin raw_id_fields the default choice for FKs, or project-wide configurable

2019-01-17 Thread shiva kumar
actually i am new to django i am not able to understand the problem which ur dealing with? On Thu, Jan 17, 2019 at 3:33 AM Santiago Basulto wrote: > Hey folks, I was about to submit a ticket but i thought it might be better > to ask everybody for opinions on the matter first. I am running a

What do you think about unify templates feature?

2019-01-17 Thread J . Pablo Martín Cobos
Hi, >From one year ago, I am using an own command for Django templates that unify them. With an example it is easy to see. If I am to render for example a template call news.html like it: 1. news.html {% extends "base.html" %} {% block title %} {% include "inc.news.title.html"