Re: Great Wall of DEP
It's worth noting that during that two-week time period the core team has been a bit preoccupied with doing a security release and followup bugfix release :) If no-one else has looked at and commented on those two DEPs within the next day or two, I will have time to do so, and will do so (and feel free to poke me if I haven't). -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAL13Cg_rg7J3c7B9%2Bmzur%3DrQLxXpvVQoj4_no9FsB_drp0mWcg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Revisiting multiline tags
Technically I'd think only core devs would vote. So neither here or there would make a diff imo. P.S.: That said I am not sure we have a formal policy on how we act on DEPs yet (or maybe I should just read DEP 001 more carefully ;)) Cheers, Florian On Wednesday, April 30, 2014 4:02:26 AM UTC+2, ted wrote: > > Now that there is a DEP, where do we voice our support (cast +1 votes)? > Here, on the DEP pull request, on the original ticket? > > T > > On Wednesday, April 16, 2014 10:14:25 PM UTC-4, Loic Bistuer wrote: >> >> On Thursday, April 17, 2014 5:47:10 AM UTC+7, Josh Smeaton wrote: >>> >>> And for the last month or so a patch has existed and feedback has been >>> requested. Performance was one of the concerns mentioned, so download >>> Curtis' patch, and test that it works for your use case. He has asked for >>> feedback a number of times. Unless you try it out, I fear that you won't be >>> seeing multi-line tags. >>> >> >> My thought exactly. >> >> I intend to review the patch, benchmark it, and work on improvements if >> need be, but that's no replacement for extensive community testing. This >> patch doesn't stand a chance unless the latter has happened since we can't >> risk breaking all the templates out there; the diff may look small, but >> it's a significant change to the parsing algorithm. >> >> Decision making in Django goes by "rough consensus and working code". The >> DEP process that Curtis started is the right way to work constructively on >> "rough consensus", but people who really want this feature need to play >> their part in coming up with "working code" and the code needs to be well >> tested to be considered as working. >> >> If you want this feature, please try the patch against your own projects >> and report your findings. The DEP is also awaiting community feedback. >> >> -- >> Loic >> >> -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/eba0e946-ced4-478f-b65d-f71e568cff57%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Revisiting multiline tags
Now that there is a DEP, where do we voice our support (cast +1 votes)? Here, on the DEP pull request, on the original ticket? T On Wednesday, April 16, 2014 10:14:25 PM UTC-4, Loic Bistuer wrote: > > On Thursday, April 17, 2014 5:47:10 AM UTC+7, Josh Smeaton wrote: >> >> And for the last month or so a patch has existed and feedback has been >> requested. Performance was one of the concerns mentioned, so download >> Curtis' patch, and test that it works for your use case. He has asked for >> feedback a number of times. Unless you try it out, I fear that you won't be >> seeing multi-line tags. >> > > My thought exactly. > > I intend to review the patch, benchmark it, and work on improvements if > need be, but that's no replacement for extensive community testing. This > patch doesn't stand a chance unless the latter has happened since we can't > risk breaking all the templates out there; the diff may look small, but > it's a significant change to the parsing algorithm. > > Decision making in Django goes by "rough consensus and working code". The > DEP process that Curtis started is the right way to work constructively on > "rough consensus", but people who really want this feature need to play > their part in coming up with "working code" and the code needs to be well > tested to be considered as working. > > If you want this feature, please try the patch against your own projects > and report your findings. The DEP is also awaiting community feedback. > > -- > Loic > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/2fb3d96b-7a31-4cb6-917d-0d92136a71c1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: On django multi tenancy
Mezzanine, a Django based CMS, has true multi tenancy. I've used it and works great. However, it's clear it's not something that should be in Django's core, for the reasons other have stated. I'm just bringing it up in case OP is still looking for something like this for his projects; not trying to restart the debate. http://mezzanine.jupo.org/docs/multi-tenancy.html https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/utils/sites.py#L12 -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/e43fd950-f8be-4fca-b963-f1ecc517d802%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.