On Sat, 2007-06-02 at 14:29 +0800, Russell Keith-Magee wrote:
> On 6/2/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> >
> > On Sat, 2007-06-02 at 10:02 +0800, Russell Keith-Magee wrote:
> > > Hi All,
> > >
> > > Any objections to my committing this to trunk?
> >
> > I hadn't actually read the
On 6/2/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> On Sat, 2007-06-02 at 10:02 +0800, Russell Keith-Magee wrote:
> > Hi All,
> >
> > Any objections to my committing this to trunk?
>
> I hadn't actually read the patch and I think I lost consciousness at
> some point in the middle of the t
On Sat, 2007-06-02 at 10:02 +0800, Russell Keith-Magee wrote:
> Hi All,
>
> I recently raised ticket #4418 to add media descriptors to newforms.
> It was discussed on the following thread:
>
> http://groups.google.com/group/django-developers/browse_thread/thread/58fc9cab819c08b9/82a9adc74ae81833
On Fri, 2007-06-01 at 09:50 -0500, Jacob Kaplan-Moss wrote:
> On 6/1/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > I suspect my laxness has been holding up the boulder-oracle-sprint
> > branch merge.
>
> Yeah, I've also been bad about getting my review notes in. Now that you've
> started
On Fri, 2007-06-01 at 11:05 -0600, Ian Kelly wrote:
> Hi Malcolm, thanks for taking the time to look this over.
>
> On 6/1/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > (1) In core/management.py, there are a lot of lines that are
> > doing the equivalent of;
> >
> >
On 6/1/07, kernel1983 <[EMAIL PROTECTED]> wrote:
>
> Now session can be only storaged in the database.
>
> I think,django should be friendly with both new users and the mature
> python users.
Yeah, I agree, though I haven't gotten around to supplying a patch for
other backends. I do like the per
Now session can be only storaged in the database.
I think,django should be friendly with both new users and the mature
python users.
Since cache can support different kinds of backend, session should
also be.
Many people want to build application which can be deployed easily. If
they had to run
Hi All,
I recently raised ticket #4418 to add media descriptors to newforms.
It was discussed on the following thread:
http://groups.google.com/group/django-developers/browse_thread/thread/58fc9cab819c08b9/82a9adc74ae81833
To my reading, Jacob and Malcolm were +1 to the change (correct me if
I
On 6/1/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> Or does one of the other core devs have access to an Oracle install? I'm
> pretty
> sure Adrian doesn't, but if Russ or Malcolm does I'm happy to let one of them
> do
> the merge...
I have access to an Oracle install at work. However,
On 6/2/07, Amit Upadhyay <[EMAIL PROTECTED]> wrote:
> Django is a web development framework, and not model development. REST
> (XMLRPC/SOAP) API are created to expose webservices, which by definition
> could be anything, not just models. CRUD is myopic world view.
Thanks for your comment!
You ar
This email address is no longer in service. Please use [EMAIL PROTECTED]
Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@go
This email address is no longer in service. Please use [EMAIL PROTECTED]
Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@go
This email address is no longer in service. Please use [EMAIL PROTECTED]
Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@go
This email address is no longer in service. Please use [EMAIL PROTECTED]
Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@go
This email address is no longer in service. Please use [EMAIL PROTECTED]
Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@go
This email address is no longer in service. Please use [EMAIL PROTECTED]
Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@go
This email address is no longer in service. Please use [EMAIL PROTECTED]
Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@go
This email address is no longer in service. Please use [EMAIL PROTECTED]
Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@go
This email address is no longer in service. Please use [EMAIL PROTECTED]
Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@go
This email address is no longer in service. Please use [EMAIL PROTECTED]
Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@go
On 6/1/07, Andreas Stuhlmüller <[EMAIL PROTECTED]> wrote:
>
> This week, I have started checking in code. I am always happy about
> feedback. Add a few lines to your (non-production!) urls.py [1], make
> your models available in XML or JSON format and tell me what works for
> you and what doesn't.
Hi Malcolm, thanks for taking the time to look this over.
On 6/1/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> (1) In core/management.py, there are a lot of lines that are
> doing the equivalent of;
>
> if opts.db_tablespace and backend.supports_tablespaces:
On 6/1/07, Ian Kelly <[EMAIL PROTECTED]> wrote:
> On 6/1/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > (2) The use of django.db.utils.truncate_name() introduces a
> > small backwards incompatible change for all existing backends.
> > With sufficiently long table and
This is the first weekly status update for my Summer of Code project,
a generic REST interface for Django. If you haven't seen it, take a
look at http://code.google.com/p/django-rest-interface/.
This week, I have started checking in code. I am always happy about
feedback. Add a few lines to your
On Jun 1, 8:50 am, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> ... Is there perhaps a VMWare
> image of a pre-installed Oracle that I can test this stuff against?
Oracle had a developer program called "Oracle By Example" (OBE) that
provides a VMware image with RedHat, Oracle 10gR2 RAC, etc.
On Jun 1, 4:19 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Fri, 2007-06-01 at 10:07 -0400, Benjamin Slavin wrote:
> > On 6/1/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > > You can't tell if it's an update without asking the database sometimes
> > > (if the primary key value i
Hi folks --
We talked about this a while back: Django really needs a buildbot (or
some other continuous integration tool). I had planned to tackle this
myself (using Bitten -- http://bitten.cmlenz.net/) but it's getting
clear I'm not going to get it done in any reasonable amount of time.
So, is
On 6/1/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> You're proposal (doing a database check and moving the "pre_save"
> dispatch lower) has introduced an extra database query for every single
> save, whether it's needed or not
Two points here...
First, there's already a database check for
On 6/1/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> Let's ask the different question: what's the use case for a pre_create
> signal that isn't already possible with pre_save?
In my case it's a matter of enforcing privileges. Highly granular
pirvileges can include "create" among other thin
On 6/1/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> I suspect my laxness has been holding up the boulder-oracle-sprint
> branch merge.
Yeah, I've also been bad about getting my review notes in. Now that you've
started this rolling, though, I'll just piggy-back off yours. For the most part,
On Sat, 2007-06-02 at 00:19 +1000, Malcolm Tredinnick wrote:
> On Fri, 2007-06-01 at 10:07 -0400, Benjamin Slavin wrote:
> > On 6/1/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > > You can't tell if it's an update without asking the database sometimes
> > > (if the primary key value is not
On Fri, 2007-06-01 at 10:07 -0400, Benjamin Slavin wrote:
> On 6/1/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > You can't tell if it's an update without asking the database sometimes
> > (if the primary key value is not None). So pre_save can't make it
> > available unless the semantics o
On 6/1/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> You can't tell if it's an update without asking the database sometimes
> (if the primary key value is not None). So pre_save can't make it
> available unless the semantics of "pre_save" change so that it's no
> longer prior to anything in
On 6/1/07, olive <[EMAIL PROTECTED]> wrote:
> This returns True:
> f = myform(data)
> f.is_valid()
>
> while this returns False:
> f = myform()
> f.data = data
> f.is_valid()
>
> Is it a bug ?
Not sure if it should be called a bug or not from a quick look at
the source code (django/newforms/f
On Fri, 2007-06-01 at 09:40 -0400, Benjamin Slavin wrote:
> On 5/31/07, Ben Schwarze <[EMAIL PROTECTED]> wrote:
> > What about a simple additional attribute that wil be. This could be
> > fetched in listener functions (e.g. is_update=True/False)?
> > [...]
> > Any ideas about that?
>
> I like thi
On 5/31/07, Ben Schwarze <[EMAIL PROTECTED]> wrote:
> What about a simple additional attribute that wil be. This could be
> fetched in listener functions (e.g. is_update=True/False)?
> [...]
> Any ideas about that?
I like this idea... and it shouldn't pose any problem with backwards
compatibility
On 6/1/07, Amit Upadhyay <[EMAIL PROTECTED]> wrote:
> How about doing a:
>
> self.is_new = not bool(self.id)
>
> in pre_save and
>
> if self.is_new: # do something
>
> in post_save?
Unfortunately, that won't work in the case of OneToOne models. They
are required to have their primary key value
I suspect my laxness has been holding up the boulder-oracle-sprint
branch merge. So, I sat down tonight with my notes, read through an
updated diff and removed anything that might be evidence I was on drugs
at the time. What follows is what remains. Nothing that is a showstopper
for merging in her
On 5/31/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> However, you're not the first to propose this. In fact, I would doubt
> that you are even the tenth. This is a pretty common request.
Yeah, I know I had seen at least one mention of it before, and I
figured it was fairly common. I was j
Despite having worked with a laptop day in day out, I only landed up
with aching wrists, strained neck and back; with my work still
pending. I could quote several reasons for it - my laptop processor
runs too hot, my laptop keeps slipping from the pillow, plus the
aching back. I know most of you a
n 5/31/07, Ben Schwarze <[EMAIL PROTECTED]> wrote:
>
>
> I've reconsidered the post_create signal issue, and can imagine that
> the pre_save and post_save signals may be extended. What about a
> simple additional attribute that wil be send. This could be fetched in
> listener functions (e.g. is_upd
41 matches
Mail list logo
