I agree almost whole-heartedly with the perception that David
portrays. His feelings almost mirror mine. Albeit I haven't submitted
contributions to the django development process I've been involved
with a number of issues and come away with similar feelings viewing
the process.
I love what those
I've watched the video of the keynote speech, and the following struck me as
an "opportunity for django".
Ala the speech given.
http://www.google.com/buzz/ianbicking/BRWDjsMCGWQ/I-like-the-original-proposal-move-PyPI-stuff-into#127681396096
Thoughts?
--
You received this message because y
Marty:
If you read his post you'll see he is infact getting a 500 Server error, and
not a spam filter error. 500 Server errors happen when something goes wrong,
not when spam is filtered.
On Thu, Jun 5, 2008 at 5:40 AM, Marty Alchin <[EMAIL PROTECTED]> wrote:
>
> On Wed, Jun 4, 2008 at 1:21 PM,
Ahh my greatest apologies - not expected behaviour, nor compliant behavour.
Teach me for skim reading.
On Thu, Jun 5, 2008 at 11:31 AM, Jeff Anderson <[EMAIL PROTECTED]>
wrote:
> Mike Scott wrote:
>
>> Marty:
>>
>> If you read his post you'll see he is infact
>
> I'd trade your controversial part for an alternative: merge mewforms-admin
> back to trunk now. It's been as 'usable' as old admin for months. Sure,
> it's got a couple of dozen 'blocking' bugs in the tracker but none of them
> are all that serious. Current admin, as you note, also has some
Could this not be further discussed?
I understand the need to be toolkit agnostic, but could we not take a
similar approach as the Ext js framework, where by you can use one of
many existing frameworks as your base. Then the django community can
build connectors as demanded.
I understand there a
Jacob,
I think its the fact that we see "internal server error" and just miss
the message which is very nicely hidden after it.
Alot of django developers know what a 500 means, but generally don't
expect to see it for a spam block.
Maybe the page after the block submission needs to be changed.
David,
We know you know the difference, but you should also know how much we
love detail. More detail is also needed here.
On Tue, Jul 22, 2008 at 6:29 PM, David Cramer <[EMAIL PROTECTED]> wrote:
> I don't want to seem harsh Karen, but I understand the differences in the
> user lists. This is
On Wed, Aug 20, 2008 at 12:37 AM, Simon Willison <[EMAIL PROTECTED]>wrote:
>
> On Aug 19, 1:39 am, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
> > (And you know, I still think we'd be better off with
> > "django-YES-THIS-ONE" and "django-NO-THE-OTHER-ONE". Or perhaps a tad
> > more seriously, somethin
On Thu, Aug 21, 2008 at 7:54 PM, Jonathan Nelson <[EMAIL PROTECTED]>wrote:
>
> TWID guys? I'd be happy to combine groups. I just don't know who
> that is.
>
"This week in django" crew - http://www.thisweekindjango.com/ only the
premier podcast resource for django-aholics.
Get in touch with one
err, link doesn't seem to work with www for me, so try:
http://thisweekindjango.com/
On Thu, Aug 21, 2008 at 9:01 PM, Mike Scott <[EMAIL PROTECTED]> wrote:
>
>
> On Thu, Aug 21, 2008 at 7:54 PM, Jonathan Nelson <[EMAIL PROTECTED]>wrote:
>
>>
>> TWID
Congratulations!!
Was wondering if you could get a hold of adrian and get him to update the
python packages stuff to the latest version?
Otherwise looking good! :)
On Thu, Sep 4, 2008 at 12:07 PM, James Bennett <[EMAIL PROTECTED]>wrote:
>
> The Django team is pleased to announce the release of
Hi Guys,
I wasn't sure where/who to get in touch with regarding this but I was hoping
that on both the djangocon and django blog websites announcements could be
made to the effect of announcing the availability of the djangocon videos
from google now on youtube. I think it would be great to let ev
Please move this conversation to django-users. Django-developers is for the
discussion pertaining to the maintenance and development of the django
framework itself.
On Thu, Oct 2, 2008 at 3:55 AM, Erik Allik <[EMAIL PROTECTED]> wrote:
>
> Nevermind the previous e-mail.
>
> On 01.10.2008, at 17:10
Thierry,
Firstly django-developers is not the place for this discussion.
Secondly this question has been asked, and solved many times. If you search
through the django-users archives I'm sure you'll find plenty of solutions.
There are solutions out and about in the blogosphere too.
Cheers,
Mik
+1!
Just one suggestion - if the final "bateries included" could be split into
contrib apps, and core library that'd be nicer.
On Tue, Nov 18, 2008 at 8:44 PM, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> After months of being frustrated (and hearing other people being
> frustrated) with our n
For all three of our projects in django, we've gone through and used our own
exended version of render_to_response, which uses RequestContext by default.
Its such a blessing.
On Tue, Nov 18, 2008 at 7:42 PM, James Bennett <[EMAIL PROTECTED]>wrote:
>
> On Tue, Nov 18, 2008 at 12:04 AM, Yuri Baburo
I'm +1 for the reasons of lack of upstream support.
On Wed, Nov 26, 2008 at 10:42 PM, mrts <[EMAIL PROTECTED]> wrote:
>
> On Nov 26, 3:20 am, Julien Phalip <[EMAIL PROTECTED]> wrote:
> > On Nov 26, 11:43 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
> > wrote:
> >
> >
> > > On Wed, Nov 26, 2008 a
I second Todds suggestion.
I'm also just +0 on the whole affair. While it would be nice I think it has
far surpassed the effort needed.
On 9/19/07, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
>
>
> On Wed, 2007-09-19 at 00:29 +, Johann C. Rocholl wrote:
> > On Sep 17, 10:17 am, "Justin Lilly" <[E
Also Jacob, on the documentation the link ot the contenttypes docs have gone
missing. As well as a few other documentation files that don't seem to be on
the index link.
Is this intentional?
On 9/19/07, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
>
>
> On Tue, 2007-09-18 at 15:51 -0500, Jacob Kaplan-
Istvan,
It should be threadsafe - the way web applications and web loads work mean
that lots of simultaneous connection will mean that it pretty much becomes a
threaded application, and for that reason I think more research should be
done into this sort of operation?
On 9/26/07, Istvan Albert <[E
This is something that has been a gripe of mine in a current project, where
by originally we had organisations as users, rather than users themselves.
I think what should happen is the django user class should have a
"displayname" field, for which defaulted to the username if none was
provided, if
Can I throw a hat in the ring and suggest a post-send-request hook?
I have an existing script in PHP which used shutdown_functions() and was
looking for ways to do this in python. Certain use cases for this arise.
(Though could be easily solved by sending to a queue server like
django-queue).
If
Ah,
Sorry all. Knew I missed it.
Thanks Ben. I might go about documenting all this sometime then. We really
need to improve those docs :)
On 10/9/07, Benjamin Slavin <[EMAIL PROTECTED]> wrote:
>
>
> On 10/8/07, Mike Scott <[EMAIL PROTECTED]> wrote:
> > Can I throw a
+1 from me, this also a document that developers can look at and plan around
very succinctly.
On Dec 1, 2007 3:02 PM, Simon Willison <[EMAIL PROTECTED]> wrote:
>
> Here's an idea that's been kicking around in the back of my head for
> far too long: Django Enhancement Proposals, or DEPs. At the mo
nteresting development
for a python developer to come into Django for the first time and discover
this.
Regards,
Mike Scott
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this
James, I'm think what I'm getting at more is not the fact that its
"magical", maybe that is the wrong choice of word. But my opinion is more of
the fact that it doesn't conform to the rest of the django database
commands.
I do think you put it aptly in asking do we want to be more SQL-style or
Pyt
ompressing and
obfusicating it.
Is this an approach the bulk of the Django community are interested in
taking or is it something that we should leave to the things that do it
best, ie: Apache and the like.
Regards,
Mike Scott
--~--~-~--~~~---~--~~
You received th
http://groups.google.com/group/django-newsroom
I just created this group, If Rob, Michael could ping me when they're joined
and I'll give them higher permissions. Lets see what the newsroom can do!
On Dec 16, 2007 1:53 AM, Richard D. Worth <[EMAIL PROTECTED]> wrote:
> On Dec 14, 2007 11:48 AM,
If Adrian or one of the others with access could update the new ticket page,
and add a link to register that would make these issues disappear. Right now
people just get confused and shy away more than they ask.
On Jan 10, 2008 1:54 PM, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On Jan 9, 2008
Further to this I'd like to point out that SQL lite is a very limited
database in respect to the other offerings.
Encouraging such a practice, in my opinion, is a really bad idea.
Just my 2c.
Mike
On Feb 13, 2008 3:55 PM, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> On Feb 13, 2008 1:5
I'm not a fan of this discussion,
I understand what you're saying, and the simple importerror test should
suffice, otherwise its going to get to a point where we're going to have to
keep a list of python libraries that can't be used for app names. Its not
going to work like that. As far as I'm con
This mailing list is for the development of django itself. Your issue is
with mod_python and is probably better answered at
http://mailman.modpython.org/mailman/listinfo/mod_python
It has nothing to do with django itself.
If you have any issues with django, then the first port of call (and oft
Congratulations Malcolm,
You very much deserve a big pat on the back for the entirety of the work you
have done.
We've been testing on 3 of our websites the QS-RF branch, with little to no
issues, and lots of benefits.
Regards,
Mike Scott
On Sun, Apr 27, 2008 at 5:46 PM, Russell Keith-
check these things BEFORE you do a svn update, rather than after.
Regards,
Mike Scott
On Wed, Apr 30, 2008 at 2:25 PM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> I've been extremely busy over the last few weeks, and have rarely had
> the chance to check the mailing list. I
On Fri, May 23, 2008 at 2:59 AM, Simon Willison <[EMAIL PROTECTED]>
wrote:
> 1. Replication - being able to send all of my writes to one master
> machine but spread all of my reads over several slave machines.
> Thankfully Ivan Sagalaev's confusingly named mysql_cluster covers this
> problem neatl
36 matches
Mail list logo
