issue: is something like
>>> red=ColourObject('red','#FF')
>>> s=ContentString('%s','text/html')
>>> print s%red
red
>>> print "spam is %s."%red
spam is red.
>>> print ContentString(red,'text
filed in trac as ticket #4051
(http://code.djangoproject.com/ticket/4051)
webograph
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-
his behavior is the MultipleChoiceField (newforms/fields.py:376).
is this intended behavior or just a leftover from some earlier stage?
why isn't the boolen representation used instead? (`if self.required and
not value:` instead of `if self.required and value in EMPTY_VALUES:`)
to the new syntax as soon as python-2.4 support is dropped.
same goes for "user-space" apps, by the way: in the tutorial (3), it is
recommended to use a syntax like
>>> from mysite.polls.models import Poll
which causes problems if mysite is renamed or, more likely, the polls
ap
;,fk_field='details_id')
the problem becomes first apparent when delete()ing an A type object.
is this a valid bug or the way it has to be due to the (to me)
mysterious nature of GenericForeignKey-s?
regards
webograph
--~--~-~--~~~---~--~~
You receive
