Re: making URL resolving/reversing gradually more flexible

Hi Sam, what's the problem with regexp = '^newitems'+SUFFIX+'$' where SUFFIX='(/|\.xml|\.json)' ? And if you need more shortcuts, there are surlex ( http://codysoyland.com/2009/sep/6/introduction-surlex/ ) and alternatives. On Fri, Nov 12, 2010 at 11:25 AM, Sam Lai wrote:

making URL resolving/reversing gradually more flexible

[First timer participating in the Django dev process, so apologies if I have missed some protocol etc.] First up, this is not about adding an alternate URL resolution/reversal method to the core; I've noticed a fair bit of resistance to that. PROBLEM: I want to make my website available via an

Django developer required

Hello My company is looking for a Django developer based in Somerset in the UK. If anyone is interested please see http://www.joinerysoft.com/en/company/job-vacancies/ Many Thanks Tom -- You received this message because you are subscribed to the Google Groups "Django developers" group.

Re: DDN: Localize anything with _(this_syntax) ?

On Thu, Nov 11, 2010 at 4:39 PM, Stephen Kelly wrote: > I have a patch to allow localizing localizable values like {{ _(foo) }}, > which I think is more convenient. It sort of mixes up the meaning of _() to > be both for translatable strings and localizable dates and numbers,

DDN: Localize anything with _(this_syntax) ?

Hi, Currently strings in templates can be translated with {{ _("foo") }} syntax. Localizing values can be done with a filter {{ foo|localize }}. I have a patch to allow localizing localizable values like {{ _(foo) }}, which I think is more convenient. It sort of mixes up the meaning of _() to

Re: Disqus API 3.0

I think you accidentally sent this to the wrong list. This is django- developers, a mailing list for discussion about the development of Django itself. Thanks, Eric Florenzano -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to

Disqus API 3.0

We have been working on a new version of the API these past couple of months, and we're nearing a public release. I wanted to take this opportunity to see if any of the heavy API users (specific needs, etc) would like to chime in with what they want to see, and possible give our docs/api testing

Re: Receipt for mail to security@ ?

> I'd argue that an autoresponder is almost exactly what we *don't* > need. An autoreponder can give the illusion of that a message has been > received when it's really just a robot going through the motions. The > worst possible situation would be an autoreponse message that says > "We're looking

Re: custom function for autoescape

Hi Luke, > First, you depend only on the name of the function - so one that shadows > a builtin filter won't be treated correctly (as you noted on the > ticket). This is true, I really hated this bit. The only thing that might work is "libraryname.filtername" if it's possible to identify exactly

Re: custom function for autoescape

On Wed, 2010-11-10 at 13:04 +0100, Will Hardy wrote: > > Reading over the discussion, I'm in the same camp as Luke. I can see > > the use case, but I see a bunch of sharp edges that will end up biting > > the user in unexpected ways. > > Thanks for dropping by :-) I think I've managed to remove

Re: Charfields and Admin and None, oh my.

On 11/11/10 01:40, Karen Tracey wrote: > > There is a way, it just requires some admin customization. See: > > http://stackoverflow.com/questions/454436/unique-fields-that-allow-nulls-in-django/1400046#1400046 Right, and you can also register a pre_save hook to fix this, but it's just ugly. > >