Ok, I'll post the patches.
One further question: db.models.fields.TextField.formfield() currently returns
a CharField witout its widget set. I would have expected its widget set to
widgets.Textarea. Is this by design?
greets
Philipp
On Sun, Jan 07, 2007 at 01:15:41PM -0600, Adrian Holovat
Hi there
There's a problem with newforms with foreignkey/choicefield.
In the following example, category is a ForeignKey field:
>>> EntryForm = forms.models.form_for_model(Entry)
>>> print EntryForm.fields.keys()
['title', 'body', 'category']
>>> data = dict(title="lorem", body="lorem ipsum dol
+1 from me.
I'm german speaking, having ümläüts all over the place.
I stumbled over the following post that refers to a few tickets whose patches
proved helpful
http://maurus.net/weblog/2006/08/08/utf8-encoded-unicode-support/
greets
Philipp
On Wed, Jan 10, 2007 at 11:56:52PM -0800, Ville Sää
Hi there
I'm trying to start the design discussion needed for #3247 concerning newforms.
Currently if you add a field to your model with editable=False, e.g.
created = models.DateTimeField(editable=False)
then the field "created" isn't rendered in a form in the admin but it will
still be rende
> So I'd like to propose that we draw up some guidelines for
> contributing documentation for Django, and begin encouraging
> documentation contributions just as much as we encourage code
> contributions.
I'm not 100% sure this is the right direction.
As I found out there's lacking documentation
Hi Ivan
Thank you very much for making things very clear here.
It seems the whole issue cryes for a unification of the whole django source
before the 1.0 release, or do I misinterpret?
Do you know which parts of django still use bytecode strings?
greets
Philipp
On Sat, Jan 27, 2007 at 06:10:
> The real question, then, is what will it take to get Django unicode
> uh, "safe" (not sure if that's the best term) before 1.0. I realise
> that this looks like it's going to be fairly major to sort out, but if
> we don't then we're going to have all sorts of irritating little bugs
> like th
Hi there
The newforms documentation still lacks a paragraph about converting model to
forms and posted form data back to models/db.
There are some tickets (3247, 3257) waiting for this documentation bit to be
written so they can submit a documentation path and become part of the svn
trunk.
Is
+1
I also looked into django.contrib.admin for that
thing and wanted to reuse the code there but ended in coding it myself.
greets
Philipp
On Mon, Aug 27, 2007 at 08:40:45AM -, Iapain wrote:
>
> Introduction:
>
> Most of the time ObjectionPaginator server incomplete functionality
> beca
