On Tue, Aug 19, 2008 at 8:16 AM, Malcolm Tredinnick
<[EMAIL PROTECTED]> wrote:
> Please take this thread to django-users. This list is for the internal
> development of django and this thread doesn't contribute to that.
Done.
--~--~-~--~~~---~--~~
You received thi
On Mon, Aug 18, 2008 at 7:36 PM, Tom Tobin <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 18, 2008 at 7:01 PM, tezro <[EMAIL PROTECTED]> wrote:
>>
>> Hi all. Got a question unsolved yet.
>
> Wrong list — you want django-users. django-developers is for
> develop
On Mon, Aug 18, 2008 at 7:01 PM, tezro <[EMAIL PROTECTED]> wrote:
>
> Hi all. Got a question unsolved yet.
Wrong list — you want django-users. django-developers is for
development *of* Django, not *using* Django. ^_^
--~--~-~--~~~---~--~~
You received this messag
On Mon, Jul 21, 2008 at 10:18 AM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
> If there's anything that absolutely *MUST* be in 1.0 alpha, speak up
> now. Please keep in mind that the alpha release is intended only for
> the "must-have" features, which are now all in. This means that the
> only
On Thu, Jul 17, 2008 at 10:01 AM, Waylan Limberg <[EMAIL PROTECTED]> wrote:
>
> On Thu, Jul 17, 2008 at 6:46 AM, zvoase <[EMAIL PROTECTED]> wrote:
>>
>> Dear Developers,
>> I've written a module which may be helpful to a lot of Django
>> developers, and would like to suggest it for trials and te
On Tue, Jul 8, 2008 at 8:49 PM, Malcolm Tredinnick
<[EMAIL PROTECTED]> wrote:
> *Deprecation*, dagnabbit! Depreciation is a different word. :-)
Ye grammar gods! I'm usually more on top of things than that. Shame
on me! ^_^
[...]
> Anyway, you've got a few weeks. Probably worth whacking togeth
On Tue, Jul 8, 2008 at 6:08 PM, Malcolm Tredinnick
<[EMAIL PROTECTED]> wrote:
>
> On Tue, 2008-07-08 at 09:55 -0500, Tom Tobin wrote:
> [...]
>> I'm curious as to
>> whether others think we can still manage this cleanly post-1.0. If we
>> can, great! —
Since bringing up the topic a few months ago (and getting support for
the idea) [1], I haven't had time to whip up a patch to move the
contents of various modules' __init__ out into "base" or "main". It
finally clicked (you know, several weeks *after* 1.0 features were
nailed down, ugh) that this
On Sat, Jul 5, 2008 at 3:10 AM, Keir <[EMAIL PROTECTED]> wrote:
> I have recently been working on my first project in Django and have
> encountered a small problem when using ModelForm. Here's my ModelForm
> class
You're on the wrong list. ^_^ For support questions, you want django-users.
The
On Thu, Jul 3, 2008 at 9:26 AM, Jannis Leidel <[EMAIL PROTECTED]> wrote:
>> Even if these sorts of features have a patch and are "Ready for checkin,"
>> that does not mean they get a 1.0 milestone. They still take core
>> developer time to review and commit, time that also needs to be
>> focused
On Thu, Jul 3, 2008 at 9:26 AM, phillc <[EMAIL PROTECTED]> wrote:
>
> random person: "i need help"
> magus: gives technical answer
> random person: does understand python
> magus: points to docs
> random person: you are rude
1) Let's stop referring to specific people, mmkay? I made that
mistake,
On Wed, Jul 2, 2008 at 7:17 AM, Arien <[EMAIL PROTECTED]> wrote:
>
> Can we get back to our regular program now and move personal problems
> to private communication, please? Thank you.
Insofar as referencing particular individuals goes, I agree. I should
have raised any issues with particular c
On Tue, Jul 1, 2008 at 4:25 AM, Kenneth Gonsalves
<[EMAIL PROTECTED]> wrote:
>
> why should he be more polite? He follows the policy of 'teaching to
> fish' rather than spoonfeeding. I have several times got flamed by
> him for getting impatient and giving the answer. I would say that he
> is the s
On Mon, Jun 30, 2008 at 4:29 AM, Antti Haapala <[EMAIL PROTECTED]> wrote:
>
> 2008/6/27 Tom Tobin <[EMAIL PROTECTED]>:
>>
>> Well, it stores the *offset*, which is virtually useless in real-world
>> applications.
>
> I haven't tested on 8.3, but
On Fri, Jun 27, 2008 at 5:55 AM, Antti Haapala <[EMAIL PROTECTED]> wrote:
>
>
> On 25 kesä, 19:12, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
>
>> All PostgresSQL supports in terms of *storage* is
>> a fixedtimezoneoffset, not the actual zoneinfo name;
On Fri, Jun 27, 2008 at 11:36 AM, rskm1 <[EMAIL PROTECTED]> wrote:
>
>> Help me out here: how can I make it more obvious? You missed that;
>> others often do to. Can you share with me some insights on how you
>> missed it?
>
> I'll chime in. Basic rule of thumb for GUIs:
> * If it's going to fail
On Thu, Jun 26, 2008 at 9:05 AM, Mike Scott <[EMAIL PROTECTED]> wrote:
> I understand there are some complexities involved, but essentially its
> just creating a uniform javascript API to use - not unlike the may we
> have a uniform database api.
That's a gross understatement. :-)
The various J
On Wed, Jun 25, 2008 at 4:48 PM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
> Calling someone else out publically is a move of last resort, and one
> that should be avoided at all costs.
::sigh:: I'm sorry; after this and another spat on the ChiPy list, I
think I'm not very good at the whole t
I don't spend much time in #django on Freenode, but for a moment, I'd
like you to check the logs of that channel.
http://oebfare.com/logger/django/
Specifically, I'd like you to note interactions with user "Magus-"
(with trailing dash).
I think we have a representation problem on our hands. If
On Wed, Jun 25, 2008 at 11:17 AM, Ramiro Morales <[EMAIL PROTECTED]> wrote:
>
> On Wed, Jun 25, 2008 at 1:12 PM, Tom Tobin <[EMAIL PROTECTED]> wrote:
>
>>
>> I propose that the PostgresSQL backends start acting like the other
>> backends regarding time
Thanks to some happy signal magic, I've come up with a
"DateTimeZoneField" that takes a "time_zone" argument; time_zone can
be a tzinfo instance or a field lookup to a zoneinfo string (e.g.,
"America/Chicago"). The field can then consume any sort of datetime
object, and will always spit back a ti
On Thu, Jun 19, 2008 at 4:27 PM, Marc Fargas <[EMAIL PROTECTED]> wrote:
> El jue, 19-06-2008 a las 14:03 -0700, Michael Elsdörfer escribió:
>> FWIW (I'm currently playing around with all three of them), bazaar
>> appears to support pushing into svn as well.
>
> Yes, with bzr-svn. Didn't play too mu
On Thu, Jun 19, 2008 at 11:39 AM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
> I've published an experimental Git clone of Django's SVN repository
> (created with git-svn). If you're a Git user and want to use this
> repository, be my guest. Please still upload patches to Trac for
> review, but
On Fri, Jun 13, 2008 at 12:36 PM, Marty Alchin <[EMAIL PROTECTED]> wrote:
>
> On Fri, Jun 13, 2008 at 1:23 PM, Tom Tobin <[EMAIL PROTECTED]> wrote:
>> Ugh, time. I have a bad habit of assuming I have more of that
>> resource available than I ultimately do. :)
On Fri, Jun 13, 2008 at 12:32 PM, Marty Alchin <[EMAIL PROTECTED]> wrote:
>
> On Fri, Jun 13, 2008 at 1:23 PM, Alex Koshelev <[EMAIL PROTECTED]> wrote:
>> There is existing multi-lingual aggregator http://djangosearch.com/
>
> I didn't realize djangosearch broke articles down by language,
> comple
Bah, simultaneous thread-splitting. Send any replies to the other
"djangochatter" thread.
On Fri, Jun 13, 2008 at 12:23 PM, Tom Tobin <[EMAIL PROTECTED]> wrote:
> On Fri, Jun 13, 2008 at 12:07 PM, Marty Alchin <[EMAIL PROTECTED]> wrote:
>>
>> There's an
On Fri, Jun 13, 2008 at 12:25 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Also for anyone interested, there's this:
>
> http://djangosearch.com/
Well. Damn. That looks like what we're talking about here.
I wonder if it indexes everything the "official" aggregator does?
--~--~
On Fri, Jun 13, 2008 at 12:23 PM, Alex Koshelev <[EMAIL PROTECTED]> wrote:
> There is existing multi-lingual aggregator http://djangosearch.com/
That's just been mentioned in the new "djangochatter" thread as well
... very interesting. Continuing over there.
--~--~-~--~~
On Fri, Jun 13, 2008 at 12:27 PM, Alex Koshelev <[EMAIL PROTECTED]> wrote:
> -100
>
> Non-English post isn't noise!
>
> Some English posts has more less profit then non-English ones.
*To me*, someone who can't read them, yes, they're noise. I'm sorry.
If I can't read it, it does nothing for me b
On Fri, Jun 13, 2008 at 12:07 PM, Marty Alchin <[EMAIL PROTECTED]> wrote:
>
> There's an aggregator, IRC log, various mailing list archives, wiki
> articles, ticket comments, localized community sites, the list goes on
> and on. In the spirit of community-oriented sites (like djangosites,
> django
On Fri, Jun 13, 2008 at 12:04 PM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
>
> I'll look into setting up language-specific feeds (and a general
> non-English one). If it's easy, I'll do it. If not, anyone is welcome
> to look at the djangoproject.com source and submit a patch; I'll
> happily a
On Fri, Jun 13, 2008 at 12:02 PM, Arien <[EMAIL PROTECTED]> wrote:
>
> The non-English posts are clearly useful to the Django community as a
> whole, as it appears that the majority of its members don't speak
> English as their native tongue.
I'm totally fine with non-English feeds being availabl
On Fri, Jun 13, 2008 at 11:33 AM, Alex Koshelev <[EMAIL PROTECTED]> wrote:
>
> It is not a problem. Just skip non-English posts at all. English is
> international language of cource but not the one.
Except it *is* a problem when I'm forced to deal with a regular influx
of what is, to me, *noise*
On Fri, Jun 13, 2008 at 11:31 AM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> I propose an option on the side of the page that asks whether or not
> to translate the posts into english. The google translator is fairly
> effective and a lot of the russian posts I have looked at have bee
> ver
On Fri, Jun 13, 2008 at 11:05 AM, Arien <[EMAIL PROTECTED]> wrote:
>
> On Fri, Jun 13, 2008 at 10:58 AM, Tom Tobin <[EMAIL PROTECTED]> wrote:
>>
>> The Django community aggregator includes non-English posts, which are
>> unfortunately pure noise for th
On Fri, Jun 13, 2008 at 11:01 AM, pi song <[EMAIL PROTECTED]> wrote:
> Are they real posts? I thought just spam.
They certainly *look* like real posts, but I can't understand anything
outside of the technical (English) terms used. :)
--~--~-~--~~~---~--~~
You rec
The Django community aggregator includes non-English posts, which are
unfortunately pure noise for those of us who don't understand other
languages. Can we either restrict the aggregator to English posts, or
at least create sub-feeds for English and non-English posts?
I don't mean to tread on th
On Tue, Jun 10, 2008 at 7:13 PM, Russell Keith-Magee
<[EMAIL PROTECTED]> wrote:
>
> However, I'm happy to defer to
> someone with a higher degree in grammarnazism.
With that in mind, I whipped out my copies of the Chicago Manual of
Style and Garner's Modern American Usage last night.
And came up
On Sat, Jun 7, 2008 at 2:06 PM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
> * Wait for newforms-admin to be done, merge it, and release 1.0 (well,
> a series of beta/rcs, then final). This has been "plan A" all along.
+1; this is The Right Thing.
> * Release an interim release right away to r
On 2/18/08, Brian Rosner <[EMAIL PROTECTED]> wrote:
>
> > Is there any good reason why the "fieldsets" option of ModelAdmin (in
> > newforms-admin) shouldn't be pushed down into the newforms library?
> > What I'm doing right now by overriding change_form.html would be even
> > easier if I could de
On 2/12/08, Waldemar Kornewald <[EMAIL PROTECTED]> wrote:
> Hi,
> since Trac does neither allow me to post anonymously nor do I get a
> registration mail (username wkornewald) I'll post here:
Please don't post patches to the mailing list. Trac is the right
place for these.
If you're having trou
Is there any good reason why the "fieldsets" option of ModelAdmin (in
newforms-admin) shouldn't be pushed down into the newforms library?
What I'm doing right now by overriding change_form.html would be even
easier if I could define my fieldsets on a ModelForm.
Related to how I'm working around it
On 2/2/08, Justin Bronn <[EMAIL PROTECTED]> wrote:
>
> > I'm *way* off base at the moment (and stuck gradually walking towards
> > HEAD, fixing my patch in increments; this is where git definitely has an
> > advantage over hg, but I'm using the latter).
>
> I've found hg-svn to be particularly usef
On 2/1/08, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> Stuff intended for reuse inside a particular package doesn't really
> belong in __init__ if the package contains multiple non-trivial files
> (e.g. argument lexing and parsing), so no argument about moving those
> bits out.
>
> So I'm stil
On 2/1/08, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> I'm probably -0 on this. It's a little unnecessary code churn and being
> able to track what lines changed when is unbelievable handy, so code
> shuffling should be resisted.
Copying in subversion retains history; why would we lose anythi
I'm in the midst of resurrecting my "taghelpers" code that makes
writing complex template tags much easier; as with all my patches, I'm
using Mercurial to track Django locally while I work on them. Thing
is, I've moved nearly everything out of django.template.__init__ into
a django.template.main
On 1/29/08, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> I'd make the ``*args`` style start issuing DeprecationWarnings
> immediately, and remove support entirely when we wipe deprecated
> features in the run-up to 1.0. I'd make this change on the
> queryset-refactor branch.
I'm inclined to lik
On 1/28/08, Kaelten <[EMAIL PROTECTED]> wrote:
> So I've had to dig into the handler setup for various things. Since then
> I've broken down the handler and refactored more common code code into
> BaseHandler, and cleaned up the error catching to I've tested the WSGI
> handler and it works under
Over at The Onion, we're working on a major new project in Django.
(By "major", well, let's just say that it doesn't end in
"theonion.com" or "avclub.com".) We absolutely *love* Django to
pieces ... especially me, considering that Django's the reason I was
hired. ^_^ Just like everyone, though,
On Thu, 2007-10-18 at 19:18 -0500, Jeremy Dunck wrote:
> Devs,
> I'd like to improve the quality of Django's documentation.
> I'm sure there will be many opinions on what "improvement" would mean.
>
> I'd like to solicit ideas from django-users regarding how people use
> the docs and wish t
On 9/20/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On 9/20/07, Tom Tobin <[EMAIL PROTECTED]> wrote:
> > I'd certainly like to simply
> > "be bold" as per Wikipedia and be a bit more aggressive with improving
> > the wiki, but of cou
On 9/20/07, Scott Paul Robertson <[EMAIL PROTECTED]> wrote:
>
> On Tue, Jul 24, 2007 at 06:52:54PM -0500, Adrian Holovaty wrote:
> >
> > On 7/24/07, Scott Paul Robertson <[EMAIL PROTECTED]> wrote:
> > > [ Discusion about editor for development wiki pages... ]
> > > Since I'm throwing out the idea,
On 9/19/07, James Bennett <[EMAIL PROTECTED]> wrote:
>
> David Cramer has asked that Django's ORM lookup syntax be changed to
> allow a single underscore for a foreign key lookup; in other words,
> the following two examples would become equivalent:
>
> UserProfile.objects.get(user__id=3) #Current
On 8/8/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> What I *do* think is worth fixing is allowing the template system to
> be used on its own, for the simple, common case, without having to
> configure stuff. This is what I was trying to explain in my last
> e-mail. Tom, if we solved that, w
On 8/8/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 8/8/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > A couple of other areas are going to be at least equally as
> > interesting...
>
> Malcolm has made some *really* good points throughout this thread, and
> I'm convinced that goin
On 8/8/07, Robert Coup <[EMAIL PROTECTED]> wrote:
> On 08/08/2007, James Bennett <[EMAIL PROTECTED]> wrote:
> >
> > On 8/8/07, Tom Tobin <[EMAIL PROTECTED]> wrote:
> > > I'd ideally like the Django installer to detect if django.template was
> &
On 8/7/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> This would be great, as long as you could figure out how to make it
> backwards compatible. Thanks for volunteering! :-)
>
> Here are some broad goals/thoughts, IMHO:
>
> * Users of Django the framework should not be affected in any way.
>
On 8/7/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> On Tue, 2007-08-07 at 17:39 -0500, Tom Tobin wrote:
> > At the end of the angsty autoescaping thread (said angst in no small
> > part from my direction ^_^), I floated the idea that perhaps my
> > concern
At the end of the angsty autoescaping thread (said angst in no small
part from my direction ^_^), I floated the idea that perhaps my
concern over autoescaping was pointed in the wrong direction -- that it
might be time to split Django's template module out into a standalone
library. The idea has b
On 8/6/07, Alex Nikolaenkov <[EMAIL PROTECTED]> wrote:
> > If a core dev closes a ticket with a "wontfix", you shouldn't re-open
> > the ticket unless you've made a compelling case on django-dev and
> > gotten the core devs to change their minds. "Wontfix" essentially
> > means that a design deci
On 8/6/07, Alex Nikolaenkov <[EMAIL PROTECTED]> wrote:
>
> I never heard that tickets should not be reopened if you disagree. If
> the bug is still reproducible it should be reopened. If its
> resolution is changed to "won't fix", one should point why. And
> not just - "Oh, it is good enough now".
On 8/4/07, Tom Tobin <[EMAIL PROTECTED]> wrote:
> On 8/4/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> >
> > On 8/1/07, James Bennett <[EMAIL PROTECTED]> wrote:
> > > Let's just do:
> > >
> > > 1. Autoescape on by default.
>
On 8/4/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 8/1/07, James Bennett <[EMAIL PROTECTED]> wrote:
> > Let's just do:
> >
> > 1. Autoescape on by default.
> > 2. Autoescape is turned off by the {% autoescape off %}
> > 3. Autoescape happens irregardless of what the template's source fil
On 8/2/07, Simon Willison <[EMAIL PROTECTED]> wrote:
>
> On Aug 1, 7:56 pm, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
> > Set autoescaping on by default for anything ending in ``.html`` (and,
> > perhaps, ``.htm``), and off otherwise.
>
> I've b
On 8/1/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> - No, we're not going to create a branch (at least, not yet)
I think we've more-or-less moved to a "not ever" policy for branches
going forward, encouraging developers to maintain their own branches
outside the official tree. (Core de
On 8/1/07, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 8/1/07, Tom Tobin <[EMAIL PROTECTED]> wrote:
> > Let's assume autoescaping is on unless the template engine knows
> > otherwise; your inline templates will work as expected both before and
> >
On 8/1/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> Anybody who thinks this decision is actually a really big life-changing
> decision needs to re-evaluate their priorities. And perhaps pick some
> bigger-item bugs to fix. This is too depressing; just pick one and move
> on.
Translating
On 8/1/07, Luke Plant <[EMAIL PROTECTED]> wrote:
>
> On Wednesday 01 August 2007 19:56:05 Tom Tobin wrote:
> > Okay, post-Starbucks chat with my co-workers, here's my last-ditch
> > mitigation proposal:
> >
> > Set autoescaping on by default for anyth
Okay, post-Starbucks chat with my co-workers, here's my last-ditch
mitigation proposal:
Set autoescaping on by default for anything ending in ``.html`` (and,
perhaps, ``.htm``), and off otherwise.
Being (at least ideally) language-neutral has precedent in Django;
we've already moved away from ass
On 8/1/07, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 8/1/07, Tom Tobin <[EMAIL PROTECTED]> wrote:
> > I felt my hackles rising until I read this part. ^_^ I'm somewhere
> > between -0 and +0 at this point so long as auto-escaping is off by
>
On 8/1/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
> Auto-escaping is off by default, so there shouldn't be any compatibility
> issues at all.
I felt my hackles rising until I read this part. ^_^ I'm somewhere
between -0 and +0 at this point so long as auto-escaping is off by
default (and
On 7/27/07, David Cramer <[EMAIL PROTECTED]> wrote:
>
> QuerySet refactoring is like Django 1.0 ya? Never coming?
The Django developers are ::gasp:: real people, with real jobs and
real lives. I see this perhaps more readily than most, since a few of
them are my co-workers. Considering all the
On 7/26/07, Tom Tobin <[EMAIL PROTECTED]> wrote:
> I'm starting to seriously wonder if the 80-character line width has
> outlived its usefulness. There are various naturally occurring bits
> of code that just don't fit onto a single 80-character line, and the
> option
On 7/26/07, Nicola Larosa <[EMAIL PROTECTED]> wrote:
>
> Tom Tobin wrote:
> > I'm starting to seriously wonder if the 80-character line width has
> > outlived its usefulness.
>
> It has not, and it never will, until human beings stay the same: it's not a
&
On 7/26/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > I find it hard to imagine a programmer these days who is so starved
> > for screen real estate that they couldn't handle a width of, say, 120
> > characters;
>
> Try to imagine a bit harder then. I'm in that position, for example,
> eve
On 7/26/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On 7/25/07, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> > On 26-Jul-07, at 7:36 AM, Thejaswi Puthraya wrote:
> > > This week I worked on getting the 'like' and 'between' check
> > > conditions into the project and also writing a lot o
On 7/26/07, Andrey Khavryuchenko <[EMAIL PROTECTED]> wrote:
> "Tom Tobin" <[EMAIL PROTECTED]> wrote:
> TT> I find it hard to imagine a programmer these days who is so starved
> TT> for screen real estate that they couldn't handle a width of, say, 120
&
On 7/26/07, Amit Upadhyay <[EMAIL PROTECTED]> wrote:
> On 7/26/07, Tom Tobin <[EMAIL PROTECTED]> wrote:
> > I'm starting to seriously wonder if the 80-character line width has
> > outlived its usefulness. There are various naturally occurring bits
> > of cod
On 7/26/07, Tom Tobin <[EMAIL PROTECTED]> wrote:
> ... increasing the minimum width would ...
Err, *maximum* width, rather. ^_^
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers"
On 7/25/07, Gary Wilson <[EMAIL PROTECTED]> wrote:
>
> Adrian, which BDFL do we follow :)
I'm +1 to Adrian's style (descriptive, rather than prescriptive); it
feels more natural to have the docstring be a description of the given
code rather than a direct "English translation". The code itself i
On 7/25/07, Duc Nguyen <[EMAIL PROTECTED]> wrote:
>
> On a somewhat related note, is it just me or does no django core developer
> follow the "no line longer than 79 characters" note. I like using emacs
> and I have my frame width set at 80 and it bothers me to no end to have
> to scroll to see ev
On 7/22/07, oggie rob <[EMAIL PROTECTED]> wrote:
>
> This was my feeling also, however I think it is prudent to prevent
> legitimate users from making mistakes. I don't know about designers,
> but I have worked with some programmers that just don't think things
> through like they should...
This
On 7/22/07, Amit Upadhyay <[EMAIL PROTECTED]> wrote:
> I have just uploaded a patch for what I call "reverse pagination". Please
> read about it here:
> http://code.djangoproject.com/ticket/4956. You can see it
> in action on my blog: http://www.amitu.com/blog/.
[...]
> To avoid confusion I was wo
On 7/20/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
>
> heh, i read this and was like "there are other backends?!?" ;p
>
> nope, sqlite/mysql/postgres is all she wrote right now, as that was all
> that existed last summer when i did the bulk of the work on this. but
> i'll add oracle and mssql
On 7/20/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> actually, I find it a legitimate use of django-developers to report errors
> that are probably caused by Django and look weird, especially if the mail
> concentrates on the bug description and is, well, developer style (full
> cont
On 7/20/07, Nicola Larosa <[EMAIL PROTECTED]> wrote:
>
> Tom Tobin wrote:
> > Django-developers isn't a "Help Desk Level 2"; please don't try to use
> > it as such.
>
> Maybe too much politeness on my part obscured the main point, so let's
On 7/20/07, Nicola Larosa <[EMAIL PROTECTED]> wrote:
>
> [Sent this to the users list with no answer, and who knows, maybe it's not
> me, but actually a bug instead. :-) I also tried using the newforms-admin
> branch, but most URLs are absent or commented out...]
[...]
> What am I missing?
Django
On 7/17/07, Etienne Robillard <[EMAIL PROTECTED]> wrote:
>
> Russell,
>
> Thanks for your help.
>
> Next time, could you please just have the decency to reply
> to the sender himself, instead of writing things like that
> to the list ?
>
> I think that would have more punch (think netiquette) than
On 7/15/07, Tai Lee <[EMAIL PROTECTED]> wrote:
>
> I'd rather petition the PostgreSQL developers to optimise count(*) and
> suggest Django users implement their own changes or workaround in the
> meantime if they're working with large datasets where count(*) is a
> serious performance penalty.
Th
On 7/14/07, Brian Harring <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 13, 2007 at 11:19:53PM -0500, Tom Tobin wrote:
> >
> > On 7/12/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > >
> > > A few comments (mostly questions) from an initial reading:
&g
On 7/12/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> A few comments (mostly questions) from an initial reading:
I've now implemented most of your suggestions [1]; a few questions
remain, though:
1) If I'm going to import the taghelpers errors/API into
django.template, I'll need to in tu
On 7/13/07, Tom Tobin <[EMAIL PROTECTED]> wrote:
> +0; seems like a reasonable addition. I wonder of "any" might be a
> better method name (along the lines of the Python 2.5 built-in
> function), but either name would be fine IMHO.
Er
On 7/13/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> I'd like to add a QuerySet.exists() method, which would return True or
> False if the given QuerySet contains at least one record. This would
> be more efficient than qs.count() or len(qs) because it would perform
> the following SQL under
On 7/12/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> On Thu, 2007-07-12 at 01:58 -0500, Tom Tobin wrote:
> > Over at the Lawrence Journal-World, we have a bunch of custom template
> > tags included in Ellington, our commercial CMS based on Django. One
> >
On 7/12/07, Baptiste <[EMAIL PROTECTED]> wrote:
>
> I have tried to read this patch, but its presentation is really
> awful.. But even if I have stopped to read, that seems to be a very
> big work! I would like to see it from Trac or I don't know what but
> from something that makes him legible ;-
Over at the Lawrence Journal-World, we have a bunch of custom template
tags included in Ellington, our commercial CMS based on Django. One
day, I finally got fed up with writing the same damned boilerplate
code for custom tags over and over again (for parsing arguments,
resolving context variable
On 7/11/07, Carl Karsten <[EMAIL PROTECTED]> wrote:
>
> Jacob Kaplan-Moss wrote:
> > OK, we're 8 messages deep into this thread, and I've got no idea what
> > the point is.
> >
> > Carl -- what is it you want to know? Is something not working
> > correctly for you, or is this just an academic ques
On 7/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> The code Ned put up contains data from the public domain and
> was most likely restricted due to that.
I'm not sure what you mean by this; "public domain" means anyone can
do pretty much whatever they want with it, without restriction.
--
On 7/8/07, _ <[EMAIL PROTECTED]> wrote:
> I'm doing my best to convert over to the newforms-admin model.
You're on the wrong list; please redirect to django-users.
Django-developers is for development *on Django itself*, not for
development *using Django*.
--~--~-~--~~~--
On 7/8/07, Al Abut <[EMAIL PROTECTED]> wrote:
> Can anyone share their tips on ongoing work with forms and designers?
You're on the wrong list; please redirect this to django-users.
Django-developers is for development work *on Django itself*, not
development *using* Django.
--~--~-~--~-
1 - 100 of 180 matches
Mail list logo
