Re: schema-evolution: status?

i only ever made two commits into django's repo: changeset 3646 - the meat and potatoes changeset 3647 - test code can someone who knows svn better than i help me out as to how i would refresh the branch with the latest from the trunk, and then remerge these changes back into it? thanks, derek

Re: schema-evolution: status?

On 26-Oct-06, at 12:40 PM, Derek Anderson wrote: > can someone who knows svn better than i help me out as to how i would > refresh the branch with the latest from the trunk, and then remerge > these changes back into it? in your working copy root do: svn merge http://code.djangoproject.com/svn

Re: DecimalField

Am 25.10.2006 um 00:25 schrieb Jason Davies: > I am working on an application which deals with monetary values and it > *really* needs proper support for decimal, fixed-point (as opposed to > floating-point) values. > > See: http://code.djangoproject.com/ticket/2365 > > Could someone take a look a

Re: schema-evolution: status?

"svn merge http://code.djangoproject.com/svn/django/trunk"; gives me the "svn help merge" message. here's what i did: $ svn co http://code.djangoproject.com/svn/django/branches/schema-evolution/ django_tmp_src [normal checkout crap] $ cd django_tmp_src/ $ svn merge http://code.djangoproject.co

Re: fastcgi: maxRequests

Hi, the patch has been ready since yesterday but I can't create tickets (Akismet), so I dump it here (what can I do?)--the patch is attached. 'python manage.py runfcgi help' describes the additional parameter. Michael -- noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg - Tel +4

Re: schema-evolution: status?

Hey Derek, On Thu, 2006-10-26 at 03:30 -0500, Derek Anderson wrote: > "svn merge http://code.djangoproject.com/svn/django/trunk"; gives me the > "svn help merge" message. > > here's what i did: > > $ svn co > http://code.djangoproject.com/svn/django/branches/schema-evolution/ > django_tmp_src >

Re: Ticket spam

let me add the Akismet is not a solution, it looks like it has become part of the problem. It doesn't keep the spam out to a degree that could be ignored, but now it keeps me from opening tickets (yes, I sent the mail to Tom after digging through my email archive for his address--the whitelist

comment to ticket 2839

since my comment is rejected by Akismet, I´m posting it here ... in filterspecs, line 40 {{{ t.append(_('By %s:\n\n') % self.title()) }}} in filter.html, line 2 {{{ {% blocktrans with title|escape as filter_title %} By {{ filter_title }} {% endblocktrans %} }}} in django.po, line 354: {{{

Re: Re: schema-evolution: status?

Hi Derek, To do the merge you need to look at the last revision that you merged from trunk or in your case when your branch was created. In this case it is revision 3332. So to merge the latest trunk you need to: cd django_tmp_src svn merge -r 3332:HEAD http://code.djangoproject.com/svn/django/t

Re: Ticket spam

On 10/24/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > Also, I've been mulling over the idea of requiring an account signup > in order to post tickets and comments. Would that be worth the pain? I'm +1 on requiring an account signup; it's irritating to make wiki edits and append to tickets on

Re: DecimalField

On 10/26/06 2:49 AM, Christopher Lenz wrote: > Oh come on, just let Python 2.3 users install the decimal module from > SF: > > group_id=104148&package_id=130611&release_id=291663> > > I'd also suggest keeping FloatField as it is (i.e. half-b

Re: DecimalField

Jacob Kaplan-Moss wrote: > On 10/26/06 2:49 AM, Christopher Lenz wrote: > > Oh come on, just let Python 2.3 users install the decimal module from > > SF: > > > > > group_id=104148&package_id=130611&release_id=291663> > > > > I'd also suggest keep

Re: schema-evolution: status?

Matthew Flanagan wrote: > cd django_tmp_src > svn merge -r 3332:HEAD http://code.djangoproject.com/svn/django/trunk > > [resolve and conflicts and test your code] > svn co -m 'merged latest changes from trunk' I think that should be: svn ci -m 'merged latest changes from trunk' After you resolve

Comments system

The Wiki page on the API Stability says this about the comment system: > The comments framework, which is yet undocumented, will likely get a complete > rewrite > before Django 1.0. Even if the change isn't quite that drastic, there will at > least be > moderate changes. Are there goals or doc

Re: Comments system

On 10/26/06, Rob Hudson <[EMAIL PROTECTED]> wrote: > Are there goals or docs about what this might become? There seem to be > enough people using the comments systems that maybe people could work > on a patch (or at least get started in the right direction) if there > were some goals and ideas on

another ticket: related-object window is missing query ...

when doing a search in the related-object window in the admin- interface and using the link "xxx total" after that search, the query is missing. because "pop=1" is in the query, the header is shown ... using 0.95 thanks, patrick (don´t know if it is appropriate to post here, but since my tic

Re: Comments system

James Bennett wrote: > On 10/26/06, Rob Hudson <[EMAIL PROTECTED]> wrote: >> Are there goals or docs about what this might become? There seem to be >> enough people using the comments systems that maybe people could work >> on a patch (or at least get started in the right direction) if there >> w

spamblocked ticket: Use IPython profile if in current directory

"Akismet rejected spam", so, though very minor, here's my ticket. === Use IPython profile if in current directory === [http://ipython.scipy.org/ IPython] is great. It's profiles are very nice and it would be neat to use one if available. This patch offers a way to do that. It assumes that a

Re: schema-evolution: status?

thanks for your help. the merge went smoothly, and has been committed as revision 3937. Matthew Flanagan wrote: > Hi Derek, > > To do the merge you need to look at the last revision that you merged > from trunk or in your case when your branch was created. In this case > it is revision 3332.

Re: Ticket spam

Am 25.10.2006 um 17:22 schrieb Christopher Lenz: > Am 25.10.2006 um 11:24 schrieb Michael Radziej: >> Adrian Holovaty schrieb: Also, I've been mulling over the idea of requiring an account signup >>> in order to post tickets and comments. Would that be worth the pain? >> >> I wouldn't

Re: Comments system

On Thu, 2006-10-26 at 11:29 -0700, Rob Hudson wrote: > James Bennett wrote: > > On 10/26/06, Rob Hudson <[EMAIL PROTECTED]> wrote: > >> Are there goals or docs about what this might become? There seem to be > >> enough people using the comments systems that maybe people could work > >> on a patch

Jython with Django

Has anybody tested Django on Jython? I am interested in using simplified Java servlets with Jython and Django to add needed AJAX / AJAJ functionality to the ever interesting Django project. Thanks, JsD --~--~-~--~~~---~--~~ You received this message because you

Re: Re: Comments system

On 10/26/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > It might also be possible to achieve the same with model inheritance > because the way we have decided to expose that is via an attribute on > the base model. So if MyComment was a subclass of Comment, a Comment > instance would have a m

Re: Jython with Django

On 10/26/06, JsD <[EMAIL PROTECTED]> wrote: > I am interested in using simplified Java servlets with Jython and > Django to add needed AJAX / AJAJ functionality to the ever interesting > Django project. As far as I know, Jython is still "stuck" at a version of the Python language specification to

Call for comment: Forms/manipulator replacement, take 1

Hello all, I've attached the first draft implementation of the manipulator replacement framework -- it's just a single Python module. This handles validation, form display/redisplay and rendering of HTML form elements. It's mostly similar to what came out of the discussion here: http://groups.goo