Hi,
I have been updating my proposal and as the deadline is friday Your
feedback will help me to make it better in technical point of view
https://gist.github.com/auvipy/1da0d96f826bd8da4d47
Regards
--
You received this message because you are subscribed to the Google Groups
"Django develope
Hi Alex,
On Thu, Mar 26, 2015 at 7:03 AM, Alexander Patel <
alexanderpa...@college.harvard.edu> wrote:
> Hello, all,
> My name is Alex Patel, and I am an undegraduate at Harvard College in the
> United States studying mathematics and philosophy. I intend to submit a
> proposal to work on Django's
Hello, all,
My name is Alex Patel, and I am an undegraduate at Harvard College in the
United States studying mathematics and philosophy. I intend to submit a
proposal to work on Django's URL dispatch mechanism for this year's Google
Summer of Code, and am posting to solicit any feedback, commen
In the dicts produced by a values query like that, what key would the
result be found under? The full lookup string i.e. 'pub_date__month'?
On Thu, Mar 26, 2015 at 2:36 AM, Anssi Kääriäinen
wrote:
> There remains a bit of work to do to make transforms usable everywhere in
> the ORM. The example
Maybe .values(month='pub_date__month') could work? Otherwise the month
would be the full lookup string.
On Wednesday, March 25, 2015, Alexander Hill wrote:
> In the dicts produced by a values query like that, what key would the
> result be found under? The full lookup string i.e. 'pub_date__mont
There remains a bit of work to do to make transforms usable everywhere in the
ORM. The example should work with just .values('pub_date__month').annotate(...)
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
Transforms are just single argument expressions available using lookup strings.
The biggest complication is that Transforms have slightly different API to
expressions.
I don't see a reason why transforms couldn't be a special case of expression.
There are some API incompabilities, but they shou
2015-03-25 17:21 GMT+01:00 Asif Saifuddin :
> lookign for some feedback from you about my proposal idea
>
> its still on going to improve my proposal and im working on it
> https://gist.github.com/auvipy/1da0d96f826bd8da4d47
>
I read it when you first posted it, but I don't have constructive feed
Hi Aymeric,
lookign for some feedback from you about my proposal idea
its still on going to improve my proposal and im working on it
https://gist.github.com/auvipy/1da0d96f826bd8da4d47
On Wednesday, March 25, 2015 at 7:45:39 PM UTC+6, Aymeric Augustin wrote:
>
> 2015-03-25 14:40 GMT+01:00 Hars
Hi Thomas,
On 03/25/2015 03:37 AM, Thomas Güttler wrote:
> Up to now the validation/cleaning of a attribute can not access the
> value of an other attribute.
>
> The work around is to override the clean() method of the form/model.
>
> A team mate and I talked about it, and we asked ourself, if
>
Hi Varun,
On 03/24/2015 07:18 PM, Varun Sharma wrote:
> I've been writing this proposal from past few days. After going through
> the pycon talks of Carl Meyer and Julien Phalip on Django's testing
> framework and working on the test framework from last 2 months, I have
> drafted some improvements
I have updated the proposal with what I'm planning to acheive in the
program and updating with my analysis and plans to acheive the goal. still
in draft and am editing according the goal I wanted to acheive/implement in
this project proposal.
--
You received this message because you are subsc
Great proposal and I'd love it on forms. I'm not sure about models, though.
I always use forms for sanitization.
On Wednesday, 25 March 2015 10:37:43 UTC+1, guettli wrote:
>
> Up to now the validation/cleaning of a attribute can not access the
> value of an other attribute.
>
> The work around
There are times when I've definitely wanted this feature. Particularly,
when multiple fields on a form have this type of constraint. Putting all
the logic in the clean method gets convoluted.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Con
Ok! Thanks :)
On Wednesday, March 25, 2015 at 7:37:55 PM UTC+5:30, Aymeric Augustin wrote:
>
> 2015-03-25 14:48 GMT+01:00 Harsh Vardhan Ladha >:
>
>> Thanks for quick reply. Can you help me to decide whether its good
>> project for GSoC or not? and to which Mentor I can submit its proposal if
>
2015-03-25 14:48 GMT+01:00 Harsh Vardhan Ladha :
> Thanks for quick reply. Can you help me to decide whether its good project
> for GSoC or not? and to which Mentor I can submit its proposal if Django
> community will not accept it?
>
This isn't our choice. It's one of the rules of GSoC. It also
Hi Aymeric,
Thanks for quick reply. Can you help me to decide whether its good project
for GSoC or not? and to which Mentor I can submit its proposal if Django
community will not accept it?
On Wednesday, March 25, 2015 at 7:15:39 PM UTC+5:30, Aymeric Augustin wrote:
>
> 2015-03-25 14:40 GMT+01:0
2015-03-25 14:40 GMT+01:00 Harsh Vardhan Ladha :
> I am planning to develop Django based Management Information System for
> Institutes to manage their Marks Entry System and Grade Card generation
> system efficiently.
>
Hi Harsh,
GSoC only covers the development of Django itself. Projects that
I am planning to develop Django based Management Information System for
Institutes to manage their Marks Entry System and Grade Card generation
system efficiently.
I have already developed the same in PHP-MySQL but the code is very robust
and the framework is not good and Highly secure as it wi
>
> Just to be clear, are you suggesting support for this be a part of my
> change? Personally, I see this feature as orthogonal to the transform
> refactoring. Seeing as it doesn't work with the built-in lookups nor
> transforms there should be little BC concerns.
>
No, I was just wondering
On Tue, Mar 24, 2015 at 9:24 PM, Josh Smeaton wrote:
> Hi,
>
> Firstly (and least importantly) opening a PR makes it a lot easier to review
> code, especially when there are lots of commits. A [WIP] pull request is
> common and useful. If you get a chance, you should open one with this
> change.
>
FWIW I put a rough patch together awhile ago (I can't find it or the
discussion unfortunately) that attempted to make Transforms usable as
expressions.
They share partial APIs but not the full set which made that first attempt
quite messy/hacky. I'm not aware of any reasons that they couldn't be
Hi list,
The thread about reimplementing the date-based lookups[1] reminded me of
something that was bugging me a couple of days ago.
There's some overlap between Funcs (of arity 1) and Transforms. They seem
to fundamentally do the same thing – wrap an expression in some arbitrary
SQL – but wi
Up to now the validation/cleaning of a attribute can not access the
value of an other attribute.
The work around is to override the clean() method of the form/model.
A team mate and I talked about it, and we asked ourself, if
a two phase cleaning would help here.
Our idea:
- The first clean p
Hi Josh,
With a suitably-defined Month function your example could be:
sales_per_month = Model.objects.annotate(month=Month(F('mydate'))).values(
'month').Aggregate(sales=Sum('sale'))
ISTM there's a bit of overlap between Func and Transform that could be
cleared up - I'll start a new thread abo
Hi
I am ZAFACK Billy student at National Advanced School Of Engineering
Yaounde, Cameroun.
I have gone through your ideas page and am interested in some of your
project ideas.
I am late but I nevertheless hope to work with you if possible.
I admire the work you are doing here.
Thanks for having
Hi,
We're still running Oracle and GIS. Though we do have built custom
backend based on Django GIS backend - mainly to have support for
Oracle XE, 3D functionality and in general to make it faster.
It's currently closed source but we're working on to open source it
in hope that it could interest
27 matches
Mail list logo
