Re: [RFC]GSoC 2018 Test framework improvement

Dear Josh and Rotund, Sorry for late reply, since I was surveyed for what concrete feature I want to implement. According to some ticket, such as #6712 #17365 #13873

Re: GSoC 2018

Hello, > On 18 Mar 2018, at 09:45, Manasvi Saxena wrote: > > I simply intend to create an option for the developer to use python for > templating rather than DTL or jinja. > Is Python fast compared to any other templating language? Yes. No. Jinja2 compiles to Python

Re: GSoC 2018

Hello Sir, I like theses idea less and less evertime. > > What is your usecase for a smarter rendering engine ? You can already > compute complex things in the view, store it in the rendering context and > simply display it in the template. > > The first idea was only slightly in the wrong

Re: On adding comments to database schema

Hello, My gut feeling is that I'd rather implement this in the migrations engine (your option 1) than bolt it on (the option 2). Disclaimer — I don't know the migrations engine all that well. Best regards, -- Aymeric. > On 18 Mar 2018, at 07:12, vanadium23 wrote:

Re: GSoC 2018

On Sat, 17 Mar 2018, 21:55 Manasvi Saxena, wrote: > Hello Sir, > > I'll give some background. The Django Templating Language was very >> specifically designed to NOT allow putting business logic or allow calling >> arbitrary functions in the template. Jinja2 loosened up that

Re: On adding comments to database schema

Hi, community. I've been stuck at realization, because Postgres and oracle have a syntax like comment on {table}.{column} for storing comments, so this needs to be done after table/column creation. So there are two ways: 1. Add it to post migrate signal, as for content types. But I can