On 4/21/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
>
> Hi Limodou.
> Thanks for the reply.
>
> what I was trying to do was slightly different.
>
> def all_models_setup_post_init():
> for ct in Comments.get_content_types():
> ... add the query objects to the ct's model
>
> so i have
On 4/21/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
> so i have two problems.. the first is:
> - is there some dispatch thing I can connect to so that this function
> gets called at the right time
To clarify a bit after some late-night IRC chatting about this:
What Ian's trying to do, basically,
Hi,
I just posted some issues with i18n in M-R on django-i18n:
http://groups.google.com/group/Django-I18N/browse_thread/thread/26cc1ad95bf845bd
Two of the issues are very easy to solve, by adding 'verbose_name' to
the ManyToMany fields of the User and Group model. For the other issues
I do not h
There was a diff submitted by Geert Vanderkelen awhile ago. It doesn't
apply cleanly to 'core/management.py' anymore.
Is there a reason it wasn't commited?
If I fix it to work with current release will someone commit it? I
assume svn ci is restricted.
--~--~-~--~~~---
On Apr 21, 2006, at 7:10 AM, njharman wrote:
> There was a diff submitted by Geert Vanderkelen awhile ago. It
> doesn't
> apply cleanly to 'core/management.py' anymore.
>
> Is there a reason it wasn't commited?
Most likely nobody got a chance to look at it until the patch no
longer applied c
>By way of process - Is the plan to make a formal release after the merge, or
>will the "MR Trunk" be allowed to settle a little longer before we formally
>tag a release? And, to follow a previous disussion, are we going to tag the
>current state of trunk as a 0.92 release reflecting all the trunk
Jacob Kaplan-Moss wrote:
> On Apr 21, 2006, at 7:10 AM, njharman wrote:
>
>>There was a diff submitted by Geert Vanderkelen awhile ago. It
>>doesn't
>>apply cleanly to 'core/management.py' anymore.
>>If I fix it to work with current release will someone commit it? I
>>assume svn ci is restric
On Thursday 20 April 2006 22:26, Adrian Holovaty wrote:
> At this point, Django's magic-removal branch is stable enough that
> we're ready to begin the merging process. I've been running the
> branch on chicagocrime.org for a couple of weeks with no problems. As
> of right now, Jacob and I are fr
Ticket marked wontfix. Seems rather harsh to force MySQL users into
editing output of manage.py and commands like 'install' just won't work.
Politely asking if this decision might be reconsidered if a clean
solution could be found.
If not, a warning / note in the docs about the limitations of M
It's a bit hard trying to piece together the history of this from
listarchives and tickets. It seems that putting models in a package
instead of 'models.py' should work and is believed to work.
I can verify that for MR-r2717 'models/__init__.py' does not work. In
that 'manage.py sql' produces n
This is great news. I've been using M-R for a couple months on a
restricted-access production site and am very happy with it.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to thi
njharman wrote:
> Ticket marked wontfix. Seems rather harsh to force MySQL users into
> editing output of manage.py and commands like 'install' just won't work.
Alternatively, set default table type in your database to InnoDB, and
you're fine.
Michael
--~--~-~--~~~---
On 4/21/06, Luke Plant <[EMAIL PROTECTED]> wrote:
> Great news Adrian. I was just about to add my CsrfMiddleware into
> contrib (see other thread) - but now you've called feature freeze.
> Shall I still go ahead and add it? It can't affect anything else since
> it isn't actually used anywhere.
Michael Radziej wrote:
> njharman wrote:
>>Ticket marked wontfix. Seems rather harsh to force MySQL users into
>>editing output of manage.py and commands like 'install' just won't work.
> Alternatively, set default table type in your database to InnoDB, and
> you're fine.
Didn't know such a thin
Hi,
njharman wrote:
> Michael Radziej wrote:
>> njharman wrote:
>>> Ticket marked wontfix. Seems rather harsh to force MySQL users into
>>> editing output of manage.py and commands like 'install' just won't work.
>> Alternatively, set default table type in your database to InnoDB, and
>> you're
Is there any chance http://code.djangoproject.com/ticket/1637 can be applied soon? The ticket seemed to have fallen off the radar, and I can't completely move to magic-removal (soon to be trunk) until comments work.
Dave
--~--~-~--~~~---~--~~
You received this mess
On 4/21/06, Dave St.Germain <[EMAIL PROTECTED]> wrote:
> Is there any chance
> http://code.djangoproject.com/ticket/1637 can be applied
> soon? The ticket seemed to have fallen off the radar, and I can't
> completely move to magic-removal (soon to be trunk) until comments work.
Which patch there
On 4/21/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> Which patch there is the "one true patch"(tm) ;) comments.3.diff?
Looks like it; it seems to match pretty closely with the patches I'd
submitted on #1659, which cover parts of the comments app as well (and
on that ticket, the most recent
On 4/21/06, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 4/21/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
> > Which patch there is the "one true patch"(tm) ;) comments.3.diff?
>
> Looks like it; it seems to match pretty closely with the patches I'd
> submitted on #1659, which cover parts o
I posted this to django-users a few days ago but no one commented and I
didn't see any mention of it here so I thought I'd repost to the dev
group. I'm using M-R and just updated to 2721 and still didn't see a
fix.
If you use a FloatField in the admin list_display, you get an error
rendering the
Maybe I don't understand the implications but I have been using
ENGINE=MyISAM on my tables so I can use MySQLs full-text indexing (not
supported by InnoDB).
Does this thread imply that I can no longer use MyISAM tables with
MySQL? Or just that if I do, I must tweak the output of manage.py
(which
DavidA wrote:
> Maybe I don't understand the implications but I have been using
> ENGINE=MyISAM on my tables so I can use MySQLs full-text indexing (not
> supported by InnoDB).
>
> Does this thread imply that I can no longer use MyISAM tables with
> MySQL? Or just that if I do, I must tweak the o
22 matches
Mail list logo
