Daniel Fetchinson schrieb: >> Sorry for the duplicate ticket, Daniel. Just trying to make sure your patch >> didn't get lost in the shiffle. > > No problem :) > Just noticed the duplicate, the thing is that on the version I sent to > the mailing list from which you created ticket/1710 the names were > such as OnetimeTask, add_onetime_task, etc and on ticket/1709 I > renamed them to SingleTask, add_single_task, etc because Chris > mentioned PEP-8 which I took to mean that Onetime should be OneTime > which didn't look very good to me.
No, I meant the improper white space after opening parantheses and such things. Anyway, I'm just in the process of cleaning up the whole scheduler mdoule and making it PEP-8 compliant. I'll then integrate your new patch with the new names (which I like better). It'll be ready in a couple of minutes. > In addition ticket/1709 is for trunk 1.1 while ticket/1710 is for > trunk 1.0 (although as far as I can tell scheduler.py is the same), > again something Chris asked for so I guess 1709 is the relevant ticket > not 1710 (although as things are marked now, 1709 is closed and 1710 > is open). Kinda confusing :) I don't think we should have two different tickets for the same issue for the different branches. New features should go in bramch 1.1 and if we want to backport them to 1.0, we can open a ticket for this task once the feature is complete in 1.1. Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
