On Sat, Aug 30, 2008 at 11:33 PM, Rodolfo <[EMAIL PROTECTED]> wrote:
>
> I tried creating a new ticket on Trac, but it didn't like me, and I
> didn't like the idea of creating "just another login account" just for
> that.
>
You don't have to create a login account. If you just fill in something
I tried creating a new ticket on Trac, but it didn't like me, and I
didn't like the idea of creating "just another login account" just for
that.
Here is what I caught reading the docs on
http://www.djangoproject.com/documentation/form_preview/
---
On "How to use
On Sat, Aug 30, 2008 at 6:52 PM, julianb <[EMAIL PROTECTED]> wrote:
> On this occasion, why not change "New in Django development version"
> remarks to "New in this version"? That makes much more sense, since
> the docs get frozen for each version, so you know now and later this
> was new in
On Aug 30, 9:31 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> The latest docs will always be at //dev/; versions frozen with
> each release will be at ///.
On this occasion, why not change "New in Django development version"
remarks to "New in this version"? That makes much more sense,
Please keep in mind the the new docs are a sort of preview release --
you'll note we've not announced 'em in any official manner -- and so
are rough around the edges. Please be patient -- I'll be cleaning
these things up by the time we push 1.0.
On Sat, Aug 30, 2008 at 12:22 PM, Fraser Nevett
Hi
I encountered 2 new problems when updating to version 1.0-beta_2-SVN-8714.
I have two applications, "kousaiconreg" and "kousaimembershipfile". The
model.py in the "kousaiconreg" app imports the class "Member" from the
model of the "kousaimembership" app.
I discovered that I got an
The new documentation site is great, but is currently lacking a search
facility. I've been working on adding an embedded Google Custom
Search, which is nearly ready and working well on my local copy.
I'll submit a patch for this to Trac shortly, but it would really help
if someone who knows
On Aug 30, 1:40 am, "Bruce Kroeze" <[EMAIL PROTECTED]> wrote:
> I'm mostly through with a drop-in replacement for the old comments, using
> the new Comment system and signals. It should be slick.
>
> When it tests out, I'll also commit the new save() parameters mentioned in
> the
Yes, it has been made optional with this syntax class CharField(*
max_length=None*[, ***options*])
This is true for all other model fields as well that were expecting
max_length parameter.
Regards,
Shihan
On Sat, Aug 30, 2008 at 10:49 AM, guoqiang qian <[EMAIL PROTECTED]> wrote:
> hi,all
>
> I
I'm mostly through with a drop-in replacement for the old comments, using
the new Comment system and signals. It should be slick.
When it tests out, I'll also commit the new save() parameters mentioned in
the backwards-incompatible page, and we should be again compatible with the
latest Django
10 matches
Mail list logo
