For a while I've been thinking that it would be nice to have a tag so
you could re-use an expression in a template.
I did one up and put it on http://www.djangosnippets.org/snippets/132/
Is this useful enough for core?
--~--~-~--~~~---~--~~
You received this mess
On Mar 23, 10:46 pm, "Amit Upadhyay" <[EMAIL PROTECTED]> wrote:
> But the original poster gave me this idea: would it be useful to have a
> field which specifically disallows auto-complete. May be an optional
> argument for CharField? [HTML allows to do a autocomplete=off in input
> fields].
You
On Mar 24, 7:37 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> Just an idea, but maybe someone could make a new field class that
> encapsulates a hidden HTML input element (hidden by style) that has no
> label, and the developer can name it something conspicuous (like
> `email`). The end re
At the moment BaseHandler is tied to RegexURLResolver. This makes it
impossible to change the urlresolver in a convenient way. (For the
mod_python handler it's easy, just extend the mod_python handler, but
for the development server you cannot change the handler) Thus django
core code must be alte
On Thursday 15 March 2007 13:53, Jannis Leidel wrote:
> Hi list,
>
> After reading the list of mentoring organizations of Google's Summer
> of Code 2007 [1] I'm quite confused aboout not finding Django on it.
> Any ideas what went wrong?
>
> Best,
> Jannis Leidel
As far as I can see, Django is on
Just an idea, but maybe someone could make a new field class that
encapsulates a hidden HTML input element (hidden by style) that has no
label, and the developer can name it something conspicuous (like
`email`). The end result of this field could be that if any content
gets put into it, the form
Hi,
I came across thoes tickets and the corresponding thread just yesterday and as
fas as I understood the main problem is that newforms ist talking unicode
internally and at the interface to the django-ORM.
I attached my solution to this problem for django.newforms.models (diffed
against late
Hi Tristan,
Unfortunately, cx_Oracle - and therefore Django/Oracle - doesn't
support UTF-8 yet.
What works for setting your environment to Latin1/ISO8859 (with
os.environ['NLS_LANG'] = 'American_America.WE8ISO8859P1'). If you make
sure you're whole website uses ISO8859 then Oracle will translate
Hi Tristan,
Unfortunately, cx_Oracle - and therefore Django/Oracle - doesn't
support UTF-8 yet.
What works for setting your environment to Latin1/ISO8859 (with
os.environ['NLS_LANG'] = 'American_America.WE8ISO8859P1'). If you make
sure you're whole website uses ISO8859 then Oracle will translate
On Mar 23, 8:08 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Fri, 2007-03-23 at 06:48 +, Baptiste wrote:
> > That feature would be unable by default, and the user could use it
> > just for forms which didn't need to be autocompleted, eg. a comment
> > form (which can use cookies to
I tried hacking around with newforms, to implement part of my Stopping
Spambots with Hashes and Honeypots
(http://www.nedbatchelder.com/text/stopbots.html). My approach was to
create a BotProofForm class which would wrap an instance of an ordinary
form. This let me rename fields without chan
On 3/22/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
>
> On Fri, 2007-03-23 at 06:48 +, Baptiste wrote:
> > That feature would be unable by default, and the user could use it
> > just for forms which didn't need to be autocompleted, eg. a comment
> > form (which can use cookies to rememb
12 matches
Mail list logo
