Re: Ticket #5025 - truncate filter, why hasn't it been accepted?

I have a custom filter that does just this that I use in virtually every single Django project I use. It's such a common pattern that it seems almost silly not to have it included in core. It's also small enough that it won't add much in the way of maintenance. Also, there already exists a trunc

Re: Ticket #5025 - truncate filter, why hasn't it been accepted?

Will, I meant its usage on strings. Admittedly, it's probably not the best thing to do. On Wed, Dec 30, 2009 at 8:11 AM, Thomas K. Adamcik wrote: > On Wed, Dec 30, 2009 at 08:04:47AM +0200, Jerome Leclanche wrote: > > Users expect it to be called "truncate", that alone is sufficient reason. > >

Re: Ticket #5025 - truncate filter, why hasn't it been accepted?

On Wed, Dec 30, 2009 at 08:04:47AM +0200, Jerome Leclanche wrote: > Users expect it to be called "truncate", that alone is sufficient reason. > There's truncate_html, truncate_words. Designers and others who are not familiar with Python might expect the 'truncate' name. While developers experience

Re: Ticket #5025 - truncate filter, why hasn't it been accepted?

> Deprecate slice, move it to "truncate" and add the ellipsis for consistency. Slice has other uses, please don't deprecate it :-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googl

Re: Ticket #5025 - truncate filter, why hasn't it been accepted?

Users expect it to be called "truncate", that alone is sufficient reason. There's truncate_html, truncate_words. Deprecate slice, move it to "truncate" and add the ellipsis for consistency. No harm done, happy users. J. Leclanche / Adys On Wed, Dec 30, 2009 at 8:01 AM, Alex Gaynor wrote: > O

Re: Ticket #5025 - truncate filter, why hasn't it been accepted?

On Tue, Dec 29, 2009 at 11:59 PM, John Debs wrote: > > > On Dec 29, 9:08 pm, James Bennett wrote: > >> It is built in, though, it's just called "slice". The only thing >> people seem to offer to differentiate this proposal from the existing >> filter is that the proposed "truncate" would add an e

Re: Ticket #5025 - truncate filter, why hasn't it been accepted?

On Dec 29, 9:08 pm, James Bennett wrote: > It is built in, though, it's just called "slice". The only thing > people seem to offer to differentiate this proposal from the existing > filter is that the proposed "truncate" would add an ellipsis at the > end, and honestly I'm not really convinced

Re: Ticket #5025 - truncate filter, why hasn't it been accepted?

On Tue, Dec 29, 2009 at 6:15 PM, Nic Pottier wrote: > I'd be curious to hear what the reason for not accepting this patch > is.  String truncation is a pretty common task, and having it built in > seems like a no-brainer. It is built in, though, it's just called "slice". The only thing people se

Re: Ticket #5025 - truncate filter, why hasn't it been accepted?

Last time I asked on IRC, dev answer was "because nobody asked for it". Of course one could cat ~./irc/logs/django | grep -i truncate and just look at how ridiculous that statement is. Unfortunately, more often than not, the needs of the developers don't leave room for contributions from other use

Ticket #5025 - truncate filter, why hasn't it been accepted?

New to Django, but certainly not web development. After being pleasantly surprised with a lot of the available Django filters I was rather surprised not to see a string truncation filter included. A little googling shows I'm not the only one, there are tons of people writing their own filters to

Re: Thanks for all the hard work

> Thank you very much for all the hard work that you've put in to > Django.  It makes a big difference to web developers to have a > framework that is so well made, so well thought out and so well > documented.  It's a pleasure working with Django, and I'm looking > forward to working with it for t

Re: Thanks for all the hard work

I absolutely agree. I challenge anyone who has profited or benefited Django match my contribution of $100.00 or whatever you can afford. Confirmation number: 8M866720KD7X An email with your donation details has been sent to x...@.comt and you can print your donation receipt

Re: can anybody help me whats the wrong...

Hello, here is django-developers, not python-tornado ) 'chiru'tha schrieb: > Hi to all, > when i' running the helloworld example, i get this error.. But when i > remove the statements corresponds to the options.py module its > working fine.. > and one thing is when i run the same code with o

Thanks for all the hard work

I've been using Django for a bit over a year, and I have to say that I love it. It's a beautiful piece of software, and I want to pass on my gratitude. Thank you very much for all the hard work that you've put in to Django. It makes a big difference to web developers to have a framework that is

can anybody help me whats the wrong...

Hi to all, when i' running the helloworld example, i get this error.. But when i remove the statements corresponds to the options.py module its working fine.. and one thing is when i run the same code with options.py module on the other mechine its working fine.. so the problem with options.py