Re: Documenting new features: built-in obsolescence of the "versionadded" tag.

On Sat, Jul 24, 2010 at 6:13 AM, Justin Lilly wrote: > While I know it comes with extra work, I think the contents of the > versionadded bits need to be reworked into the body of text. While I > can't remember any specific examples, I remember reading docs a few > times

Re: New context template tag

I'm a fan of this proposal. I find that most of the tags I build return a variable to the context rather than just rendering a string. And while a few of the tags I have built require more complexity than the decorator approach could handle, the majority of them would be trivial to make if this

Re: firebird backend for django

On 23 jul, 18:58, Alex Gaynor wrote: > On Fri, Jul 23, 2010 at 4:56 PM, maxi wrote: > > > On 23 jul, 18:42, Alex Gaynor wrote: > >> On Fri, Jul 23, 2010 at 4:30 PM, maxi wrote: > >> > Hi, > > >> > I'm

Re: Documenting new features: built-in obsolescence of the "versionadded" tag.

While I know it comes with extra work, I think the contents of the versionadded bits need to be reworked into the body of text. While I can't remember any specific examples, I remember reading docs a few times and coming across versionadded statements that were at the bottom of their section

Re: firebird backend for django

On Fri, Jul 23, 2010 at 4:56 PM, maxi wrote: > > > On 23 jul, 18:42, Alex Gaynor wrote: >> On Fri, Jul 23, 2010 at 4:30 PM, maxi wrote: >> > Hi, >> >> > I'm working on django-firebird project and doing some modifications >> >

Re: firebird backend for django

On 23 jul, 18:42, Alex Gaynor wrote: > On Fri, Jul 23, 2010 at 4:30 PM, maxi wrote: > > Hi, > > > I'm working on django-firebird project and doing some modifications > > for work with django 1.2 > > Right now, I'm trying to pass some tests running

Re: firebird backend for django

On Fri, Jul 23, 2010 at 4:30 PM, maxi wrote: > Hi, > > I'm working on django-firebird project and doing some modifications > for work with django 1.2 > Right now, I'm trying to pass some tests running the tests suit of > django trunk code and I found the next problem: > >

firebird backend for django

Hi, I'm working on django-firebird project and doing some modifications for work with django 1.2 Right now, I'm trying to pass some tests running the tests suit of django trunk code and I found the next problem: django is trying to execute this sql: SELECT "AGGREGATION_BOOK"."PRICE",

Re: Documenting new features: built-in obsolescence of the "versionadded" tag.

On Fri, Jul 23, 2010 at 9:37 AM, Jeremy Dunck wrote: > I think maybe the rendering can just be altered to ignore tags with > the old values? Actually, I think I'd rather just remove them -- plenty of people (including me) read the docs in plain text, and the "versionadded" is

Re: Documenting new features: built-in obsolescence of the "versionadded" tag.

That would be also my intend. We could keep the tags in the documentation but could stop the output in the HTML generation. 2010/7/23 Jeremy Dunck : > On Fri, Jul 23, 2010 at 11:18 AM, Tobias McNulty > wrote: >> I agree.  It's a little odd seeings

Re: memcached-based-cache - timeout=0 does not work as intended by memcached

On Fri, Jul 23, 2010 at 8:17 AM, Tobias McNulty wrote: > The only concern in that ticket seems to be that 0 means different things > for different cache backends. > There may have been some effort towards making them all behave the same when > 0 is passed. > Personally I

Re: Documenting new features: built-in obsolescence of the "versionadded" tag.

On Fri, Jul 23, 2010 at 11:18 AM, Tobias McNulty wrote: > I agree.  It's a little odd seeings things flagged "New" that have been > around since 1.0.  I also like your proposal of removing the notes for > unsupported versions. > Tobias I think maybe the rendering can just

Re: Documenting new features: built-in obsolescence of the "versionadded" tag.

I agree. It's a little odd seeings things flagged "New" that have been around since 1.0. I also like your proposal of removing the notes for unsupported versions. Tobias On Fri, Jul 23, 2010 at 12:06 PM, richardbarran < richardbar...@googlemail.com> wrote: > Hi everybody, > The Django

Documenting new features: built-in obsolescence of the "versionadded" tag.

Hi everybody, The Django documentation places a strong emphasis on highlighting new/ changed features with lines such as: "New in Django 1.0: Please, see the release notes" Such comments are a useful mental reminder when scanning through the docs, they do however have one downside: built-in

Re: memcached-based-cache - timeout=0 does not work as intended by memcached

The only concern in that ticket seems to be that 0 means different things for different cache backends. There may have been some effort towards making them all behave the same when 0 is passed. Personally I prefer the approach of not messing with the value at all, and passing it straight to the

Re: Python Sort

Ok, I was registered already in django-users, but suddenly was gotten out. Why? So I decided to break the rule. On Jul 23, 4:00 pm, Karen Tracey wrote: > Please don't cross-post the same message to both django-users and > django-developers. This question belongs on

Re: intcomma ini django admin

Please ask questions about using django on django-users. The topic of this list is the development of Django itself. Karen -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: Python Sort

Please don't cross-post the same message to both django-users and django-developers. This question belongs on django-users. Karen -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

intcomma ini django admin

Hi there, Im a new django guy here so apology if i am asking a stupid question. Can you comma separate an integer field in the admin interface for example 1 -> 1 10 -> 10 100 -> 100 1000 -> 1,000 I know intcomma does that but how do you do that in admin Thanks very much in advance -- You

Python Sort

Hi everybody, I have 3 models: built-in User model, class Project(models.Model): author = models.ForeignKey(User, verbos_name=_('Author'), related_name='projects') title = models.charField(_('Title'), max_length=150) class Vote(models.Model): project = models.ForeignKey(Project,