From: Paul M. <p.f...@gm...> - 2008-05-30 15:06:52
|
The last release of docutils was 0.4, in 2006 (according to the website). Also according to the website, it is recommended to use the latest snapshot as "The snapshots usually contain more features and fewer bugs than the "official" releases". Is this text out of date? This would be quite possible, as there seems to have been no significant checkins to the core docutils code (as opposed to the sandbox, documentation, and minor text string fixes) for at least 18 months. If so, it should be removed and 0.4 "blessed" as the stable release. Otherwise, could we have a new release please? At the moment, the docutils project feels moribund, based on the website. This is frustrating, given its recent high visibility in things like the Python core documentation, and the sphinx tool. My personal feeling is that docutils is stable enough and useful enough in its current form to justify being promoted to a 1.0 release, and possibly even submitted for inclusion into the Python core. Paul. |
From: Martin G. <mg...@la...> - 2009-08-30 23:08:39
|
Hi everybody, Now that the rst2man script has entered the trunk, I hope you will consider making a release with it. It is important for Mercurial package managers that they can rely on a released version. Debian carries a snapshow of rst2man -- thanks Ben Finney! -- but I don't think other distributions have it yet. When this came up six weeks ago David Goodger pointed to two show-stopper bugs: http://thread.gmane.org/gmane.text.docutils.devel/4732/focus=4734 I've just submitted a patch for the trivial one: https://sourceforge.net/tracker/?func=detail&aid=2847448&group_id=38414&atid=422032 Please take a look at it and at the other patch I just posted: https://sourceforge.net/tracker/?func=detail&aid=2847446&group_id=38414&atid=422032 After applying it, I get no errors when I run the test suite using Python 2.5 on Debian unstable. I don't have access to Python 2.3 in order to investigate the other bug mentioned by David -- I hope there is someone else has Python 2.3 available? -- Martin Geisler VIFF (Virtual Ideal Functionality Framework) brings easy and efficient SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/. |
From: <gr...@us...> - 2009-09-04 17:48:01
|
hello, if nothing happens (currently a lot happens in my life) i will make a release 0.6 next week around thursday any objections ? cheers -- |
From: Leandro L. <ll...@gm...> - 2009-09-04 19:05:34
|
gr...@us..., el 4 de septiembre a las 19:48 me escribiste: > hello, > > if nothing happens (currently a lot happens in my life) i will make a > release 0.6 next week around thursday > > any objections ? Can you include this patch, please? http://sourceforge.net/tracker/?func=detail&aid=2823466&group_id=38414&atid=422032 It has all you asked for, AFAIK. If it needs more work please let me know. Thanks. -- Leandro Lucarella (luca) | Blog colectivo: http://www.mazziblog.com.ar/blog/ ---------------------------------------------------------------------------- GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145 104C 949E BFB6 5F5A 8D05) ---------------------------------------------------------------------------- De tan fina la condesa, por no cagarse, reza. -- Ricardo Vaporeso |
From: Alan G I. <ai...@am...> - 2009-09-04 18:06:49
|
On 9/4/2009 1:48 PM, gr...@us... wrote: > if nothing happens (currently a lot happens in my life) i will make a > release 0.6 next week around thursday I notice that neither of the following problems were fixed yet: http://article.gmane.org/gmane.text.docutils.devel/4733 Alan Isaac PS What was the decision on Python 2.3 versus 2.4? http://article.gmane.org/gmane.text.docutils.devel/4736 I like moving to 2.4, although Roberto cogently opposed it. |
From: Guenter M. <mi...@us...> - 2009-09-04 18:53:31
|
On 2009-09-04, Alan G Isaac wrote: > On 9/4/2009 1:48 PM, gr...@us... wrote: >> if nothing happens (currently a lot happens in my life) i will make a >> release 0.6 next week around thursday Please test the LaTeX writer template backwards compatibility module with Python 2.3. > I notice that neither of the following problems were fixed yet: > http://article.gmane.org/gmane.text.docutils.devel/4733 Sure? At least the second one is fine here. 1. easily eliminated DeprecationWarning Cannot test as I am lacking 2.6 Could you please propose a patch: What should be written instead the deprecated construct? 2. IOError does not report filename Running:: .. include:: doesnotexist.rst results in /home/milde/Texte/Test/Docutils/include-nonexisting-file.txt:: (SEVERE/4) Problems with "include" directive path: IOError: [Errno 2] Datei oder Verzeichnis nicht gefunden: u'doesnotexist.rst'. Exiting due to level-4 (SEVERE) system message. > Alan Isaac > PS What was the decision on Python 2.3 versus 2.4? > http://article.gmane.org/gmane.text.docutils.devel/4736 > I like moving to 2.4, although Roberto cogently opposed it. The decision was 2.3. What do you gain from moving this up to 2.4? Günter |
From: Alan G I. <ai...@am...> - 2009-09-04 21:36:15
|
On 9/4/2009 2:52 PM, Guenter Milde wrote: > 2. IOError does not report filename > > Running:: > > .. include:: doesnotexist.rst > > results in > > /home/milde/Texte/Test/Docutils/include-nonexisting-file.txt:: (SEVERE/4) Problems with "include" directive path: > IOError: [Errno 2] Datei oder Verzeichnis nicht gefunden: u'doesnotexist.rst'. > Exiting due to level-4 (SEVERE) system message. Using most recent SVN: G:\>c:\Python26\Scripts\rst2html.py c:\temp\temp.rst c:\temp\temp.htm C:\Python26\lib\site-packages\docutils\parsers\rst\__init__.py:178: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 self.message = message C:\Python26\lib\site-packages\docutils\parsers\rst\states.py:2065: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 directive_error.message) c:\temp\temp.rst:: (SEVERE/4) Problems with "include" directive path: IOError: (2, 'No such file or directory'). Exiting due to level-4 (SEVERE) system message. BUT C:\>c:\Python24\python.exe c:\Python24\Scripts\rst2html.py c:\temp\temp.rst c:\t emp\temp.htm c:\temp\temp.rst:: (SEVERE/4) Problems with "include" directive path: IOError: [Errno 2] No such file or directory: u'c:/temp/doesnotexist.rst'. Exiting due to level-4 (SEVERE) system message. So yes, I'm sure there is a problem under Python 2.6. Alan Isaac |
From: Guenter M. <mi...@us...> - 2009-09-10 14:06:06
|
On 2009-09-04, Alan G Isaac wrote: > On 9/4/2009 2:52 PM, Guenter Milde wrote: >> 2. IOError does not report filename > Using most recent SVN: > G:\>c:\Python26\Scripts\rst2html.py c:\temp\temp.rst c:\temp\temp.htm > C:\Python26\lib\site-packages\docutils\parsers\rst\__init__.py:178: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 > self.message = message > C:\Python26\lib\site-packages\docutils\parsers\rst\states.py:2065: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 > directive_error.message) > c:\temp\temp.rst:: (SEVERE/4) Problems with "include" directive path: > IOError: (2, 'No such file or directory'). > Exiting due to level-4 (SEVERE) system message. > BUT > C:\>c:\Python24\python.exe c:\Python24\Scripts\rst2html.py c:\temp\temp.rst c:\t > emp\temp.htm > c:\temp\temp.rst:: (SEVERE/4) Problems with "include" directive path: > IOError: [Errno 2] No such file or directory: u'c:/temp/doesnotexist.rst'. > Exiting due to level-4 (SEVERE) system message. > So yes, I'm sure there is a problem under Python 2.6. Is this on the same machine, or are this two machines with, maybe, different OS versions. It might have to to with the encoding of the terminal/DOSwindow and the filesystem. I did some changes to the code today, so here (Python 2.5 on Linux) it reports something like: > IOError: [Errno 2] No such file or directory: 'c:/temp/doesnotexist.rst'. (i.e. no "u" in front of the file name). Maybe this change also solved the "mystery"? Günter |
From: Alan G I. <ai...@am...> - 2009-09-10 19:29:55
|
On 9/10/2009 9:34 AM, Guenter Milde wrote: > Is this on the same machine Yes. > I did some changes to the code today Maybe this change also solved the "mystery"? Nope. (I doubt this can be diagnosed without using 2.6.) Alan isaac |
From: <gr...@us...> - 2009-09-11 06:28:14
|
On Thu, 10 Sep 2009, Guenter Milde wrote: > On 2009-09-04, Alan G Isaac wrote: >> On 9/4/2009 2:52 PM, Guenter Milde wrote: >>> 2. IOError does not report filename > >> Using most recent SVN: > >> G:\>c:\Python26\Scripts\rst2html.py c:\temp\temp.rst c:\temp\temp.htm >> C:\Python26\lib\site-packages\docutils\parsers\rst\__init__.py:178: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 >> self.message = message >> C:\Python26\lib\site-packages\docutils\parsers\rst\states.py:2065: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 >> directive_error.message) >> c:\temp\temp.rst:: (SEVERE/4) Problems with "include" directive path: >> IOError: (2, 'No such file or directory'). >> Exiting due to level-4 (SEVERE) system message. > >> BUT > >> C:\>c:\Python24\python.exe c:\Python24\Scripts\rst2html.py c:\temp\temp.rst c:\t >> emp\temp.htm >> c:\temp\temp.rst:: (SEVERE/4) Problems with "include" directive path: >> IOError: [Errno 2] No such file or directory: u'c:/temp/doesnotexist.rst'. >> Exiting due to level-4 (SEVERE) system message. > >> So yes, I'm sure there is a problem under Python 2.6. > > Is this on the same machine, or are this two machines with, maybe, different > OS versions. It might have to to with the encoding of the terminal/DOSwindow > and the filesystem. > > I did some changes to the code today, so here (Python 2.5 on Linux) it > reports something like: > >> IOError: [Errno 2] No such file or directory: 'c:/temp/doesnotexist.rst'. > > (i.e. no "u" in front of the file name). > > Maybe this change also solved the "mystery"? no it does not, same machine same docutils python2.6 and 2.7 dont report the file name. is this now a showstopper for the release ? or the DepreceationWarning ? cheers -- |
From: Guenter M. <mi...@us...> - 2009-09-11 10:25:57
|
On 2009-09-11, gr...@us... wrote: > On Thu, 10 Sep 2009, Guenter Milde wrote: >> On 2009-09-04, Alan G Isaac wrote: >>> On 9/4/2009 2:52 PM, Guenter Milde wrote: >>>> 2. IOError does not report filename ... > is this now a showstopper for the release ? Solved with the latest SVN commit. > or the DepreceationWarning ? Solved too. > cheers Günter |
From: G. M. <mi...@us...> - 2009-09-11 18:45:44
|
On 11.09.09, Alan G Isaac wrote: > So don't leave us in suspense: were you able to solve the mystery? > (I.e., why "%s"%error and "%s"%str(error) were apparently different in > this particular setting?) Its in the source and the commit message: Hack: Since Python 2.6, ``'%s' % error`` returns a unicode object. IOError seems to miss a `__unicode__` method and the fallback `__repr__` does not report the file name. Explicitely converting to str fixes this:: print '%s\n%s\n%s\n' %(error, str(error), repr(error)) Günter |
From: Alan G I. <ai...@am...> - 2009-09-12 02:30:26
|
On 9/11/2009 4:40 PM, Michael Foord wrote: > Interoplating into a Unicode string calls __unicode__ and not __str__. > IOError inherits its __unicode__ method from BaseException and does > indeed miss out the filename... OK, this is odd enough, and is probably the clue, but ... The original bug (?) involved string interpolations, not unicode string interpolation, so it seems to me that a bit of mystery remains. What am I missing? Alan |
From: Georg B. <g.b...@gm...> - 2009-09-12 20:02:07
|
Alan G Isaac schrieb: > On 9/11/2009 4:40 PM, Michael Foord wrote: >> Interoplating into a Unicode string calls __unicode__ and not __str__. >> IOError inherits its __unicode__ method from BaseException and does >> indeed miss out the filename... > > > OK, this is odd enough, and is probably the clue, but ... > The original bug (?) involved string interpolations, > not unicode string interpolation, so it seems to me that > a bit of mystery remains. > > What am I missing? It's probably best explained with a bit of code: >>> class C(object): ... def __str__(self): return '[str]' ... def __unicode__(self): return '[unicode]' ... >>> "%s %s" % ('foo', C()) 'foo [str]' >>> "%s %s" % (u'foo', C()) u'foo [unicode]' >>> I.e., as soon as a Unicode element is interpolated into a string, further interpolations automatically request Unicode via __unicode__, if it exists. I don't think the Python docs specify this one way or the other, but that the exception's __unicode__ is not equivalent to its __str__ is a bug for sure. Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. |
From: Alan G I. <ai...@am...> - 2009-09-11 20:32:52
|
On 9/11/2009 2:45 PM, G. Milde wrote: > Hack: Since Python 2.6, ``'%s' % error`` returns a unicode > object. IOError seems to miss a `__unicode__` method and the > fallback `__repr__` does not report the file name. Explicitely > converting to str fixes this:: > print '%s\n%s\n%s\n' %(error, str(error), repr(error)) Sorry, I'm not understanding that. :: Python 2.6.2 (r262:71605, Apr 14 2009, 22:40:02) [MSC v.1500 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> e = IOError('msg') >>> type("%s"%e) <type 'str'> (Some outcome with unicoded strings.) Thanks, Alan |
From: Michael F. <fuz...@vo...> - 2009-09-11 20:40:24
|
Alan G Isaac wrote: > On 9/11/2009 2:45 PM, G. Milde wrote: > >> Hack: Since Python 2.6, ``'%s' % error`` returns a unicode >> object. IOError seems to miss a `__unicode__` method and the >> fallback `__repr__` does not report the file name. Explicitely >> converting to str fixes this:: >> print '%s\n%s\n%s\n' %(error, str(error), repr(error)) >> > > > Sorry, I'm not understanding that. :: > > Python 2.6.2 (r262:71605, Apr 14 2009, 22:40:02) [MSC v.1500 32 bit (Intel)] on win32 > Type "help", "copyright", "credits" or "license" for more information. > >>> e = IOError('msg') > >>> type("%s"%e) > <type 'str'> > > (Some outcome with unicoded strings.) > > With Python 2.6: >>> try: ... open('flooble') ... except Exception as e: ... pass ... >>> e IOError(2, 'No such file or directory') >>> unicode(e) u"(2, 'No such file or directory')" >>> str(e) "[Errno 2] No such file or directory: 'flooble'" >>> >>> u'%s' % e u"(2, 'No such file or directory')" >>> '%s' % e "[Errno 2] No such file or directory: 'flooble'" Interoplating into a Unicode string calls __unicode__ and not __str__. IOError inherits its __unicode__ method from BaseException and does indeed miss out the filename... Michael > Thanks, > Alan > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Docutils-develop mailing list > Doc...@li... > https://lists.sourceforge.net/lists/listinfo/docutils-develop > > Please use "Reply All" to reply to the list. > -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog |
From: Michael F. <fuz...@vo...> - 2009-09-11 20:44:33
|
Michael Foord wrote: > Alan G Isaac wrote: > >> On 9/11/2009 2:45 PM, G. Milde wrote: >> >> >>> Hack: Since Python 2.6, ``'%s' % error`` returns a unicode >>> object. IOError seems to miss a `__unicode__` method and the >>> fallback `__repr__` does not report the file name. Explicitely >>> converting to str fixes this:: >>> print '%s\n%s\n%s\n' %(error, str(error), repr(error)) >>> >>> >> I think this should be seen as a bug in Python. I'll test it against trunk and report if necessary. Michael >> Sorry, I'm not understanding that. :: >> >> Python 2.6.2 (r262:71605, Apr 14 2009, 22:40:02) [MSC v.1500 32 bit (Intel)] on win32 >> Type "help", "copyright", "credits" or "license" for more information. >> >>> e = IOError('msg') >> >>> type("%s"%e) >> <type 'str'> >> >> (Some outcome with unicoded strings.) >> >> >> > > With Python 2.6: > > > >>> try: > ... open('flooble') > ... except Exception as e: > ... pass > ... > >>> e > IOError(2, 'No such file or directory') > >>> unicode(e) > u"(2, 'No such file or directory')" > >>> str(e) > "[Errno 2] No such file or directory: 'flooble'" > >>> > >>> u'%s' % e > u"(2, 'No such file or directory')" > >>> '%s' % e > "[Errno 2] No such file or directory: 'flooble'" > > > Interoplating into a Unicode string calls __unicode__ and not __str__. > IOError inherits its __unicode__ method from BaseException and does > indeed miss out the filename... > > Michael > > > >> Thanks, >> Alan >> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day >> trial. Simplify your report design, integration and deployment - and focus on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Docutils-develop mailing list >> Doc...@li... >> https://lists.sourceforge.net/lists/listinfo/docutils-develop >> >> Please use "Reply All" to reply to the list. >> >> > > > -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog |
From: <gr...@us...> - 2009-09-12 20:25:38
|
On Fri, 11 Sep 2009, Guenter Milde wrote: > On 2009-09-11, gr...@us... wrote: >> On Thu, 10 Sep 2009, Guenter Milde wrote: >>> On 2009-09-04, Alan G Isaac wrote: >>>> On 9/4/2009 2:52 PM, Guenter Milde wrote: > >>>>> 2. IOError does not report filename > ... >> is this now a showstopper for the release ? > > Solved with the latest SVN commit. docutils/parsers/rst/directives/tables.py line 278 is the same problem. same solution ? also for "u'filename'" ? cheers -- |
From: Guenter M. <mi...@us...> - 2009-09-14 07:14:37
|
On 2009-09-12, gr...@us... wrote: > On Fri, 11 Sep 2009, Guenter Milde wrote: >> On 2009-09-11, gr...@us... wrote: >>> On Thu, 10 Sep 2009, Guenter Milde wrote: >>>> On 2009-09-04, Alan G Isaac wrote: >>>>> On 9/4/2009 2:52 PM, Guenter Milde wrote: >>>>>> 2. IOError does not report filename >> ... >>> is this now a showstopper for the release ? >> Solved with the latest SVN commit. > docutils/parsers/rst/directives/tables.py line 278 is the same > problem. same solution ? also for "u'filename'" ? The error report for:: Include a table: .. csv-table:: :file: nön-existing-table.csv is:: [...]/include-nonexisting-file.txt:12: (SEVERE/4) Problems with "csv-table" directive path: (2, 'Datei oder Verzeichnis nicht gefunden'). .. csv-table:: :file: n\xf6n-existing-table.csv Exiting due to level-4 (SEVERE) system message. As it shows both, the location (line 12) and the faulty directive including the filname, there is no need to hack around the IOError in this case. This raises the question if we should provide a line number with the .. include:: directive too, rather than the ugly hack. Günter |
From: <gr...@us...> - 2009-09-14 14:04:19
|
On Mon, 14 Sep 2009, Guenter Milde wrote: > Include a table: > > .. csv-table:: > :file: nön-existing-table.csv > > is:: > > [...]/include-nonexisting-file.txt:12: (SEVERE/4) Problems with "csv-table" directive path: > (2, 'Datei oder Verzeichnis nicht gefunden'). > > .. csv-table:: > :file: n\xf6n-existing-table.csv > > Exiting due to level-4 (SEVERE) system message. > > As it shows both, the location (line 12) and the faulty directive including > the filname, there is no need to hack around the IOError in this case. you are right > This raises the question if we should provide a line number with the > .. include:: directive too, rather than the ugly hack. this would be cool, OTOH i am on the edge to calling freeze cheers -- |
From: engelbert g. <gr...@us...> - 2009-09-14 14:51:29
|
On Mon, Sep 14, 2009 at 3:33 PM, <gr...@us...> wrote: >> This raises the question if we should provide a line number with the >> .. include:: directive too, rather than the ugly hack. > > this would be cool, OTOH i am on the edge to calling freeze freeze not yet * all is not supported in python2.3 and 2.4 so latex-writer fails * i couldnt test the pifont codepath that uses all. |
From: Guenter M. <mi...@us...> - 2009-09-18 10:02:25
|
On 2009-09-14, engelbert gruber wrote: > freeze not yet The hold of the freeze was used to fix some more bugs. (See HISTORY.txt plus - Fix [ 2821266 ] --strict option works now like --halt=info. and the commit log.) There is one more important bug where I need testing by a Windows user: Test suite failure on Windows (CR/LF incompatibility) http://sourceforge.net/tracker/?func=detail&aid=2809965&group_id=38414&atid=422030 The problem here is that the expected output differs in Windows, Mac and Unix due to different expansions of the newline ('\n'). I my view, Docutils should produce files with "native" newline markup, so care should be taken that the test data files are in the right format for the respective platform. There might be an issue with using a daily snapshot versus SVN checkout. Günter |
From: <gr...@us...> - 2009-09-20 19:16:48
|
On Fri, 18 Sep 2009, Guenter Milde wrote: > On 2009-09-14, engelbert gruber wrote: > >> freeze not yet > > The hold of the freeze was used to fix some more bugs. > (See HISTORY.txt plus > - Fix [ 2821266 ] --strict option works now like --halt=info. > and the commit log.) > > > There is one more important bug where I need testing by a Windows user: > > Test suite failure on Windows (CR/LF incompatibility) > http://sourceforge.net/tracker/?func=detail&aid=2809965&group_id=38414&atid=422030 > > The problem here is that the expected output differs in Windows, Mac and > Unix due to different expansions of the newline ('\n'). I my view, > Docutils should produce files with "native" newline markup, so care > should be taken that the test data files are in the right format for the > respective platform. There might be an issue with using a daily snapshot > versus SVN checkout. you give the freeze (mostly freezing yourself) then i try the release cheers and many thanks -- |
From: Guenter M. <mi...@us...> - 2009-09-22 08:22:07
|
On 2009-09-20, gr...@us... wrote: > On Fri, 18 Sep 2009, Guenter Milde wrote: >> On 2009-09-14, engelbert gruber wrote: > you give the freeze (mostly freezing yourself) then i try the release OK. I will do a "feature freeze" from now on and concentrate on important bugfixes only. * invalid link **without any warning** with the construct:: .. |x| replace:: `External Hyperlink`_ .. _External Hyperlink: external.html This should be an |x| https://sourceforge.net/tracker/?func=detail&aid=1627229&group_id=38414&atid=422030 See also my separarate posting. * wrong line numbers for errors in included files https://sourceforge.net/tracker/?func=detail&aid=2788716&group_id=38414&atid=422030 Might be too complex to solve before 0.6 * There are 6 open bugs for the newlatex writer. Is there still someone working on this writer or should we document it as unmaintained. Please test the latex writer's compatibility code for templates with Python 2.3. After the release, I will start working on the code-block and math directives. Günter |
From: <gr...@us...> - 2009-09-22 14:40:11
|
On Tue, 22 Sep 2009, Guenter Milde wrote: > On 2009-09-20, gr...@us... wrote: >> On Fri, 18 Sep 2009, Guenter Milde wrote: >>> On 2009-09-14, engelbert gruber wrote: > >> you give the freeze (mostly freezing yourself) then i try the release > > OK. I will do a "feature freeze" from now on and concentrate on important > bugfixes only. > > > * invalid link **without any warning** with the construct:: > > .. |x| replace:: `External Hyperlink`_ > > .. _External Hyperlink: external.html > > This should be an |x| > > https://sourceforge.net/tracker/?func=detail&aid=1627229&group_id=38414&atid=422030 > > See also my separarate posting. > > * wrong line numbers for errors in included files > https://sourceforge.net/tracker/?func=detail&aid=2788716&group_id=38414&atid=422030 > > Might be too complex to solve before 0.6 > > > * There are 6 open bugs for the newlatex writer. Is there still someone > working on this writer or should we document it as unmaintained. +1 > Please test the latex writer's compatibility code for templates with > Python 2.3. done , alltests.py 1102 tests OK cheers -- |