kubiku wrote:
> May I suggest using word "stable" instead of final? While "final" is
> great mood improver for internal django developers, "stable" gives
> stronger message to django users and especially their bosses. And
> brings more assurance that it means what it means. Final is, well,
> some
Karen Tracey wrote:
> We've had at least three people run into a problem (#9090) after
> installing 1.0 over an old level. Now, we do document that before
> installing you should remove any old level. But I find the results when
> you don't rather odd. It's not just old files renamed/deleted
skyrim wrote:
> I just wanted to notify you that the simple login template example
> is completely messed up:
> http://www.djangobook.com/en/1.0/chapter12/
well, HTML-wise, it isn't *that* messed up.
> . single quotes used instead of double quotes in opening 'form' tag
HTML attributes can use
Joost Cassee wrote:
> Thanks for all the great info. Usually articles refer ''.join(...) as
> the fastest concat operation, but it won't do type coersion of course.
> I was interested whether there was a Django standard for this sort of
> thing. In any case the '+' operator is discouraged by all.
Ludvig Ericson wrote:
>> In general, expect DNS hiccups for a while; the whole world is
>> patching right now.
>
> Off-topic, yes, but I have to ask, what do you mean?
the Kaminsky bug, perhaps?
http://www.doxpara.com/
which is a rumored to be a naughty little DNS poisoning attack that's
Peter Rowell wrote:
> I sort of know the answers, but it would be interesting (to me at
> least) to hear what the core developers think.
as for most successful open source projects, the core audience is people
that are pretty much like themselves. projects that try to "talk down
to the masses
Jacob Kaplan-Moss wrote:
> That's probably the best idea. We'd still need an editor to eye
> submissions, remove outdated or missing material, brow-beat authors
> into updating blog entries, etc.
Just make sure you make it possible for external editors (=anyone) to
maintain link collections, an
Jacob Kaplan-Moss wrote:
> Like James and Marty I'm skeptical that it'll be useful all that
> often. docstrings are really meant for folks reading the source
nah, they're meant for folks using the "help" command when playing with
things via the command line (or using similar mechanisms in smart
Alex Myodov wrote:
> Breaking the huge documents into smaller chunks for readability is
> good... but please do leave the original huge ones as well! There are
> cases where "a huge document" serves more help than "a bunch of
> smaller ones" and really has its worth.
I haven't checked if Sphinx
Jacob Kaplan-Moss wrote:
>> I'm wondering if something like http://django.reddit.com/ shouldn't
>> get some sort of official blessing for listing/searching those blog
>> posts which aren't of good enough quality for inclusion in the
>> official docs, but are still useful to some people.
>
>
Tim Chase wrote:
> Ah, the curse of backwards compatibility and permalinks. My one
> concern (okay, given more time to think about it, perhaps more
> will percolate to the surface) with this is the abundance of
> (legacy) HTML-fragment references that reside in the ML archives,
> such as
>ht
Derek Anderson wrote:
> but then again, python itself isn't multi-threaded. (all threading is
> faked - google "global interpreter lock". lazy s.o.b. python devs)
given that a stock CPython interpreter releases the lock in a few
hundred places, primarily around potentially long-running or blo
limodou wrote:
> On 12/8/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
>> limodou wrote:
>>
>>>> Why not use unicode object directly ?
>>>>
>>>> dict={"adviser":u"n.顾问, <美> (学生的)指导老师","od":"dd"
limodou wrote:
>> Why not use unicode object directly ?
>>
>> dict={"adviser":u"n.顾问, <美> (学生的)指导老师","od":"dd"}
>>
> because django will auto convert unicode to DEFAULT_CHARSET encoding,
> so you got may be not a unicode string
even if you pass the unicode object to simplejson? sound weird.
us
Graham King wrote:
> If you have thousands of entries in a multiple select box in the
> Django admin interface, the Javascript in SelectBox.js which makes the
> nice gui widget, runs too slowly, and the browser will complain.
if I had to use a multi-selection box with thousands of entries in
James Bennett wrote:
> There's a real-world difference there. You may say that nobody's ever
> used a real SGML parser on HTML4, but I actually have (in fact, I once
> ran into a situation where it was the only way to find a bug that the
> standard W3C validator settings couldn't catch), and I kn
James Bennett wrote:
> They are valid but have a completely different meaning which
(most)
> browsers don't interpret correctly; in HTML4, the closing slash is a
> form of SGML SHORTTAG syntax, and '' in HTML4 is meant to be
> interpreted as a 'br' element followed by a literal greater-than
James Bennett wrote:
> Unfortunately, I don't really have a good proposal for how to handle
> this, except maybe to further break down the Widget API to include
> 'as_html' and 'as_xhtml'. Any ideas?
build up the output using a light-weight DOM with a nice Python-level
syntax, and serialize it
Julio Nobrega wrote:
> Ok... but I think it's strange... The earliest possible "positive"
> date is 01-01-, isn't?
Depends on what calendar you're using. Year zero doesn't exist in the
Gregorian calendar, but "-01-01" is afaik allowed by ISO 8601 (where
it means January 1st, 1 BC).
Daniel Poelzleithner wrote:
> If such a Interface is specified, it should be flexible enough to switch
> backends. In my optinion PIL has a total terrible quality when compared
> to ImageMagick.
that's a rather broad statement, don't you think? what are you doing
with PIL, and how are you doin
Gary Wilson wrote:
> And that is sort of my point. Is it confusing that text|title doesn't
> behave the same as text.title()?
no, I was unclear: the c.l.python poster found it confusing that
text.title() has such a brain-dead notion of that a word is. he
wasn't a Django user, as far as I ca
Gary Wilson wrote:
> I did realize an example where the title filter's implementation would
> be desired. When you've got a possessive noun:
>
Template("{{ text|title }}").render(Context({"text": "the boy's blob"}))
> "The Boy's Blob"
>
> as opposed to:
"the boy's blob".title()
> "The
22 matches
Mail list logo
