2013/12/8 unai
> Hello,
>
> > given this approach, what if the third party app wants to self-extend
> > a django admin template for example?
>
> I'm working on an other solution that instead of relying on loader skipping
> relies on template skipping.
>
> Imagine you extend to a self-reference fr
Cool!
FWIW I built the same feature as an external app called django-overextends
some time ago, you might like to compare implementations:
https://github.com/stephenmcd/django-overextends/
https://github.com/stephenmcd/django-overextends/blob/master/overextends/templatetags/overextends_tags.py
Hi,
I am planning to participate in GSOC 2014 and i would like to contribute in
Django as it is working on my area of interest that is Python. Is anybody
working on this project. Or can any one mentor me or Guide me through this.
I forgot to mention that I am totally new to this as I have an ov
Hi!
> 1. Efficiency: If this new solution slows the compilation/find/render
> template, I dislike it
Well, if there is no self-referenced inheritance, no extra code (except for the
very same self-referenced inheritance check) is executed, so there is that.
If self-referenced inheritance is foun
On Monday 09 December 2013 14:58:34 unai wrote:
>
> > 2. This solution will complicate the template development. e.g. if a
> >
> > application overwrite the "admin/change_form.html" template and a
> > developer wants to update this template, he will have to search this
> > template in every app
On Monday, December 9, 2013 12:43:04 PM UTC+1, Goinnn wrote:
>
> 1. Efficiency: If this new solution slows the compilation/find/render
> template, I dislike it
>
Lots of "ifs" which are not really worth discussing before we run actual
benchmarks; also I think that it won't be slower since curren
> I read Pablo's concern as: If the skipping is done in each loader,
> does "recursive" self-reference work across loaders?
Uh, I didn't understand, of course you can ;-)
Imagine you are extending an app template from within a project template and
that the order of the loaders is [dirs, app]. Wel
2013/12/9 Florian Apolloner
> On Monday, December 9, 2013 12:43:04 PM UTC+1, Goinnn wrote:
>>
>> 1. Efficiency: If this new solution slows the compilation/find/render
>> template, I dislike it
>>
>
> Lots of "ifs" which are not really worth discussing before we run actual
> benchmarks; also I thi
Hi all,
I found that there was a hard coded 2 seconds limit in
StoppableWSGIServer.shutdown:
https://github.com/django/django/blob/1.6/django/test/testcases.py#L999
This causes problems on slow boxes ie. travis:
https://travis-ci.org/yourlabs/django-autocomplete-light/jobs/15177543
Can we enable
On Monday, December 9, 2013 5:18:16 PM UTC+1, Goinnn wrote:
>
> 2013/12/9 Florian Apolloner >
>
>> On Monday, December 9, 2013 12:43:04 PM UTC+1, Goinnn wrote:
>>>
>>> 1. Efficiency: If this new solution slows the compilation/find/render
>>> template, I dislike it
>>>
>>
>> Lots of "ifs" which
Just as a good example on why it's not a good idea to skip a loader:
Grappelli could most likely strongly benefit from this feature and their
preferred setup looks like this
http://django-grappelli.readthedocs.org/en/latest/quickstart.html#setup --
Having to set TEMPLATE_DIRS to the grappelli t
Hi everyone,
It's time to talk 1.7. We had a core discussion recently and I've stepped
forward to release manage 1.7, and so please direct all criticism or issues
my way! I'll be using some of my Kickstarter time to help push things
through and get a release out bang on schedule, so hopefully thin
See https://code.djangoproject.com/wiki/Version1.7Roadmap for more details.
On Monday, December 9, 2013 3:00:14 PM UTC-5, Andrew Godwin wrote:
>
> Hi everyone,
>
> It's time to talk 1.7. We had a core discussion recently and I've stepped
> forward to release manage 1.7, and so please direct all c
Hi Andrew,
Great news! Many thanks for sharing this information.
I have only one comment regarding Django timelines.
Personally, I prefer less major features per release
in order to deliver Django more frecuently
(3 releases per year maybe?).
I think Django Migrations is one of the most
wan
On Mon, Dec 9, 2013 at 8:44 PM, x13 wrote:
>
> Personally, I prefer less major features per release
> in order to deliver Django more frecuently
> (3 releases per year maybe?).
>
>
This has been suggested before, including by some core developers. The move
to using Git has helped in this regard,
On Monday, December 9, 2013 5:53:11 PM UTC-3, Andrew Godwin wrote:
>
>
>
> This has been suggested before, including by some core developers. The
> move to using Git has helped in this regard, but we can't do it that fast
> for this release as I'm moving to the USA during this release cycle
>
I also hoped that the release date will be way before the 15th of may.
Also just a question.. I currently looking forward to maybe contribute
something back to django. But I always struggle with trac it looks so
extremly messy.
I mean i try to query some unresolved, accepted queries:
https://code
Hi Christian,
On 12/09/2013 03:28 PM, Schmitt, Christian wrote:
> Also just a question.. I currently looking forward to maybe contribute
> something back to django.
Great!
> But I always struggle with trac it looks so extremly messy.
Yeah, it takes some getting used to. If you'd like help with
So, after discussions with various devs, it was recognised that one of the
issues with the 1.6 release cycle was the lack of communication with the
general community about what was happening... who was developing what,
what the hold ups were, etc.
So, I've decided to undertake the task of periodi
On Mon, Dec 9, 2013 at 8:59 PM, Sagar Ghuge wrote:
> Hi,
>
> I am planning to participate in GSOC 2014 and i would like to contribute
> in Django as it is working on my area of interest that is Python. Is
> anybody working on this project. Or can any one mentor me or Guide me
> through this. I fo
On Tue, Dec 10, 2013 at 12:52 AM, James Pic wrote:
> Hi all,
>
> I found that there was a hard coded 2 seconds limit in
> StoppableWSGIServer.shutdown:
> https://github.com/django/django/blob/1.6/django/test/testcases.py#L999
>
> This causes problems on slow boxes ie. travis:
> https://travis-ci.
Hi,
On Monday 09 December 2013 17:52:20 James Pic wrote:
> Hi all,
>
> I found that there was a hard coded 2 seconds limit in
> StoppableWSGIServer.shutdown:
> https://github.com/django/django/blob/1.6/django/test/testcases.py#L999
>
> This causes problems on slow boxes ie. travis:
> https://tra
Filling in some blanks here, because some people may not recognise who
"Curtis Maloney" is - Curtis is FunkyBob on IRC, and was the recent winner
of the Malcolm Tredinnick Memorial Prize [1]. He made the mistake of
volunteering to do this on IRC, so we've taken him up on his offer :-)
We've also s
Florian, I know that the benefits of this solution. But I see the
detriments too. I think that if we allow that a app template overwrite with
self-reference another app template the template development will be a
chaos. I thought alot about it
2013/12/9 Florian Apolloner
> Just as a good example
24 matches
Mail list logo
