I am also curious about this. With in the next few weeks I have a
project that will need a HTML editor in the admin interface. If this
work will include it I would be happy to wait versus having to branch
off from trunk.
--~--~-~--~~~---~--~~
You received this mes
Let's return to this subject, which was discussed a couple of weeks
ago. Here's my latest thinking on the subject.
* Automatic manipulators go away. Instead of messing with those, to
create a new model object you try instantiating it. Validation errors
are raised at that point. Example:
try:
hi.
So I have my tagging and auditing application on the current trunk,
and they service their purpose well.
but I'd like to know the 'best' way to rewrite this in the magic-removal trunk.
when magic removal was first proposed it mentioned that these kind of
things would be much easier.
so.. h
On 22/02/2006, at 12:34 PM, Luke Plant wrote:
>
> For now, if you have deadlines then trunk is the way to go (yep, bad
> timing for that advice, sorry). While migration will be a bit of a
> pain and tedious, it will at least be reasonably straightforward.
>
> Sorry for the difficulties you've ha
On 2/22/06, Luke Plant <[EMAIL PROTECTED]> wrote:
>
> On Tuesday 21 February 2006 22:57, Nick Phillips wrote:
>
> > "Bugger. NameError at /admin/foo/bar/person/1/delete/
> > global name 'ObjectDoesNotExist' is not defined. What have I let
> > myself in for here? I mean, does anyone actually *run*
On Tuesday 21 February 2006 22:57, Nick Phillips wrote:
> "Bugger. NameError at /admin/foo/bar/person/1/delete/
> global name 'ObjectDoesNotExist' is not defined. What have I let
> myself in for here? I mean, does anyone actually *run* this magic-
> removal stuff?"
>
>
> If it weren't for the fac
On 2/22/06, Luke Plant <[EMAIL PROTECTED]> wrote:
- #1346 (and probably others)A quick heads up - I've been working on this one, and I've almost got it sorted out. Russ Magee %-)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Googl
On 22/02/2006, at 10:58 AM, Jacob Kaplan-Moss wrote:
>
> I, for one, want to get m-r wrapped up and merged back to trunk as
> soon as humanely possible. I feel like it's starting to be a drag on
> new users trying to figure out why development on trunk seems to have
> stopped, and I want to get u
In my model, I have a date_created field that is defined as :
date_created = meta.DateField(auto_now_add = True, db_index = True)
This field is correctly auto-populated upon creation when I invoke
creation of the objects through a web interface (either the admin or my
own). However, when I creat
On Feb 21, 2006, at 3:33 PM, gabor wrote:
> http://wiki.python.org/moin/PyCon2006/Sprints/DjangoSprint
>
> unfortunately no trace of magic-removal :(
That's really only a rough guide. I'd hoped that magic-removal would
be mostly done by PyCon, but as that won't happen chances are much of
PyC
Luke Plant wrote:
>
> Also, Jacob is doing Django sprint at PyCon AFAIK, which might affect
> all this. I'm not sure whether Jacob was planning on working on
> magic-removal or trunk.
http://wiki.python.org/moin/PyCon2006/Sprints/DjangoSprint
unfortunately no trace of magic-removal :(
gabor
Hi Christopher,
I'll speak out of turn here and say I how see things from my limited
experience with the project/code.
> Other issues include the broken content-types stuff (#1280... why's
> that patch not checked in yet?)
There hasn't been that much activity on magic-removal for the past few
Am 09.02.2006 um 15:34 schrieb Jacob Kaplan-Moss:
> On Feb 9, 2006, at 2:55 AM, Ian Holsman wrote:
>> a while back Euguene mentioned on djnago-users that 0.92 will have
>> dojo ajax components in the admin interface.
>>
>> is this being developed on a seperate branch?
>> I'd like to talk about the
Hey folks,
We've just started a new project here with Django and decided to
build it on top of the magic-removal branch, since the project is
going to be worked on for a couple of months.
Now, actually using the magic-removal is currently raising more
problems than I had hoped. I've been l
It seems that I cannot define two and more OneToOneFields in a model.
If I do so, then as I install the app, django will complain that:
CREATE TABLE "user_profile_userprofile" (
"user_id" integer NOT NULL PRIMARY KEY,
"portrait" varchar(100) NOT NULL,
"blog_setting_id" integer NOT NUL
15 matches
Mail list logo
