Re: Requiring GitHub login for actions on Trac

On Saturday 09 August 2014 01:38:32 Curtis Maloney wrote: > For what it's worth, I can understand the opposition to requiring a GH > login [ostensibly a "coders" account] in order to make comments on tickets. > > However, if you're opinionated on a ticket you're either a coder, or feel > strongly

Re: Requiring GitHub login for actions on Trac

For what it's worth, I can understand the opposition to requiring a GH login [ostensibly a "coders" account] in order to make comments on tickets. However, if you're opinionated on a ticket you're either a coder, or feel strongly enough to overcome such a [low] hurdle. Still, options of more than

Re: [GSOC] Weekly update

On Wednesday, August 6, 2014 3:46:42 PM UTC+2, Tom Christie wrote: > > > This has been resolved by using the ImmutableList datastructure > > Looks fine. Behaviourally it's the same as a tuple, but with more explicit > errors if you attempt to modify it, which seems reasonable. > > Given that `.g

Re: The unordered_list template filter suports a format that was seen as old 7 years ago

We can use the normal deprecation cycle. I've added a link to the guide of how to do so on the ticket you created: https://code.djangoproject.com/ticket/23261 On Friday, August 8, 2014 10:21:59 AM UTC-4, ja...@eight.nl wrote: > > Are you suggesting to simply nuke the code and the mention in the

Re: The unordered_list template filter suports a format that was seen as old 7 years ago

Are you suggesting to simply nuke the code and the mention in the documentation or should there be some sort of deprecation period? Not sure what the policy of Django on this sort of thing is. On Friday, August 8, 2014 4:13:38 PM UTC+2, Tim Graham wrote: > > Feel free to submit a ticket and patc

Re: Problem with profile picture and mysql. URGENT !!

This mailing list is for the development of Django. Please direct questions about how to use Django to the django-users mailing list. On Friday, August 8, 2014 12:41:52 AM UTC-4, Swathi Rajanna wrote: > > My app does not use South as it keeps giving me django.core.management > Improperly Configu

Re: The unordered_list template filter suports a format that was seen as old 7 years ago

Feel free to submit a ticket and patch that does so. On Friday, August 8, 2014 8:49:47 AM UTC-4, Jaap Roes wrote: > > First link is wrong, was missing a zero > https://code.djangoproject.com/ticket/23260 >

Problem with profile picture and mysql. URGENT !!

My app does not use South as it keeps giving me django.core.management Improperly Configured error. Hence I have to do syncdb every time. But recently I wanted to add an image element to the previously created class in models.py but it keeps giving me unknown element image in field list. I trie

Re: The unordered_list template filter suports a format that was seen as old 7 years ago

First link is wrong, was missing a zero https://code.djangoproject.com/ticket/23260 On Fri, Aug 8, 2014 at 1:59 PM, wrote: > Today I tried to use the unordered_list template tag with a generator > (doesn't work https://code.djangoproject.com/ticket/2326). While > investigating the code I notice

The unordered_list template filter suports a format that was seen as old 7 years ago

Today I tried to use the unordered_list template tag with a generator (doesn't work https://code.djangoproject.com/ticket/2326). While investigating the code I noticed that this filter does a lot of work to support a fairly idiosyncratic form of nested lists (https://code.djangoproject.com/tick

Re: Requiring GitHub login for actions on Trac

2014-08-08 8:55 GMT+02:00 Ben Finney : > Aymeric Augustin > > writes: > > > You're right. Then just remove "to submit pull requests" from my > > argument and it still holds, simply because the vast majority of the > > Django ecosystem is on GitHub, and you can't participate meaningfully > > witho

Re: Requiring GitHub login for actions on Trac

On Fri, 2014-08-08 at 08:39 +0200, Aymeric Augustin wrote: > You're right. Then just remove "to submit pull requests" from my > argument > and it still holds, simply because the vast majority of the Django > ecosystem > is on GitHub, and you can't participate meaningfully without GitHub. > > >

Re: ORM Optimization for filtering by related existence

IIRC relation lookups don't yet use the custom lookups facility, so just writing a custom lookup might not work. We should turn the related lookups to use the new lookup system, too, but that wasn't done as the way relation lookups work is a bit special inside the ORM. As for addition of .exists l

Re: ORM Optimization for filtering by related existence

Just to be clear, are you (Curtis) suggesting that the isnull lookup should do an EXISTS when looking at a join? I don't think that's a very good idea - having that construct can be extremely useful. I think adding an __exists lookup to relationships would be a great addition - but that's where

Re: ORM Optimization for filtering by related existence

Unfortunately the problem is a bit deeper in the ORM. In general, when filtering against a multivalued relation (reverse foreign key or m2m relation) Django uses joins instead of subqueries. This can result in duplicating rows if multiple related rows match the filter. The fix recommended in the do