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 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! —
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 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 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 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, 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 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
Context:
http://groups.google.com/group/django-developers/browse_thread/thread/cb0dd0b5ba0ffe11/
I would like to submit for (re-)appraisal ticket #1465, which
implements regular expression field lookups (``__regex`` and
``__iregex``). A newly attached patch is up to date with trunk, and
additio
On 6/18/07, Jared Kuolt <[EMAIL PROTECTED]> wrote:
>
> I have a common set of extra bits that I put in my settings.py files
> and re-input them each time I create a project. I would like to have a
> directory like ~/.django_skeletons/project that houses my customized
> settings.py (and perhaps oth
On 6/18/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> modeltests/lookup/models.py looks like the right location.
Tests have been added there in the latest patch.
> Then the maintainers of [Oracle] should be able to help with
> the implementation there.
Good to hear.
--~--~-~--~
On 6/19/07, Jonas <[EMAIL PROTECTED]> wrote:
>
> On 18 jun, 23:17, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > I'm going to give this one more pass and then dropout. We're just going
> > around in circles now.
> It's true that we are around circles, and I understand that you wann't
> make tha
On 6/21/07, john-f <[EMAIL PROTECTED]> wrote:
>
> Hi all
>
> I'm currently moving sites over to one server at my company. The
> server will be hosting 2 versions of django (0.91 and 0.95).
In the future, please direct help requests to the django-users mailing
list; django-developers is for develo
Now that boulder-oracle-sprint has been merged into trunk, I'd like to
ask the Oracle backend developers to take a look at Ticket #1465,
implementing regular expression field lookups (i.e.,
"somefield__regex=foo" or "somefield__iregex=foo"); the patch there
currently lacks support for Oracle.
Bas
On 6/26/07, Ian Kelly <[EMAIL PROTECTED]> wrote:
>
> On 6/23/07, Tom Tobin <[EMAIL PROTECTED]> wrote:
> >
> > Am I on target here? Also, are there versions of Oracle usable with
> > Django that might not support these?
>
> Hi Tom,
>
> You've
On 6/26/07, Ian Kelly <[EMAIL PROTECTED]> wrote:
>
> Let me know if I can be of any other help, e.g. with testing.
Thanks for helping me catch that bug; I think the patch is finally
ready to be committed. :-)
--~--~-~--~~~---~--~~
You received this message becaus
On 7/5/07, anna <[EMAIL PROTECTED]> wrote:
> On Jul 5, 10:19 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> > On 7/5/07, anna <[EMAIL PROTECTED]> wrote:
> >
> > > Can anyone tell me what version of Python the latest version of Django
> > > (and previous versions if available) is written/develope
On 7/5/07, anna <[EMAIL PROTECTED]> wrote:
>
> On Jul 5, 10:42 am, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
> >
> > I think you're asking an unanswerable question; Django is developed
> > *against* a particular minimum Python version's spe
On 7/5/07, anna <[EMAIL PROTECTED]> wrote:
>
> On Jul 5, 11:19 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> >
> > In the Python world, developing "against" a single specific version of
> > the language tends to be frowned upon; there's quite a lot of code out
> > there which runs compatibly on
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.
--~--~-~--~-
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/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/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
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/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 ;-
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/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/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/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/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/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/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/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/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, 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, 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/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/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/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/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, 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:
> 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, 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, 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/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 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 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
>
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, 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
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, 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/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/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/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/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/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
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/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
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/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/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, 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 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 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/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 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
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 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
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
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 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
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/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
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/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
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
101 - 180 of 180 matches
Mail list logo
