On Sun, Jul 4, 2010 at 1:10 PM, Simon Litchfield wrote:
> For those of us using MySQL, having large tables, whilst also wanting
> queryset goodness --
> http://code.djangoproject.com/ticket/11003
>
> It goes a little something like this --
> Model.objects.filter(field=value).with_hints('my_index')
There are two types of documentation, "reference" documentation
(articles explaining all about one specific object such as slugify or
the Feed class), and "topical" documentation (articles explaining how
to do stuff like write templates).
It seems right now, django's documentation is trying to do
On Sun, Jul 4, 2010 at 12:05 PM, dffdgsdfgsdfhjhtre wrote:
> It seems right now, django's documentation is trying to do both at the
> same time. One project that does reference documentation really well,
> imo, is PHP. For example: http://us3.php.net/preg_replace Say what you
> will about PHP, but
On Jul 4, 2010, at 1:10 AM, Simon Litchfield wrote:
> For those of us using MySQL, having large tables, whilst also wanting
> queryset goodness --
> http://code.djangoproject.com/ticket/11003
>
> It goes a little something like this --
> Model.objects.filter(field=value).with_hints('my_index')
>
On Sun, Jul 4, 2010 at 2:05 PM, dffdgsdfgsdfhjhtre wrote:
> There are two types of documentation, "reference" documentation
> (articles explaining all about one specific object such as slugify or
> the Feed class), and "topical" documentation (articles explaining how
> to do stuff like write templ
Hi!
I have opened a ticket and would like some feedback on it. Do you
think it is a good idea?
Ticket description:
Allow context processors access to current version of context so that
they can change values and not just override them. This can be easily
done with another argument, context, and
On Jul 4, 2:22 pm, Flávio Amieiro wrote:
> For this kind of problem, i just grep django's code for the string I want. I
> know that not everyone likes to do this
I may be in the minority here, but I believe grepping source should
never, ever, ever be an acceptable substitution for proper
documen
On Sun, Jul 4, 2010 at 8:29 PM, dffdgsdfgsdfhjhtre wrote:
> I may be in the minority here, but I believe grepping source should
> never, ever, ever be an acceptable substitution for proper
> documentation.
>
I agree with you here. As I said, I don't think this workflow should be
imposed
on everyo
On Jul 4, 7:38 pm, Flávio Amieiro wrote:
> On Sun, Jul 4, 2010 at 8:29 PM, dffdgsdfgsdfhjhtre wrote:
>
> > I may be in the minority here, but I believe grepping source should
> > never, ever, ever be an acceptable substitution for proper
> > documentation.
>
> I agree with you here. As I said, I d
On Sun, 2010-07-04 at 10:05 -0700, dffdgsdfgsdfhjhtre wrote:
> There are two types of documentation, "reference" documentation
> (articles explaining all about one specific object such as slugify or
> the Feed class), and "topical" documentation (articles explaining how
> to do stuff like write tem
On Jul 4, 8:40 pm, Luke Plant wrote:
> Unlike PHP, we have namespaces, which means that providing a list of
> every function/class is a different matter.
So? Matplotlib has similar documentation to PHP's reference, and it's
fairly well regarded. The one thing that matplotlib doesn't do well is
th
Hi Helgi,
that's an awesome story. We share your appreciation.
Rahul and Ambrish would be really satisfied and motivated if their
ibm_db_django adapter was used in this.
thanks
Mario
On Jul 2, 4:03 pm, Helgi Borg wrote:
> Remember the Eyjafjallajökull eruption that stopped air traffic over
> p
Could a poll on the mailing lists (and djangopeople.net) be a way to
know how important for the django programmers View permission in admin
will be?
On Sat, Jul 3, 2010 at 09:36, Russell Keith-Magee
wrote:
> On Fri, Jul 2, 2010 at 7:03 PM, Helgi Borg wrote:
>> Remember the Eyjafjallajökull erup
13 matches
Mail list logo
