creoleparser - Project Hosting on Google Code

Last 30 days Dec 11, 2009 r171 (fixed cheatsheet link) committed by stephen.h.day - fixed cheatsheet link fixed cheatsheet link Dec 11, 2009 r170 (fixed test) committed by stephen.h.day - fixed test fixed test Dec 11, 2009 r169 (DOCTYPE fixed) committed by stephen.h.day - DOCTYPE fixed DOCTYPE fixed Dec 11, 2009 r168 (added mimetype) committed by stephen.h.day - added mimetype added mimetype Dec 11, 2009 r167 (changed mimetype) committed by stephen.h.day - changed mimetype changed mimetype Earlier this year Aug 20, 2009 issue 29 (Add preprocess option to Parser.generate()) reported by stephen.h.day - Preprocessing is only done if context='block'. This could be problematic. Change behavior so preprocessing always happens unless explicitly turned off. Preprocessing is only done if context='block'. This could be problematic. Change behavior so preprocessing always happens unless explicitly turned off. Jun 29, 2009 issue 28 (Block macros with attributes) Status changed by stephen.h.day - No problem Status: Invalid No problem Status: Invalid Jun 29, 2009 issue 28 (Block macros with attributes) commented on by afief.h - Sorry, my bad, I misunderstood how macros are supposed to work Sorry, my bad, I misunderstood how macros are supposed to work Jun 28, 2009 issue 28 (Block macros with attributes) Owner changed by stephen.h.day - Block macro's use a special syntax. As long as that is followed, attributes should work fine. See the explanation here: http://creoleparser.googlecode.com/svn/docs/syntax.html On the other hand, your example is not what creoleparser calls a "block" macro. It's just a plain "bodied" macro and should work fine as you've written it. Perhaps the formatting was lost when you created the issue? Owner: stephen.h.day Block macro's use a special syntax. As long as that is followed, attributes should work fine. See the explanation here: http://creoleparser.googlecode.com/svn/docs/syntax.html On the other hand, your example is not what creoleparser calls a "block" macro. It's just a plain "bodied" macro and should work fine as you've written it. Perhaps the formatting was lost when you created the issue? Owner: stephen.h.day Jun 28, 2009 issue 28 (Block macros with attributes) reported by afief.h - The following is not possible: <<fontsize size=5>> some text <</fontsize>> The example is not very useful but there are cases where attributes are desirable for block macros. In my case I have made a math plugin, and would like to be able to chose between display style(bigger, centered) and inline style without making two separate macros. The following is not possible: <<fontsize size=5>> some text <</fontsize>> The example is not very useful but there are cases where attributes are desirable for block macros. In my case I have made a math plugin, and would like to be able to chose between display style(bigger, centered) and inline style without making two separate macros. Apr 03, 2009 issue 27 (Macros work on only a single paragraph) Status changed by stephen.h.day - Thanks for letting me know :) Status: Invalid Thanks for letting me know :) Status: Invalid Apr 03, 2009 issue 27 (Macros work on only a single paragraph) commented on by montystyles - Sorry, you're completely right. This is not a bug, I was entering it in wrong. Sorry, you're completely right. This is not a bug, I was entering it in wrong. Apr 02, 2009 issue 27 (Macros work on only a single paragraph) commented on by stephen.h.day - Note that macros only span paragraphs if a special syntax is used: http://creoleparser.googlecode.com/svn/docs/syntax.html#macros Note that macros only span paragraphs if a special syntax is used: http://creoleparser.googlecode.com/svn/docs/syntax.html#macros Apr 02, 2009 issue 27 (Macros work on only a single paragraph) changed by stephen.h.day - Hi, I am not able to reproduce this and I am not able to test on a Mac (although I can't see this making a difference). Please try this first for a sanity check: >>> from creoleparser import Parser, creole11_base, create_dialect >>> parse = Parser(create_dialect(creole11_base)) >>> parse("{{{\nHello\n\nWorld\n}}}") '<pre>Hello\n\nWorld\n</pre>\n' If this works as expected, please send a full code example and I'll try again to reproduce. Steve Status: Started Owner: stephen.h.day Hi, I am not able to reproduce this and I am not able to test on a Mac (although I can't see this making a difference). Please try this first for a sanity check: >>> from creoleparser import Parser, creole11_base, create_dialect >>> parse = Parser(create_dialect(creole11_base)) >>> parse("{{{\nHello\n\nWorld\n}}}") '<pre>Hello\n\nWorld\n</pre>\n' If this works as expected, please send a full code example and I'll try again to reproduce. Steve Status: Started Owner: stephen.h.day Apr 02, 2009 issue 27 (Macros work on only a single paragraph) reported by montystyles - What steps will reproduce the problem? 1. Make a piece of text with either a macro <<mymacro>>blah<</mymacro>> where the innards have two repeated '\n's, e.g. <<code>> Hey there big guy <</code>> 2. Try to parse this through creoleparser 3. Realize that it doesn't see the macro as having a body. What is the expected output? What do you see instead? I expect that the entire middle between the macro beginning and end is fed in as the body, but only the beginning tag is and it acts as if it has no body. What version of the product are you using? On what operating system? CreoleParser 0.6.0, using creole11_base. Python 2.5 on Mac OS X 10.5 and Ubuntu Linux. Please provide any additional information below. This also occurs for pre statements, e.g. {{{ Hey there big guy }}} What steps will reproduce the problem? 1. Make a piece of text with either a macro <<mymacro>>blah<</mymacro>> where the innards have two repeated '\n's, e.g. <<code>> Hey there big guy <</code>> 2. Try to parse this through creoleparser 3. Realize that it doesn't see the macro as having a body. What is the expected output? What do you see instead? I expect that the entire middle between the macro beginning and end is fed in as the body, but only the beginning tag is and it acts as if it has no body. What version of the product are you using? On what operating system? CreoleParser 0.6.0, using creole11_base. Python 2.5 on Mac OS X 10.5 and Ubuntu Linux. Please provide any additional information below. This also occurs for pre statements, e.g. {{{ Hey there big guy }}} Mar 31, 2009 r166 (updated CHANGES.txt) committed by stephen.h.day - updated CHANGES.txt updated CHANGES.txt Mar 31, 2009 r165 (added indentation support) committed by stephen.h.day - added indentation support added indentation support Mar 30, 2009 r164 (docs update) committed by stephen.h.day - docs update docs update Mar 30, 2009 r163 (0.6.1 tagged) committed by stephen.h.day - 0.6.1 tagged 0.6.1 tagged Mar 30, 2009 r162 (added date to CHANGES.txt) committed by stephen.h.day - added date to CHANGES.txt added date to CHANGES.txt Mar 30, 2009 r161 (forgot sphinx css file) committed by stephen.h.day - forgot sphinx css file forgot sphinx css file Mar 30, 2009 r160 (checkin before release updated docs added convert_implicit_l...) committed by stephen.h.day - checkin before release updated docs added convert_implicit_lists removed force_strings checkin before release updated docs added convert_implicit_lists removed force_strings Mar 29, 2009 r159 (refactoring of argument parsing work on docs) committed by stephen.h.day - refactoring of argument parsing work on docs refactoring of argument parsing work on docs Mar 29, 2009 r158 (work on docs) committed by stephen.h.day - work on docs work on docs Mar 28, 2009 r157 (keywords must be type str (not unicode)) committed by stephen.h.day - keywords must be type str (not unicode) keywords must be type str (not unicode) Mar 28, 2009 r156 (mostly work on the docs) committed by stephen.h.day - mostly work on the docs mostly work on the docs Mar 24, 2009 r155 (refactored fill_from_store to use finditer (over 2 fold fast...) committed by stephen.h.day - refactored fill_from_store to use finditer (over 2 fold faster!) refactored fill_from_store to use finditer (over 2 fold faster!) Mar 24, 2009 r154 (trailing slash (/) is removed from macro arg_string) committed by stephen.h.day - trailing slash (/) is removed from macro arg_string trailing slash (/) is removed from macro arg_string Mar 24, 2009 r153 (refactoring of new argument parsing dialect ) committed by stephen.h.day - refactoring of new argument parsing dialect refactoring of new argument parsing dialect Mar 22, 2009 r152 (added argument parser for macros) committed by stephen.h.day - added argument parser for macros added argument parser for macros Mar 15, 2009 r151 (refactoring for fragmentize() and _process methods) committed by stephen.h.day - refactoring for fragmentize() and _process methods refactoring for fragmentize() and _process methods Mar 14, 2009 r150 (refactored main _process method to avoid recursion issues no...) committed by stephen.h.day - refactored main _process method to avoid recursion issues now able to removed complicated preprocessing refactored main _process method to avoid recursion issues now able to removed complicated preprocessing Mar 14, 2009 issue 25 (RuntimeError("maximum recursion depth exceeded") with long b...) Status changed by stephen.h.day - Fixed. No crippled WikiElement needed :) http://code.google.com/p/creoleparser/source/detail?r=149 Status: Fixed Fixed. No crippled WikiElement needed :) http://code.google.com/p/creoleparser/source/detail?r=149 Status: Fixed Mar 14, 2009 r149 (fixed recursion issue with long lists and tables (>400 rows)...) committed by stephen.h.day - fixed recursion issue with long lists and tables (>400 rows) (see issue 25 ) fixed recursion issue with long lists and tables (>400 rows) (see issue 25 ) Mar 11, 2009 issue 25 (RuntimeError("maximum recursion depth exceeded") with long b...) changed by stephen.h.day - This problem is similar to issue 2 and is common to recursive-descent type parsers (like creoleparser). I think a fair solution would be to make a special, crippled, WikiElement that creoleparser uses for lists when a recursion error happens. In this case, very long lists wouldn't support nesting (for example). Status: Accepted Owner: stephen.h.day This problem is similar to issue 2 and is common to recursive-descent type parsers (like creoleparser). I think a fair solution would be to make a special, crippled, WikiElement that creoleparser uses for lists when a recursion error happens. In this case, very long lists wouldn't support nesting (for example). Status: Accepted Owner: stephen.h.day Mar 11, 2009 issue 25 (RuntimeError("maximum recursion depth exceeded") with long b...) commented on by stephen.h.day - Issue 26 has been merged into this issue. Issue 26 has been merged into this issue. Mar 11, 2009 issue 26 (RuntimeError("maximum recursion depth exceeded") with long b...) changed by stephen.h.day - Status: Duplicate Status: Duplicate Mar 11, 2009 issue 26 (RuntimeError("maximum recursion depth exceeded") with long b...) reported by ckknight - What steps will reproduce the problem? 1. make a really long bullet list. Mine had about 400 lines total. 2. render What is the expected output? What do you see instead? It should generate the proper ul list. A RuntimeError with the message "maximum recursion depth exceeded" What version of the product are you using? On what operating system? Creoleparser-0.6-py2.5.egg on Linux and Mac OS X. Using the creole11_base dialect. Please provide any additional information below. It appears to be bouncing between core.py line 152 [frags = wiki_element._process(mo, text, wiki_elements, element_store, environ)] and elements.py lines 124-125 [frags.extend(fragmentize(text[mo.end ():],wiki_elements, element_store, environ))] What steps will reproduce the problem? 1. make a really long bullet list. Mine had about 400 lines total. 2. render What is the expected output? What do you see instead? It should generate the proper ul list. A RuntimeError with the message "maximum recursion depth exceeded" What version of the product are you using? On what operating system? Creoleparser-0.6-py2.5.egg on Linux and Mac OS X. Using the creole11_base dialect. Please provide any additional information below. It appears to be bouncing between core.py line 152 [frags = wiki_element._process(mo, text, wiki_elements, element_store, environ)] and elements.py lines 124-125 [frags.extend(fragmentize(text[mo.end ():],wiki_elements, element_store, environ))] Mar 11, 2009 issue 25 (RuntimeError("maximum recursion depth exceeded") with long b...) reported by ckknight - What steps will reproduce the problem? 1. make a really long bullet list. Mine had about 400 lines total. 2. render What is the expected output? What do you see instead? It should generate the proper ul list. A RuntimeError with the message "maximum recursion depth exceeded" What version of the product are you using? On what operating system? Creoleparser-0.6-py2.5.egg on Linux and Mac OS X. Using the creole11_base dialect. Please provide any additional information below. It appears to be bouncing between core.py line 152 [frags = wiki_element._process(mo, text, wiki_elements, element_store, environ)] and elements.py lines 124-125 [frags.extend(fragmentize(text[mo.end ():],wiki_elements, element_store, environ))] What steps will reproduce the problem? 1. make a really long bullet list. Mine had about 400 lines total. 2. render What is the expected output? What do you see instead? It should generate the proper ul list. A RuntimeError with the message "maximum recursion depth exceeded" What version of the product are you using? On what operating system? Creoleparser-0.6-py2.5.egg on Linux and Mac OS X. Using the creole11_base dialect. Please provide any additional information below. It appears to be bouncing between core.py line 152 [frags = wiki_element._process(mo, text, wiki_elements, element_store, environ)] and elements.py lines 124-125 [frags.extend(fragmentize(text[mo.end ():],wiki_elements, element_store, environ))] Mar 07, 2009 issue 24 (Many creoleparser markup blocks need terminal newlines to wo...) Status changed by stephen.h.day - fixed, extra preprocessing was also removed Status: Fixed fixed, extra preprocessing was also removed Status: Fixed Mar 07, 2009 issue 24 (Many creoleparser markup blocks need terminal newlines to wo...) reported by stephen.h.day - Many creoleparser markup blocks need terminal newlines to work. In order to compensate for this, a newline have to be added to input text. Many creoleparser markup blocks need terminal newlines to work. In order to compensate for this, a newline have to be added to input text. Mar 07, 2009 r148 (no longer appending \n during preprocessing needed to tweak ...) committed by stephen.h.day - no longer appending \n during preprocessing needed to tweak several WikiElement re's for this no longer appending \n during preprocessing needed to tweak several WikiElement re's for this Mar 01, 2009 r147 (Typos in the docs) committed by stephen.h.day - Typos in the docs Typos in the docs Feb 28, 2009 r146 (live documentation for 0.6 committed) committed by stephen.h.day - live documentation for 0.6 committed live documentation for 0.6 committed Feb 28, 2009 r145 (date fixed in CHANGES.txt) committed by stephen.h.day - date fixed in CHANGES.txt date fixed in CHANGES.txt Feb 28, 2009 r144 (last doc update before release) committed by stephen.h.day - last doc update before release last doc update before release Feb 28, 2009 r143 (0.6 tagged) committed by stephen.h.day - 0.6 tagged 0.6 tagged Feb 28, 2009 r142 (final refactoring of dialects.py) committed by stephen.h.day - final refactoring of dialects.py final refactoring of dialects.py Feb 28, 2009 r141 (small change to 0.5.1 docs) committed by stephen.h.day - small change to 0.5.1 docs small change to 0.5.1 docs Feb 28, 2009 r140 (maintenance of 0.5.1 docs) committed by stephen.h.day - maintenance of 0.5.1 docs maintenance of 0.5.1 docs

