Hi
I've been using the form wizard for an convention sign-up application.
I felt that the FormWizard is strange. It's not a form class, neither
a view function but something inbetween. I'm going to EuroPython and
wonder if anyone out there would like to join me for a FormWizard-
rewrite-sprint? My
On Sat, May 31, 2008 at 9:25 AM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
>
> Hi folks --
>
> I'm being bitten by http://code.djangoproject.com/ticket/6886. Short
> version: ``object.related = obj`` doesn't stick the assigned object in
> the model cache (the same way accessing ``object.related
Hello django-devs!
FWIW, I'm forwarding my GSoC weekly report to this list. Any ideas,
comments, flames, etc are welcome.
-- Forwarded message --
From: Leo Soto M. <[EMAIL PROTECTED]>
Date: Sat, May 31, 2008 at 12:00 AM
Subject: GSoC Weekly Report: Django on Jython
To: JythonDev
Hi folks --
I'm being bitten by http://code.djangoproject.com/ticket/6886. Short
version: ``object.related = obj`` doesn't stick the assigned object in
the model cache (the same way accessing ``object.related`` does) and
can lead to weird mis-matches between modified objects and ones fresh
from t
On May 30, 2008, at 7:29 PM, Jeremy Dunck wrote:
>
> On Fri, May 30, 2008 at 5:16 PM, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
>>
>> Let's discuss the ORM save() method. In my opinion, unless I grossly
>> misunderstand what's going on it seems the save method is very
>> magical.
>>
>> Firs
On Fri, May 30, 2008 at 7:29 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
> On Fri, May 30, 2008 at 5:16 PM, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
> >
> > Let's discuss the ORM save() method. In my opinion, unless I grossly
> > misunderstand what's going on it seems the save method is ve
On Fri, May 30, 2008 at 5:16 PM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> Let's discuss the ORM save() method. In my opinion, unless I grossly
> misunderstand what's going on it seems the save method is very
> magical.
>
> First, some confirmations; The save method will INSERT a row into t
On Thu, May 29, 2008 at 10:19 AM, Johannes Dollinger
<[EMAIL PROTECTED]> wrote:
> I'm quite new to django (first real project) and stumbled across several
> bugs/features that I'd like to see in trunk. And I'm willing and
> hopefully able to help.
Awesome :)
> Where should I start?
Well, the st
Let's discuss the ORM save() method. In my opinion, unless I grossly
misunderstand what's going on it seems the save method is very
magical.
First, some confirmations; The save method will INSERT a row into the
database if it doesn't exist, always. The save method will UPDATE a
row that exists in
My goal is to eventually be able to run multiple Django projects in
the same WSGI server instance. I believe that translates into Django
being loaded at the process level but the Django projects (i.e. the
requests for a project) being run at the thread level.
My lack of experience in Python is
I'm not sure if this a bug, maybe somebody can tell:
(Django latest trunk on both machines)
On my local devserver (python 2.5 ubuntu) I had the following line:
menu = models.ForeignKey('menubuilder.menu')
This gave an instance of the object Menu the attr "article_set"
the above worked on the devs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> At a very high level, I have an application, which holds many
> organisations, and these organisations each contain many products. I
> may need to at times, partition the product data, so that some
>
The easy way (and what I do now) is create your "skel" folder in SVN
(or whatever you use), then just do an svn copy for new projects and
away you go. That way you can also store common svn:externals or
svn:ignore properties in your directory structure as well.
On May 29, 12:12 am, phillc <[EMAI
13 matches
Mail list logo