I've added looking at this merge to my todo list for this week. It's a pretty crazy week at work, but to get passing tests, I'm willing to go out of my way as much as possible ;)
--Mark Ramm On Mon, Jan 25, 2010 at 12:25 AM, Anthony Theocharis <[email protected]> wrote: > The tests that fail in tg 2.0.3 should all be fixed in my branch, which is > waiting to be merged (nobody has offered yet) at > http://bitbucket.org/anthony.theocharis/tg-2_0 . > > I posted a message to the turbogears group, but I'll copy it to the tg-trunk > list here. I guess it's the more appropriate forum. > > -- Anthony > > > On 24-Jan-10, at 6:57 PM, percious wrote: >> >> For those of you who may have read this previously. The recommended >> way to patch TG (and have it easily accepted) is as follows: >> >> set up an account at http://bitbucket.org >> >> fork a copy of http://bitbucket.org/turbogears/tg-dev >> >> clone your forked copy. >> >> Make your changes. >> >> Changes that include tests that break before the fix, but work after >> the fix are more easily integrated. Also, be sure that your new code >> does not break the existing tests. >> >> push your changes up to your repo. >> >> send a pull request, open a ticket in trac with a description of the >> problem and solution. >> >> cheers. >> -chris >> >> On Dec 1 2009, 7:00 am, "Diez B. Roggisch" <[email protected]> wrote: >>> >>> Bump. >>> >>> No takers on this? >>> >>> Additionally, I'm having difficulties with mercurial to create a patch >>> for the >>> 2.1-branch of my working fix for the before_call-fix - at least in >>> the "mercurial way". Can anybody lend me a hand on this? that would be >>> great. >>> >>> Diez >>> >>> >>> >>>> I'm attending to some bugs in 2.0.3 we hit. When running the test-suite, >>>> there are 4 tests failing: >>> >>>> tg.tests.test_tg_controller_dispatch:TestTGController.test_new_default >>> >>>> tg.test_stack.rendering.test_custom_format:test_html_custom_format >>>> tg.test_stack.rendering.test_custom_format:test_xml_custom_format >>>> tg.test_stack.rendering.test_custom_format:test_json_custom_format >>> >>>> Can somebody confirm this? >>> >>>> The custom-format-stuff is especially dangerous, because without it >>>> running >>>> the much bigger error lurking behind it can't be fixed. It has the same >>>> race-condition issues that I already fixed for override_template. >>> >>>> Diez >>> >>>> -- >>> >>>> 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 >>>> athttp://groups.google.com/group/turbogears-trunk?hl=en. >> >> -- >> 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. >> > > -- > 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. > > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog -- 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.
