n jinja2? or whats on our mind? If you
> guide me with some direction then I might go for the ticket. looking
> forward to hear from you.
>
> Regards
>
> On Sunday, March 23, 2014 at 5:24:05 PM UTC+6, Christopher Medrela wrote:
>>
>> On Sunday, March 23, 2014 11:51:06 A
On Sunday, March 23, 2014 11:51:06 AM UTC+1, Gwildor Sok wrote:
>
> So, there won't be a GSoC project for this, but it would be a shame to let
> the lengthy discussion and momentum generated go to waste. Can a decision
> on this matter be made and implemented regardless of the GSoC projects?
>
I
Hello! I'm sorry for such long time without any feedback. Unfortunately, I'm
not going to send Django proposal. My original plan was to send two
proposals:
one for Django and one for Breeze (Scala numerical processing library) but I
lack time and I will focus on Breeze. Therefore, I won't have eno
The link is here: http://pastebin.com/DWjE1axV
It times only rendering -- templates are parsed and cached in the setup.
On Tuesday, February 25, 2014 8:34:14 AM UTC+1, Curtis Maloney wrote:
>
> Did I miss the link to your benchmark code?
> Does it time just rendering, or parsing also?
> --
> Sen
I've made some benchmarks. The results are:
jinja2 empty for 0.028 s
jinja2 include1.094 s
django empty for 0.435 s
django include2.134 s
Where "empty for" is an empty loop repeated 50 times:
{% for i in range_ %} {% endfor %}
And include is a similar template where the loop body
I'm sorry for such long time without any reply, but I was investigating
possible
approaches of mixing Django and Jinja2 templates.
On Sunday, February 16, 2014 1:08:49 AM UTC+1, Russell Keith-Magee wrote:
>
>
> On Sun, Feb 16, 2014 at 12:43 AM, Christopher Medrela > wrote:
>
ox means introducing dependencies. Are we
ready for this?
On Tuesday, February 11, 2014 2:07:19 PM UTC+1, Aymeric Augustin wrote:
>
> 2014-02-11 13:42 GMT+01:00 Christopher Medrela :
>
>
>> What did Armin said about Python 3 exactly?
>
>
> He wrote an extensive ar
I'm really astonished how much feedback I got!
On Sunday, February 9, 2014 1:11:19 AM UTC+1, Russell Keith-Magee wrote:
>
> On Sun, Feb 9, 2014 at 6:16 AM, Christopher Medrela
> wrote:
>
>> Hello! GSoC 2014 is coming and I'm thinking about issue to work on.
>>
Hello! GSoC 2014 is coming and I'm thinking about issue to work on.
The template system is one of the components that are of special interest
to me.
One of the major issues is that rendering templates is slow. The problem
could
be solved by compiling template to Python bytecode, but it seems to
There is a list of ideas [1] and both improving aggregates and annotations
as well as improving error messages are listed there, so I suppose these
ideas are still open.
Google doesn't allow you to submit your proposal before March 10, but the
submission is only a formality and this doesn't me
I've used autopep8 to make some additional cleanup -- see this pull
request: https://github.com/django/django/pull/1875
--
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
I was working at system check framework [1] during this holiday. I've done
some changes that will solve all problems considered in this thread.
Maybe I'm a careless kind of guy, but when I test out new versions of
> Django, reading all of the release notes is rarely the first thing that
> I do...
In order to get more attention, I've created a new thread [1].
[1] https://groups.google.com/forum/#!topic/django-developers/_sde4eoNRyQ
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emai
Hello!
This summer I'm a student of Google Summer of Code. I was working at
introducing a new system check framework (merging django-secure was a part
of
my proposal, but I didn't manage to do it due to my time overestimation).
The
project is coming to the end and there is a pull request [1] tha
>
> 4. More important changes in code:
>>
>> - Introduced RAW_SETTINGS_MODULE [1]. I use it in compatibility checks to
>>> test
>>
>> if `TEST_RUNNER` setting was overriden [2].
>>
>>
>
> Have a look at the internals of the diffsettings management command -- I'm
>> not sure RAW_SETTINGS_MODU
I've written four more tests. I've moved some of checks out of `__init__`
methods. I've changed `tag` to `register`. I've rebased against master. I've
improved documentation (added sections about filtering and silencing system
checks), but I'm still polishing it. Code is ready for final review exce
1. Progress: I've made improvements to admin checks. I've also finished
implementing filtering and silencing checks. I've rebased my branch against
master again.
2. I'm afraid that there is too little time to merge django-secure.
September 16 is
suggested 'pencils down' date, so there are only le
1. One of my questions left unanswered on the pull request [1] (I mean this
one
about documentation and `__str__` use.).
2. I've finished rewriting admin checks. I've renamed `admin_validation` to
`admin_checks`. I would like you to have a deep look at `fk_name` and
`exclude` checks [2] as well a
Progress:
- Converted `BaseCommand.verbosity` from bytestring into an unicode.
- Integrated compatibility checks.
- Deprecated "validate" command. This command delegates to "check" command
now.
Changed "check" command -- it performs all system checks, including model
validation and compatib
*Progress.*
- Deprecated `requires_model_validation` flag and `validate` method (both
`BaseCommand` members) in favour of new `requires_system_checks` flag and
`check` method.
- Finished working at `contenttypes` tests.
- Improved code thanks to Preston Holmes comments. Deleted dead code and
I'm still working at polishing after reviewing. I've deprecated
`requires_model_validation` and `validate`. I've started at adding tests for
contenttype fields: `GenericForeignKey` and `GenericRelation`.
I've updated gsoc2013-checks-review branch [1]. Now it's the same as
gsoc2013-checks branch [2
Unfortunately, I'm a bit late. I didn't suspected that polishing code after
review takes so much time. Lots of my work from last Wednesday was small
improvements, but there are some vital changes:
The API will be consistent with API of logging module or message framework.
Being consistent means th
Progress: I've implemented registering entry points. Now there is
`django.core.checks.register(callable)` function. There is no
`run_in_development` and `run_in_production` arguments. I've also rewritten
mechanism of triggering checking framework -- `BaseCommand.validate` calls
`django.core.checks.
I've created a pull request [1] to make deep review easier. I've rolled out
tests we were talking about and reverted `validate_field` -- there exist
both `check_field` and `validate_field`, the first calling the second.
[1] https://github.com/django/django/pull/1364
--
You received this messag
Progress: I've implemented manager checks.
The schedule for the next 4 weeks is:
1. Manager checks (ref 4.1.7)(done)(0.5 week).
2. Entry point registering (ref 4.1.5) & rewriting mechanism of triggering
checking framework (ref 4.1.9)(1.5 week).
3. Moving custom User model checks (ref 4.1.6)(0.
Finally, I've rewritten all model and field tests and checks. Some new tests
were written. First draft of checking framework documentation was written.
All
tests passes (at least at my computer). I've rebased my branch
(`gsoc2013-checks` [1]) against master. The branch is ready to deep review.
[1
I'm finishing making field tests green. I'm a bit late, because the schedule
says that I should finish this job by the end of the previous week. My
excuse is
that I had exams in the previous week so I couldn't focus on GSoC.
Fortunately,
I passed all exams and now I can work full time on GSoC and
Hello!
I've deleted old `gsoc2013-verification` branch. Follow the new
`gsoc2013-checks` branch [1].
[1] https://github.com/chrismedrela/django/tree/gsoc2013-checks
What did I do? I've rewritten field tests living in
`django.tests.invalid_models` package [2], inside `tests.py` file [3]. I've
ren
Hello!
**Making distinction between form validation and static validation.** I
named
the process of static checks of apps, models etc. "validation".
Unfortunately,
novices may confuse it with form validation. So I propose to rename it to
"verification". Functions/methods/classmethods (referred t
Hello!
I'm really happy that I've been accepted as a Google Summer of Code
student. I
will work at revamping validation framework and merging django-secure this
summer. I created this thread to start discussion (especially about public
API) and get some feedback as well as to share progress. Any
>
> On Mon, Apr 29, 2013 at 6:25 AM, Christopher Medrela
>
wrote:
>
> Jacob, as you said, I deleted django-updates part, but I ended with a
>
> proposal taking only 9 weeks. Did you mean also scheduling more than 6
> weeks
>
> for the first part of the propo
>
> 2. I think your proposal is a bit too big. I'd general prefer to see a
>
less ambitious proposal with a high probability of success over a high
>
risk/high reward. I'd like to see you drop the "django-updates" part
>
of the proposal, and focus on validation and django-secure. If you end
>
Thank you for your feedback. I really appreciate every comment because that
let me improve my proposal.
1. First of all, I noticed that the license of django-secure is copyright.
Google forces us to release code under one of approved license [1], so a
question to Carl Meyer: do you mind changin
I would like to participate in Google Summer of Code this year. I've
written proposal for "revamping validation functionality" idea. It's
available as a gist:
https://gist.github.com/chrismedrela/82cbda8d2a78a280a129 . Below, I'm
pasting the proposal. Feel free to criticize it.
*Table of conte
Hello, I made all tests green finally (all commits are tested under Python
2.7.3 and 3.2.3). The problem that took a few days to solve was that the
default engine should be recomputed after changing TEMPLATE_LOADERS setting
since its _template_source_loaders internal needs to be recalculated. I
Hello. I would like to report progress of my work (not too much new things,
rather cleaning and polishing), discuss some issues and propose an idea for
next Google Summer Of Code.
Progres from last time:
- Solved problem with TemplateResponse -- it receives optional keyword
argument call
Hello. I'm really astonished how fast I get feedback and I really
appreciate that. I apologize that you had to wait for my reply so long, but
I cannot push myself to stop programming and to share results. :)
I did some progress since creating this topic:
- Almost all tests doesn't rely on th
Hello everybody.
1. I'm working on ticket #17093 [1]. You can see progress of work at github
[2]. It's about rewritting django.template so it won't use global state. I
wrote this post to tell you what I did so far, what issues I deal with and
to discuss them. I hope that we will gain valuable
38 matches
Mail list logo
