Wouldn't this be easier?:
{'required': "", 'name': 'fieldname'} =>
{% for name, value in attrs.items %} {{ name }}{% if value %}="{{ value
}}"{% endif %}{% endfor %}
Tino
On Wed, Apr 9, 2014 at 11:53 PM, Gregor Müllegger wrote:
> Hi,
>
> I recently had the need to check for "value is not Tr
Hi everyone,
I was using py2exe + Django 1.3 without problems. From Django 1.4 the way
to find the commands changed and it tries to find .py files as you can see
in the find_commands() function in the file core/management/__init__.py .
When you compile Django using py2exe, your don't have .py
On Thu, Apr 10, 2014 at 7:13 AM, Antonio Francisco Martín Romero
wrote:
> Hi everyone,
>
> I was using py2exe + Django 1.3 without problems
This post doesn't belong to this list. django-dev is exclusively for
discussions about development _of_ Django.
Regards,
--
Ramiro Morales
@ramiromora
Hi everyone,
I'm trying to fix some translations in transifex but I'm waiting for 3 days
since I requested to join the pt-br group. I already sent two messages to
django-i18n and none was approved. Looking at the list, the last message is
from Feb 24. Can someone give me some help here? I would li
On Thu, Apr 10, 2014 at 9:26 AM, Bruno Ribeiro da Silva
wrote:
> Hi everyone,
>
> I'm trying to fix some translations in transifex but I'm waiting for 3 days
> since I requested to join the pt-br group.
I've just accepted you there (with my Transifex the Django project admin hat.)
--
Ramiro Mo
Thank you!
On Thu, Apr 10, 2014 at 9:49 AM, Ramiro Morales wrote:
> On Thu, Apr 10, 2014 at 9:26 AM, Bruno Ribeiro da Silva
> wrote:
> > Hi everyone,
> >
> > I'm trying to fix some translations in transifex but I'm waiting for 3
> days
> > since I requested to join the pt-br group.
>
> I've ju
Hey folks,
Django now 100% translated to pt_BR.
Thanks for the help with transifex!
On Thu, Apr 10, 2014 at 9:58 AM, Bruno Ribeiro da Silva <
bruno.dev...@gmail.com> wrote:
> Thank you!
>
>
> On Thu, Apr 10, 2014 at 9:49 AM, Ramiro Morales wrote:
>
>> On Thu, Apr 10, 2014 at 9:26 AM, Bruno Ri
A ticket has been opened asking to add HTML5 required tag in forms for the
fields which are required for database entry.
There have been several issues:
1. Is this new option going to stay or is it just transitional.
2. Is it going to be an optional feature or default behaviour.
3. Shou
On Thursday, April 10, 2014 11:19:18 PM UTC+5:30, anubhav joshi wrote:
>
> A ticket has been opened asking to add HTML5 required tag in forms for the
> fields which are required for database entry.
>
> Better wording:
"required for database entry" --> fields have *required* attribute as *True*
Hi,
thanks for your input. Unfortunatelly this would fail for int(0):
{'value': 0} =>
Gregor
2014-04-10 11:41 GMT+02:00 Tino de Bruijn :
> Wouldn't this be easier?:
>
> {'required': "", 'name': 'fieldname'} => />
>
> {% for name, value in attrs.items %} {{ name }}{% if value %}="{{ value
>
I think adding the `required` attribute but ignoring the other possible
html form validations (like `min` and `max` [1] for that are used
by the forms.IntegerField) seems a bit half-hearted.
My opinion is that having the required attribute is pretty cool, but should
come with all other possible v
On 11 April 2014 01:11, Gregor Müllegger wrote:
> Hi,
>
> thanks for your input. Unfortunatelly this would fail for int(0):
Not if you encode all values to strings before passing to the
template, so it's "0" instead of 0.
>
> {'value': 0} =>
>
> Gregor
>
>
> 2014-04-10 11:41 GMT+02:00 Tino de B
12 matches
Mail list logo
