docutils-users — General discussions, questions, help requests.
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(15) |
Oct
(21) |
Nov
(18) |
Dec
(59) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(43) |
Feb
(35) |
Mar
(78) |
Apr
(65) |
May
(163) |
Jun
(169) |
Jul
(137) |
Aug
(77) |
Sep
(47) |
Oct
(27) |
Nov
(43) |
Dec
(68) |
| 2004 |
Jan
(61) |
Feb
(39) |
Mar
(11) |
Apr
(42) |
May
(86) |
Jun
(82) |
Jul
(24) |
Aug
(26) |
Sep
(37) |
Oct
(62) |
Nov
(131) |
Dec
(43) |
| 2005 |
Jan
(31) |
Feb
(56) |
Mar
(65) |
Apr
(165) |
May
(106) |
Jun
(97) |
Jul
(65) |
Aug
(150) |
Sep
(78) |
Oct
(115) |
Nov
(41) |
Dec
(26) |
| 2006 |
Jan
(50) |
Feb
(39) |
Mar
(56) |
Apr
(67) |
May
(89) |
Jun
(68) |
Jul
(116) |
Aug
(65) |
Sep
(58) |
Oct
(103) |
Nov
(28) |
Dec
(52) |
| 2007 |
Jan
(92) |
Feb
(60) |
Mar
(124) |
Apr
(96) |
May
(69) |
Jun
(79) |
Jul
(25) |
Aug
(22) |
Sep
(7) |
Oct
(17) |
Nov
(27) |
Dec
(32) |
| 2008 |
Jan
(57) |
Feb
(87) |
Mar
(51) |
Apr
(43) |
May
(56) |
Jun
(62) |
Jul
(25) |
Aug
(82) |
Sep
(58) |
Oct
(42) |
Nov
(38) |
Dec
(86) |
| 2009 |
Jan
(50) |
Feb
(33) |
Mar
(84) |
Apr
(90) |
May
(109) |
Jun
(37) |
Jul
(22) |
Aug
(51) |
Sep
(93) |
Oct
(86) |
Nov
(31) |
Dec
(62) |
| 2010 |
Jan
(33) |
Feb
(57) |
Mar
(62) |
Apr
(43) |
May
(30) |
Jun
(49) |
Jul
(20) |
Aug
(40) |
Sep
(152) |
Oct
(38) |
Nov
(15) |
Dec
(32) |
| 2011 |
Jan
(29) |
Feb
(25) |
Mar
(65) |
Apr
(45) |
May
(27) |
Jun
(11) |
Jul
(14) |
Aug
(8) |
Sep
(13) |
Oct
(117) |
Nov
(60) |
Dec
(19) |
| 2012 |
Jan
(23) |
Feb
(32) |
Mar
(24) |
Apr
(41) |
May
(56) |
Jun
(24) |
Jul
(15) |
Aug
(11) |
Sep
(26) |
Oct
(21) |
Nov
(12) |
Dec
(31) |
| 2013 |
Jan
(32) |
Feb
(24) |
Mar
(39) |
Apr
(44) |
May
(44) |
Jun
(8) |
Jul
(9) |
Aug
(12) |
Sep
(34) |
Oct
(19) |
Nov
(5) |
Dec
(9) |
| 2014 |
Jan
(22) |
Feb
(12) |
Mar
(7) |
Apr
(2) |
May
(13) |
Jun
(17) |
Jul
(8) |
Aug
(10) |
Sep
(7) |
Oct
(4) |
Nov
|
Dec
(39) |
| 2015 |
Jan
(13) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Andrew V. Stepanov <stanv@al...> - 2015-01-28 09:17:44
|
27.01.15 18:29, David Goodger пишет: > I'm not willing to download all the bits & pieces to try to guess > what's missing. Perhaps someone on the BRO or Pygments development > teams can help you out. > > -- David Goodger Thank you. BRO developer helped me ) Commit is https://github.com/bro/bro/commit/36bc7ba5b5d25cea881db22fb1a5bc2bc5fbc3e4 |
|
From: David Goodger <goodger@py...> - 2015-01-27 15:30:10
|
I'm afraid there's not enough information there to help you much. The setup is using Sphinx, which uses Docutils, which uses Pygments. It doesn't seem to be a Docutils issue. Pygments raises an exception: "ClassNotFound: no lexer matching the text found". Unfortunately it doesn't tell you *what* text was found, or where. Pygments does code formatting/styling. I suspect that you're missing a formatter/styler for the specific language that Pygments is trying to process. In other words, you may be missing a piece of software (maybe a Pygments plugin) that is required. The output doesn't tell you what file it was processing when the error occurred. That would be useful information. I'm not willing to download all the bits & pieces to try to guess what's missing. Perhaps someone on the BRO or Pygments development teams can help you out. -- David Goodger On Tue, Jan 27, 2015 at 7:07 AM, Andrew V. Stepanov <stanv@...> wrote: > Hello. > > I need to make RPM package for BRO. > > https://www.bro.org/ > > I need to run in SPEC file: make doc > > But it fails with: > > Running Sphinx v1.3a0 > loading pickled environment... not yet created > building [html]: targets for 422 source files that are out of date > updating environment: 422 added, 0 changed, 0 removed > reading sources... [ 0%] broids/index > running test doc/sphinx/ftp-bruteforce.btest ... > reading sources... [ 0%] cluster/index > reading sources... [ 0%] components/binpac/README > > Exception occurred: > File "/usr/lib/python2.7/site-packages/pygments/lexers/__init__.py", > line 252, in guess_lexer > raise ClassNotFound('no lexer matching the text found') > ClassNotFound: no lexer matching the text found > The full traceback has been saved in /usr/src/tmp/sphinx-err-5Cm0Xi.log, > if you want to report the issue to the developers. > > > Contents of /usr/src/tmp/sphinx-err-5Cm0Xi.log is: > > > # Sphinx version: 1.3a0 > # Python version: 2.7.8 > # Docutils version: 0.13 repository > # Jinja2 version: 2.8-dev > # Loaded extensions: > # rst_directive from > /usr/src/RPM/BUILD/bro-2.3.1/build/doc/sphinx_input/ext/rst_directive.py > # bro from /usr/src/RPM/BUILD/bro-2.3.1/build/doc/sphinx_input/ext/bro.py > # adapt-toc from > /usr/src/RPM/BUILD/bro-2.3.1/build/doc/sphinx_input/ext/adapt-toc.py > # sphinx.ext.todo from > /usr/lib/python2.7/site-packages/sphinx/ext/todo.pyc > # broxygen from > /usr/src/RPM/BUILD/bro-2.3.1/build/doc/sphinx_input/ext/broxygen.py > # btest-sphinx from > /usr/src/RPM/BUILD/bro-2.3.1/aux/btest/sphinx/btest-sphinx.pyc > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/sphinx/cmdline.py", line 254, > in main > app.build(force_all, filenames) > File "/usr/lib/python2.7/site-packages/sphinx/application.py", line > 215, in build > self.builder.build_update() > File "/usr/lib/python2.7/site-packages/sphinx/builders/__init__.py", > line 214, in build_update > 'out of date' % len(to_build)) > File "/usr/lib/python2.7/site-packages/sphinx/builders/__init__.py", > line 234, in build > purple, length): > File "/usr/lib/python2.7/site-packages/sphinx/builders/__init__.py", > line 134, in status_iterator > for item in iterable: > File "/usr/lib/python2.7/site-packages/sphinx/environment.py", line > 474, in update_generator > self.read_doc(docname, app=app) > File "/usr/lib/python2.7/site-packages/sphinx/environment.py", line > 621, in read_doc > pub.publish() > File "/usr/lib/python2.7/site-packages/docutils/core.py", line 217, > in publish > self.settings) > File "/usr/lib/python2.7/site-packages/docutils/readers/__init__.py", > line 72, in read > self.parse() > File "/usr/lib/python2.7/site-packages/docutils/readers/__init__.py", > line 78, in parse > self.parser.parse(self.input, document) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/__init__.py", > line 172, in parse > self.statemachine.run(inputlines, document, inliner=self.inliner) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 170, in run > input_source=document['source']) > File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", > line 239, in run > context, state, transitions) > File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", > line 460, in check_line > return method(match, context, next_state) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 2961, in text > self.section(title.lstrip(), source, style, lineno + 1, messages) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 327, in section > self.new_subsection(title, lineno, messages) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 395, in new_subsection > node=section_node, match_titles=True) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 282, in nested_parse > node=node, match_titles=match_titles) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 195, in run > results = StateMachineWS.run(self, input_lines, input_offset) > File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", > line 239, in run > context, state, transitions) > File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", > line 460, in check_line > return method(match, context, next_state) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 2726, in underline > self.section(title, source, style, lineno - 1, messages) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 327, in section > self.new_subsection(title, lineno, messages) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 395, in new_subsection > node=section_node, match_titles=True) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 282, in nested_parse > node=node, match_titles=match_titles) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 195, in run > results = StateMachineWS.run(self, input_lines, input_offset) > File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", > line 239, in run > context, state, transitions) > File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", > line 460, in check_line > return method(match, context, next_state) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 2726, in underline > self.section(title, source, style, lineno - 1, messages) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 327, in section > self.new_subsection(title, lineno, messages) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 395, in new_subsection > node=section_node, match_titles=True) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 282, in nested_parse > node=node, match_titles=match_titles) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 195, in run > results = StateMachineWS.run(self, input_lines, input_offset) > File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", > line 239, in run > context, state, transitions) > File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", > line 460, in check_line > return method(match, context, next_state) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 2726, in underline > self.section(title, source, style, lineno - 1, messages) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 327, in section > self.new_subsection(title, lineno, messages) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 395, in new_subsection > node=section_node, match_titles=True) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 282, in nested_parse > node=node, match_titles=match_titles) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 195, in run > results = StateMachineWS.run(self, input_lines, input_offset) > File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", > line 239, in run > context, state, transitions) > File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", > line 460, in check_line > return method(match, context, next_state) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 2299, in explicit_markup > nodelist, blank_finish = self.explicit_construct(match) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 2311, in explicit_construct > return method(self, expmatch) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 2054, in directive > directive_class, match, type_name, option_presets) > File > "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line > 2103, in run_directive > result = directive_instance.run() > File > "/usr/src/RPM/BUILD/bro-2.3.1/build/doc/sphinx_input/ext/rst_directive.py", > line 138, in run > lexer = guess_lexer(content) > File "/usr/lib/python2.7/site-packages/pygments/lexers/__init__.py", > line 252, in guess_lexer > raise ClassNotFound('no lexer matching the text found') > ClassNotFound: no lexer matching the text found > > $ rpm -q python-module-docutils > python-module-docutils-0.13-alt1.svn20140708 > > > https://github.com/bro/bro/tree/master/doc/components/binpac > https://github.com/bro/binpac/blob/master/README > > Could you please help me ? > > > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming. The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Docutils-users mailing list > Docutils-users@... > https://lists.sourceforge.net/lists/listinfo/docutils-users > > Please use "Reply All" to reply to the list. -- David Goodger <http://python.net/~goodger>; |
|
From: Alan G Isaac <alan.isaac@gm...> - 2015-01-27 14:54:21
|
I ran into this bug again today: http://sourceforge.net/p/docutils/bugs/209/ Is there any hope that it will eventually be addressed? Thanks, Alan Isaac |
|
From: Andrew V. Stepanov <stanv@al...> - 2015-01-27 13:07:15
|
Hello. I need to make RPM package for BRO. https://www.bro.org/ I need to run in SPEC file: make doc But it fails with: Running Sphinx v1.3a0 loading pickled environment... not yet created building [html]: targets for 422 source files that are out of date updating environment: 422 added, 0 changed, 0 removed reading sources... [ 0%] broids/index running test doc/sphinx/ftp-bruteforce.btest ... reading sources... [ 0%] cluster/index reading sources... [ 0%] components/binpac/README Exception occurred: File "/usr/lib/python2.7/site-packages/pygments/lexers/__init__.py", line 252, in guess_lexer raise ClassNotFound('no lexer matching the text found') ClassNotFound: no lexer matching the text found The full traceback has been saved in /usr/src/tmp/sphinx-err-5Cm0Xi.log, if you want to report the issue to the developers. Contents of /usr/src/tmp/sphinx-err-5Cm0Xi.log is: # Sphinx version: 1.3a0 # Python version: 2.7.8 # Docutils version: 0.13 repository # Jinja2 version: 2.8-dev # Loaded extensions: # rst_directive from /usr/src/RPM/BUILD/bro-2.3.1/build/doc/sphinx_input/ext/rst_directive.py # bro from /usr/src/RPM/BUILD/bro-2.3.1/build/doc/sphinx_input/ext/bro.py # adapt-toc from /usr/src/RPM/BUILD/bro-2.3.1/build/doc/sphinx_input/ext/adapt-toc.py # sphinx.ext.todo from /usr/lib/python2.7/site-packages/sphinx/ext/todo.pyc # broxygen from /usr/src/RPM/BUILD/bro-2.3.1/build/doc/sphinx_input/ext/broxygen.py # btest-sphinx from /usr/src/RPM/BUILD/bro-2.3.1/aux/btest/sphinx/btest-sphinx.pyc Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/sphinx/cmdline.py", line 254, in main app.build(force_all, filenames) File "/usr/lib/python2.7/site-packages/sphinx/application.py", line 215, in build self.builder.build_update() File "/usr/lib/python2.7/site-packages/sphinx/builders/__init__.py", line 214, in build_update 'out of date' % len(to_build)) File "/usr/lib/python2.7/site-packages/sphinx/builders/__init__.py", line 234, in build purple, length): File "/usr/lib/python2.7/site-packages/sphinx/builders/__init__.py", line 134, in status_iterator for item in iterable: File "/usr/lib/python2.7/site-packages/sphinx/environment.py", line 474, in update_generator self.read_doc(docname, app=app) File "/usr/lib/python2.7/site-packages/sphinx/environment.py", line 621, in read_doc pub.publish() File "/usr/lib/python2.7/site-packages/docutils/core.py", line 217, in publish self.settings) File "/usr/lib/python2.7/site-packages/docutils/readers/__init__.py", line 72, in read self.parse() File "/usr/lib/python2.7/site-packages/docutils/readers/__init__.py", line 78, in parse self.parser.parse(self.input, document) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/__init__.py", line 172, in parse self.statemachine.run(inputlines, document, inliner=self.inliner) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 170, in run input_source=document['source']) File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run context, state, transitions) File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line return method(match, context, next_state) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2961, in text self.section(title.lstrip(), source, style, lineno + 1, messages) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 327, in section self.new_subsection(title, lineno, messages) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 395, in new_subsection node=section_node, match_titles=True) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 282, in nested_parse node=node, match_titles=match_titles) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 195, in run results = StateMachineWS.run(self, input_lines, input_offset) File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run context, state, transitions) File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line return method(match, context, next_state) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2726, in underline self.section(title, source, style, lineno - 1, messages) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 327, in section self.new_subsection(title, lineno, messages) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 395, in new_subsection node=section_node, match_titles=True) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 282, in nested_parse node=node, match_titles=match_titles) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 195, in run results = StateMachineWS.run(self, input_lines, input_offset) File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run context, state, transitions) File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line return method(match, context, next_state) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2726, in underline self.section(title, source, style, lineno - 1, messages) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 327, in section self.new_subsection(title, lineno, messages) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 395, in new_subsection node=section_node, match_titles=True) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 282, in nested_parse node=node, match_titles=match_titles) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 195, in run results = StateMachineWS.run(self, input_lines, input_offset) File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run context, state, transitions) File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line return method(match, context, next_state) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2726, in underline self.section(title, source, style, lineno - 1, messages) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 327, in section self.new_subsection(title, lineno, messages) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 395, in new_subsection node=section_node, match_titles=True) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 282, in nested_parse node=node, match_titles=match_titles) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 195, in run results = StateMachineWS.run(self, input_lines, input_offset) File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", line 239, in run context, state, transitions) File "/usr/lib/python2.7/site-packages/docutils/statemachine.py", line 460, in check_line return method(match, context, next_state) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2299, in explicit_markup nodelist, blank_finish = self.explicit_construct(match) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2311, in explicit_construct return method(self, expmatch) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2054, in directive directive_class, match, type_name, option_presets) File "/usr/lib/python2.7/site-packages/docutils/parsers/rst/states.py", line 2103, in run_directive result = directive_instance.run() File "/usr/src/RPM/BUILD/bro-2.3.1/build/doc/sphinx_input/ext/rst_directive.py", line 138, in run lexer = guess_lexer(content) File "/usr/lib/python2.7/site-packages/pygments/lexers/__init__.py", line 252, in guess_lexer raise ClassNotFound('no lexer matching the text found') ClassNotFound: no lexer matching the text found $ rpm -q python-module-docutils python-module-docutils-0.13-alt1.svn20140708 https://github.com/bro/bro/tree/master/doc/components/binpac https://github.com/bro/binpac/blob/master/README Could you please help me ? |
|
From: Ben Finney <ben+<python@be...> - 2015-01-08 06:38:18
|
David Goodger <goodger@...> writes: > On Wed, Jan 7, 2015 at 8:39 PM, Ben Finney <ben+python@...> wrote: > > What I'd like is for any code using this custom Writer, to get that > > behaviour by default (i.e. not need to even know about the > > ‘doctitle_xform’ option). Can the Writer take care of that option in > > such a way that the client code doesn't need to know about it? > > Yes, it can (just monkey-patch the settings object), but it shouldn't. Fair enough. I can understand it makes the API clearer. > Don't you have a front-end app? It should do the configuration. Well, the extra levels of indirection complicate my unit tests. But not hugely, and the result is still good. Thanks for the help. -- \ “I turned to speak to God/About the world's despair; But to | `\ make bad matters worse/I found God wasn't there.” —Robert Frost | _o__) | Ben Finney |
|
From: David Goodger <goodger@py...> - 2015-01-08 03:26:33
|
On Wed, Jan 7, 2015 at 8:39 PM, Ben Finney <ben+python@...> wrote: > David Goodger <goodger@...> writes: > >> On Wed, Jan 7, 2015 at 7:52 PM, Ben Finney <ben+python@...> wrote: >> > Okay, that is a setting on the Publisher (and, according to the >> > docs, normally set by configuration file or command-line). >> > >> > For the task at hand (if it matters, I am transforming a changelog >> > document to structured release data), I want all the settings to be >> > internally managed. […] >> > >> > In order to modify that setting (‘doctitle_xform’), do I need to make a >> > custom Publisher class too? Or can I have the Writer somehow override >> > it? >> >> Just pass the configuration setting to the standard Publisher or >> convenience function: >> http://docutils.sourceforge.net/docs/api/publisher.html#configuration > > What I'd like is for any code using this custom Writer, to get that > behaviour by default (i.e. not need to even know about the > ‘doctitle_xform’ option). Can the Writer take care of that option in > such a way that the client code doesn't need to know about it? Yes, it can (just monkey-patch the settings object), but it shouldn't. Don't you have a front-end app? It should do the configuration. -- David Goodger <http://python.net/~goodger>; |
|
From: Ben Finney <ben+<python@be...> - 2015-01-08 02:40:01
|
David Goodger <goodger@...> writes: > On Wed, Jan 7, 2015 at 7:52 PM, Ben Finney <ben+python@...> wrote: > > Okay, that is a setting on the Publisher (and, according to the > > docs, normally set by configuration file or command-line). > > > > For the task at hand (if it matters, I am transforming a changelog > > document to structured release data), I want all the settings to be > > internally managed. […] > > > > In order to modify that setting (‘doctitle_xform’), do I need to make a > > custom Publisher class too? Or can I have the Writer somehow override > > it? > > Just pass the configuration setting to the standard Publisher or > convenience function: > http://docutils.sourceforge.net/docs/api/publisher.html#configuration What I'd like is for any code using this custom Writer, to get that behaviour by default (i.e. not need to even know about the ‘doctitle_xform’ option). Can the Writer take care of that option in such a way that the client code doesn't need to know about it? -- \ “Shepherds … look after their sheep so they can, first, fleece | `\ them and second, turn them into meat. That's much more like the | _o__) priesthood as I know it.” —Christopher Hitchens, 2008-10-29 | Ben Finney |
|
From: David Goodger <goodger@py...> - 2015-01-08 02:29:35
|
On Wed, Jan 7, 2015 at 7:52 PM, Ben Finney <ben+python@...> wrote: > David Goodger <goodger@...> writes: > >> On Tue, Jan 6, 2015 at 11:20 PM, Ben Finney <ben+python@...> wrote: >> > What I want is: >> > >> > ===== >> > $ rst2pseudoxml < foo.txt >> > <document source="<stdin>"> >> > <section ids="first-section" names="first\ section"> >> > <title> >> > First Section >> > <paragraph> >> > Lorem ipsum, dolor sit amet. >> > ===== >> > >> > In fact, I'm accessing this document programmatically using a custom >> > Writer. How can I get the parsing result I want? >> >> http://docutils.sourceforge.net/docs/user/config.html#doctitle-xform > > Thanks. Okay, that is a setting on the Publisher (and, according to the > docs, normally set by configuration file or command-line). > > For the task at hand (if it matters, I am transforming a changelog > document to structured release data), I want all the settings to be > internally managed. > > So far I've only needed to make a custom Writer class and a custom > Translator class. Unit tests for those are already cumbersome; I would > really prefer not to need creating yet another custom class. > > In order to modify that setting (‘doctitle_xform’), do I need to make a > custom Publisher class too? Or can I have the Writer somehow override > it? Just pass the configuration setting to the standard Publisher or convenience function: http://docutils.sourceforge.net/docs/api/publisher.html#configuration -- David Goodger <http://python.net/~goodger>; |
|
From: Ben Finney <ben+<python@be...> - 2015-01-08 01:55:47
|
David Goodger <goodger@...> writes: > On Tue, Jan 6, 2015 at 11:20 PM, Ben Finney <ben+python@...> wrote: > > What I want is: > > > > ===== > > $ rst2pseudoxml < foo.txt > > <document source="<stdin>"> > > <section ids="first-section" names="first\ section"> > > <title> > > First Section > > <paragraph> > > Lorem ipsum, dolor sit amet. > > ===== > > > > In fact, I'm accessing this document programmatically using a custom > > Writer. How can I get the parsing result I want? > > http://docutils.sourceforge.net/docs/user/config.html#doctitle-xform Thanks. Okay, that is a setting on the Publisher (and, according to the docs, normally set by configuration file or command-line). For the task at hand (if it matters, I am transforming a changelog document to structured release data), I want all the settings to be internally managed. So far I've only needed to make a custom Writer class and a custom Translator class. Unit tests for those are already cumbersome; I would really prefer not to need creating yet another custom class. In order to modify that setting (‘doctitle_xform’), do I need to make a custom Publisher class too? Or can I have the Writer somehow override it? -- \ “Never express yourself more clearly than you are able to | `\ think.” —Niels Bohr | _o__) | Ben Finney |
|
From: David Goodger <goodger@py...> - 2015-01-07 15:44:11
|
On Tue, Jan 6, 2015 at 11:20 PM, Ben Finney <ben+python@...> wrote: > Ben Finney <ben+python@...> writes: > >> But if the document has only one top-level section > > Sorry, I gave the wrong example. Here is an example that shows the > behaviour: > >> the special case applies and I don't get the sections as I want: >> >> ===== >> $ cat foo.txt >> First Section >> ============= >> >> Lorem ipsum, dolor sit amet. >> >> $ rst2pseudoxml < foo.txt >> <document ids="first-section" names="first\ section" source="<stdin>" title="First Section"> >> <title> >> First Section >> <paragraph> >> Lorem ipsum, dolor sit amet. >> ===== > > What I want is: > > ===== > $ rst2pseudoxml < foo.txt > <document source="<stdin>"> > <section ids="first-section" names="first\ section"> > <title> > First Section > <paragraph> > Lorem ipsum, dolor sit amet. > ===== > > In fact, I'm accessing this document programmatically using a custom > Writer. How can I get the parsing result I want? http://docutils.sourceforge.net/docs/user/config.html#doctitle-xform -- David Goodger <http://python.net/~goodger>; |
|
From: Ben Finney <ben+<python@be...> - 2015-01-07 05:21:48
|
Ben Finney <ben+python@...> writes:
> But if the document has only one top-level section
Sorry, I gave the wrong example. Here is an example that shows the
behaviour:
> the special case applies and I don't get the sections as I want:
>
> =====
> $ cat foo.txt
> First Section
> =============
>
> Lorem ipsum, dolor sit amet.
>
> $ rst2pseudoxml < foo.txt
> <document ids="first-section" names="first\ section" source="<stdin>" title="First Section">
> <title>
> First Section
> <paragraph>
> Lorem ipsum, dolor sit amet.
> =====
What I want is:
=====
$ rst2pseudoxml < foo.txt
<document source="<stdin>">
<section ids="first-section" names="first\ section">
<title>
First Section
<paragraph>
Lorem ipsum, dolor sit amet.
=====
In fact, I'm accessing this document programmatically using a custom
Writer. How can I get the parsing result I want?
--
\ “… a Microsoft Certified System Engineer is to information |
`\ technology as a McDonalds Certified Food Specialist is to the |
_o__) culinary arts.” —Michael Bacarella |
Ben Finney
|
|
From: Ben Finney <ben+<python@be...> - 2015-01-07 04:54:18
|
Howdy all,
How can I disable the special-case treatment of a lone section title as
the document title?
The default reST parser treats a lone section title as a special case,
promoting it as the document title. What I want is to disable that
behaviour, and have the first section treated as a section regardless of
whether any sections follow it.
A document with two top-level sections is parsed as I want:
=====
$ cat foo.txt
First Section
=============
Lorem ipsum, dolor sit amet.
Second Section
==============
Praesent eleifend ligula eget luctus consectetur.
$ rst2pseudoxml < foo.txt
<document source="<stdin>">
<section ids="first-section" names="first\ section">
<title>
First Section
<paragraph>
Lorem ipsum, dolor sit amet.
<section ids="second-section" names="second\ section">
<title>
Second Section
<paragraph>
Praesent eleifend ligula eget luctus consectetur.
=====
But if the document has only one top-level section, the special case
applies and I don't get the sections as I want:
=====
$ cat foo.txt
First Section
=============
Lorem ipsum, dolor sit amet.
Second Section
==============
Praesent eleifend ligula eget luctus consectetur.
$ rst2pseudoxml < foo.txt
<document ids="first-section" names="first\ section" source="<stdin>" title="First Section">
<title>
First Section
<paragraph>
Lorem ipsum, dolor sit amet.
=====
What I want is:
=====
$ rst2pseudoxml < foo.txt
<document source="<stdin>">
<section ids="first-section" names="first\ section">
<title>
First Section
<paragraph>
Lorem ipsum, dolor sit amet.
=====
In fact, I'm accessing this document programmatically using a custom
Writer. How can I get the parsing result I want?
--
\ “A politician is an animal which can sit on a fence and yet |
`\ keep both ears to the ground.” —Henry L. Mencken |
_o__) |
Ben Finney
|
|
From: Eric Knibbe <eric3knibbe@gm...> - 2015-01-04 22:55:16
|
Virgil Arrington <cuyfalls <at> hotmail.com> writes: > I've read online about people writing whole books in ReStructuredText. > So, my question is, what editor are y'all using to get the job done? For anyone on Mac OS X, I wrote a reST language module for BBEdit or TextWrangler. I wrote it to make editing this book <http://lassoguide.com>; much easier. Find it here: <http://ericfromcanada.bitbucket.org>; --- Eric3 |
|
From: Guenter Milde <milde@us...> - 2014-12-22 16:10:52
|
On 2014-12-17, Marc Abramowitz wrote: > [-- Type: text/plain, Encoding: --] > Has anyone suggested moving from Subversion to Git or Mercurial? Many have, see the list archive. > Most Python projects use one of those two and usually either GitHub or > Bitbucket, because it makes collaboration a lot easier. Collaboration is not the problem. It is a matter of familiarisation - the current Docutils developers are more familiar with SVN. OTOH, I support a move to Git because setting up brances is a pain with SVN. However, I don't think there is need to change the host, as Sourceforge supports the "modern" vcs. (If we do not want to exclude possible developers from Cuba, we should move to a non-US host, though.) Günter |
|
From: David Goodger <goodger@py...> - 2014-12-17 19:53:33
|
Sorry Nancy, I have no idea why you're having this problem. There is no "admindocscorsheaders" module in Docutils, or anything like that. The Django docs you referenced do have "admindocs" in the URL. I suspect you may have a typo somewhere. Try searching for "admindocs" in your files. Perhaps the Django people can help more. Good luck! David Goodger On Tue, Dec 16, 2014 at 10:53 AM, Poekert Family <poekert@...> wrote: > I never used docutils before. I followed the instructions to use it in the > Django docs at > https://docs.djangoproject.com/en/1.7/ref/contrib/admin/admindocs/ > > When I run manage.py runserver, I get the error: "ImportError: No module > named admindocscorsheaders" > > First I installed docutils with pip and I got the above error. Then I > installed it from the tarball and uninstalled the pip version. I am still > getting the error. > > I ran the alltests.py from the test directory and there were no errors. > > I am running on a MacBook Pro with Mavericks, Python 2.7, and Django 1.7. > > Any help on this will be appreciated. > > Regards, > > Nancy > |
|
From: David Goodger <goodger@py...> - 2014-12-17 19:49:33
|
On Wed, Dec 17, 2014 at 12:22 PM, engelbert gruber <engelbert.gruber@...> wrote: > On 16 December 2014 at 17:53, Poekert Family <poekert@...> wrote: >> I never used docutils before. I followed the instructions to use it in the >> Django docs at >> https://docs.djangoproject.com/en/1.7/ref/contrib/admin/admindocs/ >> >> When I run manage.py runserver, I get the error: "ImportError: No module >> named admindocscorsheaders" > > there is no refernce on manpage.py on that page , where did you get > this commandline from > > my understanding is: django preprocesses reST documents and produces > html by means of docutils > > and i would assume one queries django via http not n commandline > > manpage.py produces man pages that is manual pages for unix systems > you are on a mac ... open a terminal type "man man<enter>" > > or am i totally misled Engelbert, you're mistaken. It's "manage.py", not "manpage.py". IIRC, "manage.py" is Django's way of starting up applications and services. -- David Goodger <http://python.net/~goodger>; |
|
From: engelbert gruber <engelbert.gruber@gm...> - 2014-12-17 18:22:13
|
On 16 December 2014 at 17:53, Poekert Family <poekert@...> wrote: > I never used docutils before. I followed the instructions to use it in the > Django docs at > https://docs.djangoproject.com/en/1.7/ref/contrib/admin/admindocs/ > > When I run manage.py runserver, I get the error: "ImportError: No module > named admindocscorsheaders" there is no refernce on manpage.py on that page , where did you get this commandline from my understanding is: django preprocesses reST documents and produces html by means of docutils and i would assume one queries django via http not n commandline manpage.py produces man pages that is manual pages for unix systems you are on a mac ... open a terminal type "man man<enter>" or am i totally misled |
|
From: David Goodger <goodger@py...> - 2014-12-17 15:48:29
|
On Wed, Dec 17, 2014 at 5:27 AM, Ben Finney <ben+python@...> wrote: > Marc Abramowitz <msabramo@...> writes: > >> Any interest in using tox to test docutils on multiple Python >> versions? > > That is less a topic for discussion here (the forum for Docutils > end-users), and more a topic for discussion at ‘docutils-develop’ which > is for Docutils developers. +1 -- David Goodger <http://python.net/~goodger>; |
|
From: David Goodger <goodger@py...> - 2014-12-17 15:47:35
|
On Wed, Dec 17, 2014 at 12:52 AM, Marc Abramowitz <msabramo@...> wrote: > Has anyone suggested moving from Subversion to Git or Mercurial? > > Most Python projects use one of those two and usually either GitHub or > Bitbucket, because it makes collaboration a lot easier. > > Has it come up before? Many times; see the mailing list archives for this list and Docutils-develop. I'm not averse to switching, it just has to be done properly and completely with minimal perturbation. Mercurial is my preference, because it's written and extensible in Python, and because I find Git slightly harder to use (although much better than it used to be). Docutils pre-dates widespread DVCS use. Once you're set up and used to SVN, the cost of switching outweighs the benefits, at least in the short term. And I don't drink the "switch to Github and prepare for a deluge of pull requests" koolaid. -- David Goodger <http://python.net/~goodger>; |
|
From: Ben Finney <ben+<python@be...> - 2014-12-17 11:28:37
|
Marc Abramowitz <msabramo@...> writes: > Any interest in using tox to test docutils on multiple Python > versions? That is less a topic for discussion here (the forum for Docutils end-users), and more a topic for discussion at ‘docutils-develop’ which is for Docutils developers. -- \ “When I was a kid I used to pray every night for a new bicycle. | `\ Then I realised that the Lord doesn't work that way so I stole | _o__) one and asked Him to forgive me.” —Emo Philips | Ben Finney |
|
From: Marc Abramowitz <msabramo@gm...> - 2014-12-17 07:21:32
|
Any interest in using tox to test docutils on multiple Python versions? https://github.com/msabramo/docutils/pull/2 Looks like this: [marca@... docutils]$ tox ... py26: commands succeeded py27: commands succeeded py33: commands succeeded py34: commands succeeded congratulations :) Marc |
|
From: Marc Abramowitz <msabramo@gm...> - 2014-12-17 06:53:06
|
Has anyone suggested moving from Subversion to Git or Mercurial? Most Python projects use one of those two and usually either GitHub or Bitbucket, because it makes collaboration a lot easier. Has it come up before? Marc |
|
From: Marc Abramowitz <msabramo@gm...> - 2014-12-16 22:28:45
|
> You're right, my apologies. I forgot to look there for aliases, and > forgot that "code-block" is standard. Please ignore that part. No problem. Thanks for confirming. > It would have to be *really* specific. E.g., Docutils would have to > check that it was called by distutils only. OK, I updated the patch at https://sourceforge.net/p/docutils/bugs/270/ to do this. > Maybe somebody else can investigate. I don't have much time for > Docutils these days. Sure. Is there someone you might suggest? I thought perhaps Günter Milde (cc'd), since he seems to have touched that file a lot. Marc On Tue, Dec 16, 2014 at 8:34 AM, David Goodger <goodger@...> wrote: > > [CC'ing to Docutils-users. Please "reply-all", not just to me.] > > On Tue, Dec 16, 2014 at 10:12 AM, Marc Abramowitz <msabramo@...> > wrote: > > First off, thanks David, for taking the time to respond! > > > >> "code-block" is not a standard Docutils reST directive > > > > Apologies. I'm not too familiar with docutils proper so I may have > confused > > docutils with Sphinx. But does the following not mean that "code-block" > is > > an alias for "code"? > > > > * > > > https://sourceforge.net/p/docutils/code/HEAD/tree/trunk/docutils/docutils/parsers/rst/languages/en.py > > You're right, my apologies. I forgot to look there for aliases, and > forgot that "code-block" is standard. Please ignore that part. > > >> It makes assumptions that may not always be true > > > > Yeah, this is my first time touching docutils so I am not surprised. I'm > > willing to work on it though. Do you think that if you were specific > about > > what those assumptions are that the patch could be made to be acceptable? > > It would have to be *really* specific. E.g., Docutils would have to > check that it was called by distutils only. > > The problem in your patch is, you're introducing a dependency on the > stock RST parser, and client code might be using an alternate parser > (modified, or different) or none. I don't want to screw 3rd-party code > that uses Docutils, just to fix Python's bug. This smells kludgey. > > I don't understand why the issue is happening. Maybe it is a Docutils > bug, I don't know. > > > Or > > is there nothing that can be done on the docutils side, because... > > > >> If the bug is in Python's distutils, that's where the fix should be > > > > Yes, I agree in principle and I mentioned in the sourceforge ticket that > > this might be more of a distutils problem. The thing is that even if we > > correct the problem in distutils (which I think is present at least as > far > > back as Python 2.7 and as recent as Python 3.4), it won't be available to > > users until Python 3.5 is released and it will only be available to > Python 3 > > users; Python 2 folks will be out of luck. So while I agree that fixing > the > > problem in distutils might be the more correct approach, I'm also > thinking > > about "practicality beats purity". > > > > That said, I did submit a patch to CPython at > > http://bugs.python.org/issue23063 and I'll try to push that through, but > > like I said, it will only be for Python 3.5 I think. Whereas if we can do > > something in docutils, then folks can easily upgrade docutils and be > able to > > validate more of their RST documents. > > Maybe somebody else can investigate. I don't have much time for > Docutils these days. > > David Goodger > > > > > On Tue, Dec 16, 2014 at 7:13 AM, David Goodger <goodger@...> > wrote: > >> > >> On Mon, Dec 15, 2014 at 2:46 PM, Marc Abramowitz <msabramo@...> > >> wrote: > >> > python setup.py check --restructuredtext --strict --metadata fails > with: > >> > > >> > warning: check: Could not finish the parsing. > >> > > >> > if the RST document uses code or code-block directives. > >> > > >> > This is annoying because the document is valid, but it appears to be > >> > invalid > >> > and confuses people. > >> > > >> > I filed a ticket for this (with a patch included): > >> > > >> > https://sourceforge.net/p/docutils/bugs/270/ > >> > >> "code-block" is not a standard Docutils reST directive, so I don't see > >> how the document could be valid. "code-block" should always break. > >> Maybe it's a Sphinx extension, and your environment has that > >> installed. Did you try with just the "code" directive? > >> > >> -1 on the patch. It makes assumptions that may not always be true. If > >> the bug is in Python's distutils, that's where the fix should be. But > >> first, make sure your document is truly valid. > >> > >> -- > >> David Goodger <http://python.net/~goodger>; > |
|
From: Marcelo Huerta <marcelo.huerta@gm...> - 2014-12-16 17:23:22
|
El 16/12/2014 a las 01:34 p.m., David Goodger escibió: > I don't have much time for > Docutils these days. Not to be an alarmist or anything, but should we be worried about Docutils' future, given this? -- o-=< Marcelo >=-o |
|
From: Poekert Family <poekert@ve...> - 2014-12-16 16:53:40
|
I never used docutils before. I followed the instructions to use it in the Django docs at https://docs.djangoproject.com/en/1.7/ref/contrib/admin/admindocs/ When I run manage.py runserver, I get the error: "ImportError: No module named admindocscorsheaders" First I installed docutils with pip and I got the above error. Then I installed it from the tarball and uninstalled the pip version. I am still getting the error. I ran the alltests.py from the test directory and there were no errors. I am running on a MacBook Pro with Mavericks, Python 2.7, and Django 1.7. Any help on this will be appreciated. Regards, Nancy |