issue 27 (Macros work on only a single paragraph) reported by montystyles - What steps will reproduce the problem? 1. Make a piece of text with either a macro <<mymacro>>blah<</mymacro>> where the innards have two repeated '\n's, e.g. <<code>> Hey there big guy <</code>> 2. Try to parse this through creoleparser 3. Realize that it doesn't see the macro as having a body. What is the expected output? What do you see instead? I expect that the entire middle between the macro beginning and end is fed in as the body, but only the beginning tag is and it acts as if it has no body. What version of the product are you using? On what operating system? CreoleParser 0.6.0, using creole11_base. Python 2.5 on Mac OS X 10.5 and Ubuntu Linux. Please provide any additional information below. This also occurs for pre statements, e.g. {{{ Hey there big guy }}}

What steps will reproduce the problem? 1. Make a piece of text with either a macro <<mymacro>>blah<</mymacro>> where the innards have two repeated '\n's, e.g. <<code>> Hey there big guy <</code>> 2. Try to parse this through creoleparser 3. Realize that it doesn't see the macro as having a body. What is the expected output? What do you see instead? I expect that the entire middle between the macro beginning and end is fed in as the body, but only the beginning tag is and it acts as if it has no body. What version of the product are you using? On what operating system? CreoleParser 0.6.0, using creole11_base. Python 2.5 on Mac OS X 10.5 and Ubuntu Linux. Please provide any additional information below. This also occurs for pre statements, e.g. {{{ Hey there big guy }}}

Last 30 days

Earlier this year