Csound Csound-dev Csound-tekno Search About

[Csnd-dev] cannot build opcodeparser.xml

Date2018-12-30 21:30
Fromjoachim heintz
Subject[Csnd-dev] cannot build opcodeparser.xml
jh@lenov2:~/src/csound-manual-git$ /usr/bin/python opcodeparser.py
Traceback (most recent call last):
   File "opcodeparser.py", line 51, in 
     xmldoc = minidom.parseString(newfile)
   File "/usr/lib/python2.7/xml/dom/minidom.py", line 1928, in parseString
     return expatbuilder.parseString(string)
   File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 940, in 
parseString
     return builder.parseString(string)
   File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 223, in 
parseString
     parser.Parse(string, True)
xml.parsers.expat.ExpatError: syntax error: line 1849, column 0

any idea?  this is debian linux 9.6.
thanks -

Date2019-01-01 10:53
FromFrancois PINOT
SubjectRe: [Csnd-dev] cannot build opcodeparser.xml
It was an xml parsing error. I fixed the opcodeparser.py script in git and I adapted it to work with python3 as well.
By the way isn't this script deprecated?

François

Le dim. 30 déc. 2018 à 22:30, joachim heintz <jh@joachimheintz.de> a écrit :
jh@lenov2:~/src/csound-manual-git$ /usr/bin/python opcodeparser.py
Traceback (most recent call last):
   File "opcodeparser.py", line 51, in <module>
     xmldoc = minidom.parseString(newfile)
   File "/usr/lib/python2.7/xml/dom/minidom.py", line 1928, in parseString
     return expatbuilder.parseString(string)
   File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 940, in
parseString
     return builder.parseString(string)
   File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 223, in
parseString
     parser.Parse(string, True)
xml.parsers.expat.ExpatError: syntax error: line 1849, column 0

any idea?  this is debian linux 9.6.
thanks -
        joachim

Date2019-01-01 19:37
Fromjoachim heintz
SubjectRe: [Csnd-dev] cannot build opcodeparser.xml
thanks very much; it works perfectly now.

i don't know that it is deprecated.  what should be used instead?

best -
	joachim


On 01/01/19 11:53, Francois PINOT wrote:
> It was an xml parsing error. I fixed the opcodeparser.py script in git
> and I adapted it to work with python3 as well.
> By the way isn't this script deprecated?
>
> François
>
> Le dim. 30 déc. 2018 à 22:30, joachim heintz  > a écrit :
>
>     jh@lenov2:~/src/csound-manual-git$ /usr/bin/python opcodeparser.py
>     Traceback (most recent call last):
>        File "opcodeparser.py", line 51, in 
>          xmldoc = minidom.parseString(newfile)
>        File "/usr/lib/python2.7/xml/dom/minidom.py", line 1928, in
>     parseString
>          return expatbuilder.parseString(string)
>        File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 940, in
>     parseString
>          return builder.parseString(string)
>        File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 223, in
>     parseString
>          parser.Parse(string, True)
>     xml.parsers.expat.ExpatError: syntax error: line 1849, column 0
>
>     any idea?  this is debian linux 9.6.
>     thanks -
>             joachim

Date2019-01-01 20:17
FromFrancois PINOT
SubjectRe: [Csnd-dev] cannot build opcodeparser.xml
In fact I was wondering if it's deprecated... It generates the file opcodes.xml but when looking  at github, we see that opcodes.xml has not been generated for more than one years. For what do you use this file?

Le mar. 1 janv. 2019 à 20:37, joachim heintz <jh@joachimheintz.de> a écrit :
thanks very much; it works perfectly now.

i don't know that it is deprecated.  what should be used instead?

best -
        joachim


On 01/01/19 11:53, Francois PINOT wrote:
> It was an xml parsing error. I fixed the opcodeparser.py script in git
> and I adapted it to work with python3 as well.
> By the way isn't this script deprecated?
>
> François
>
> Le dim. 30 déc. 2018 à 22:30, joachim heintz <jh@joachimheintz.de
> <mailto:jh@joachimheintz.de>> a écrit :
>
>     jh@lenov2:~/src/csound-manual-git$ /usr/bin/python opcodeparser.py
>     Traceback (most recent call last):
>        File "opcodeparser.py", line 51, in <module>
>          xmldoc = minidom.parseString(newfile)
>        File "/usr/lib/python2.7/xml/dom/minidom.py", line 1928, in
>     parseString
>          return expatbuilder.parseString(string)
>        File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 940, in
>     parseString
>          return builder.parseString(string)
>        File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 223, in
>     parseString
>          parser.Parse(string, True)
>     xml.parsers.expat.ExpatError: syntax error: line 1849, column 0
>
>     any idea?  this is debian linux 9.6.
>     thanks -
>             joachim
>

Date2019-01-01 20:47
Fromjoachim heintz
SubjectRe: [Csnd-dev] cannot build opcodeparser.xml
csoundqt uses it for syntax highlighting.  i justed filed a pull request 
for updating the opcodes.xml file.

i saw that interleave/deinterleave have a manual page, but get no entry 
in opcodes.xml.  do you know where is the place to add them to any list?


On 01/01/19 21:17, Francois PINOT wrote:
> In fact I was wondering if it's deprecated... It generates the file
> opcodes.xml but when looking  at github, we see that opcodes.xml has not
> been generated for more than one years. For what do you use this file?
>
> Le mar. 1 janv. 2019 à 20:37, joachim heintz  > a écrit :
>
>     thanks very much; it works perfectly now.
>
>     i don't know that it is deprecated.  what should be used instead?
>
>     best -
>             joachim
>
>
>     On 01/01/19 11:53, Francois PINOT wrote:
>     > It was an xml parsing error. I fixed the opcodeparser.py script in git
>     > and I adapted it to work with python3 as well.
>     > By the way isn't this script deprecated?
>     >
>     > François
>     >
>     > Le dim. 30 déc. 2018 à 22:30, joachim heintz      
>     > >> a écrit :
>     >
>     >     jh@lenov2:~/src/csound-manual-git$ /usr/bin/python opcodeparser.py
>     >     Traceback (most recent call last):
>     >        File "opcodeparser.py", line 51, in 
>     >          xmldoc = minidom.parseString(newfile)
>     >        File "/usr/lib/python2.7/xml/dom/minidom.py", line 1928, in
>     >     parseString
>     >          return expatbuilder.parseString(string)
>     >        File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 940, in
>     >     parseString
>     >          return builder.parseString(string)
>     >        File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 223, in
>     >     parseString
>     >          parser.Parse(string, True)
>     >     xml.parsers.expat.ExpatError: syntax error: line 1849, column 0
>     >
>     >     any idea?  this is debian linux 9.6.
>     >     thanks -
>     >             joachim
>     >

Date2019-01-01 21:12
FromFrancois PINOT
SubjectRe: [Csnd-dev] cannot build opcodeparser.xml
Oh I see. The following opcodes have no entry in opcodes.xml because they don't match a valid category.

opcodes/deinterleave.xml---- WARNING! No Category Match!
opcodes/ftprint.xml---- WARNING! No Category Match!
opcodes/ftslice.xml---- WARNING! No Category Match!
opcodes/getrowlin.xml---- WARNING! No Category Match!
opcodes/interleave.xml---- WARNING! No Category Match!
opcodes/tabrowlin.xml---- WARNING! No Category Match!

Valid categories are referenced in categories.py. I'll have a look tomorrow.

François

Le mar. 1 janv. 2019 à 21:47, joachim heintz <jh@joachimheintz.de> a écrit :
csoundqt uses it for syntax highlighting.  i justed filed a pull request
for updating the opcodes.xml file.

i saw that interleave/deinterleave have a manual page, but get no entry
in opcodes.xml.  do you know where is the place to add them to any list?


On 01/01/19 21:17, Francois PINOT wrote:
> In fact I was wondering if it's deprecated... It generates the file
> opcodes.xml but when looking  at github, we see that opcodes.xml has not
> been generated for more than one years. For what do you use this file?
>
> Le mar. 1 janv. 2019 à 20:37, joachim heintz <jh@joachimheintz.de
> <mailto:jh@joachimheintz.de>> a écrit :
>
>     thanks very much; it works perfectly now.
>
>     i don't know that it is deprecated.  what should be used instead?
>
>     best -
>             joachim
>
>
>     On 01/01/19 11:53, Francois PINOT wrote:
>     > It was an xml parsing error. I fixed the opcodeparser.py script in git
>     > and I adapted it to work with python3 as well.
>     > By the way isn't this script deprecated?
>     >
>     > François
>     >
>     > Le dim. 30 déc. 2018 à 22:30, joachim heintz <jh@joachimheintz.de
>     <mailto:jh@joachimheintz.de>
>     > <mailto:jh@joachimheintz.de <mailto:jh@joachimheintz.de>>> a écrit :
>     >
>     >     jh@lenov2:~/src/csound-manual-git$ /usr/bin/python opcodeparser.py
>     >     Traceback (most recent call last):
>     >        File "opcodeparser.py", line 51, in <module>
>     >          xmldoc = minidom.parseString(newfile)
>     >        File "/usr/lib/python2.7/xml/dom/minidom.py", line 1928, in
>     >     parseString
>     >          return expatbuilder.parseString(string)
>     >        File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 940, in
>     >     parseString
>     >          return builder.parseString(string)
>     >        File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 223, in
>     >     parseString
>     >          parser.Parse(string, True)
>     >     xml.parsers.expat.ExpatError: syntax error: line 1849, column 0
>     >
>     >     any idea?  this is debian linux 9.6.
>     >     thanks -
>     >             joachim
>     >
>

Date2019-01-01 21:16
Fromjoachim heintz
SubjectRe: [Csnd-dev] cannot build opcodeparser.xml
ok super

On 01/01/19 22:12, Francois PINOT wrote:
> Oh I see. The following opcodes have no entry in opcodes.xml because
> they don't match a valid category.
>
> opcodes/deinterleave.xml---- WARNING! No Category Match!
> opcodes/ftprint.xml---- WARNING! No Category Match!
> opcodes/ftslice.xml---- WARNING! No Category Match!
> opcodes/getrowlin.xml---- WARNING! No Category Match!
> opcodes/interleave.xml---- WARNING! No Category Match!
> opcodes/tabrowlin.xml---- WARNING! No Category Match!
>
> Valid categories are referenced in categories.py. I'll have a look tomorrow.
>
> François
>
> Le mar. 1 janv. 2019 à 21:47, joachim heintz  > a écrit :
>
>     csoundqt uses it for syntax highlighting.  i justed filed a pull
>     request
>     for updating the opcodes.xml file.
>
>     i saw that interleave/deinterleave have a manual page, but get no entry
>     in opcodes.xml.  do you know where is the place to add them to any list?
>
>
>     On 01/01/19 21:17, Francois PINOT wrote:
>     > In fact I was wondering if it's deprecated... It generates the file
>     > opcodes.xml but when looking  at github, we see that opcodes.xml
>     has not
>     > been generated for more than one years. For what do you use this file?
>     >
>     > Le mar. 1 janv. 2019 à 20:37, joachim heintz      
>     > >> a écrit :
>     >
>     >     thanks very much; it works perfectly now.
>     >
>     >     i don't know that it is deprecated.  what should be used instead?
>     >
>     >     best -
>     >             joachim
>     >
>     >
>     >     On 01/01/19 11:53, Francois PINOT wrote:
>     >     > It was an xml parsing error. I fixed the opcodeparser.py
>     script in git
>     >     > and I adapted it to work with python3 as well.
>     >     > By the way isn't this script deprecated?
>     >     >
>     >     > François
>     >     >
>     >     > Le dim. 30 déc. 2018 à 22:30, joachim heintz
>     
>     >     >
>     >     > 
>     >>> a écrit :
>     >     >
>     >     >     jh@lenov2:~/src/csound-manual-git$ /usr/bin/python
>     opcodeparser.py
>     >     >     Traceback (most recent call last):
>     >     >        File "opcodeparser.py", line 51, in 
>     >     >          xmldoc = minidom.parseString(newfile)
>     >     >        File "/usr/lib/python2.7/xml/dom/minidom.py", line
>     1928, in
>     >     >     parseString
>     >     >          return expatbuilder.parseString(string)
>     >     >        File "/usr/lib/python2.7/xml/dom/expatbuilder.py",
>     line 940, in
>     >     >     parseString
>     >     >          return builder.parseString(string)
>     >     >        File "/usr/lib/python2.7/xml/dom/expatbuilder.py",
>     line 223, in
>     >     >     parseString
>     >     >          parser.Parse(string, True)
>     >     >     xml.parsers.expat.ExpatError: syntax error: line 1849,
>     column 0
>     >     >
>     >     >     any idea?  this is debian linux 9.6.
>     >     >     thanks -
>     >     >             joachim
>     >     >
>     >

Date2019-01-02 09:06
FromFrancois PINOT
SubjectRe: [Csnd-dev] cannot build opcodeparser.xml
Done in git

Le mar. 1 janv. 2019 à 22:16, joachim heintz <jh@joachimheintz.de> a écrit :
ok super

On 01/01/19 22:12, Francois PINOT wrote:
> Oh I see. The following opcodes have no entry in opcodes.xml because
> they don't match a valid category.
>
> opcodes/deinterleave.xml---- WARNING! No Category Match!
> opcodes/ftprint.xml---- WARNING! No Category Match!
> opcodes/ftslice.xml---- WARNING! No Category Match!
> opcodes/getrowlin.xml---- WARNING! No Category Match!
> opcodes/interleave.xml---- WARNING! No Category Match!
> opcodes/tabrowlin.xml---- WARNING! No Category Match!
>
> Valid categories are referenced in categories.py. I'll have a look tomorrow.
>
> François
>
> Le mar. 1 janv. 2019 à 21:47, joachim heintz <jh@joachimheintz.de
> <mailto:jh@joachimheintz.de>> a écrit :
>
>     csoundqt uses it for syntax highlighting.  i justed filed a pull
>     request
>     for updating the opcodes.xml file.
>
>     i saw that interleave/deinterleave have a manual page, but get no entry
>     in opcodes.xml.  do you know where is the place to add them to any list?
>
>
>     On 01/01/19 21:17, Francois PINOT wrote:
>     > In fact I was wondering if it's deprecated... It generates the file
>     > opcodes.xml but when looking  at github, we see that opcodes.xml
>     has not
>     > been generated for more than one years. For what do you use this file?
>     >
>     > Le mar. 1 janv. 2019 à 20:37, joachim heintz <jh@joachimheintz.de
>     <mailto:jh@joachimheintz.de>
>     > <mailto:jh@joachimheintz.de <mailto:jh@joachimheintz.de>>> a écrit :
>     >
>     >     thanks very much; it works perfectly now.
>     >
>     >     i don't know that it is deprecated.  what should be used instead?
>     >
>     >     best -
>     >             joachim
>     >
>     >
>     >     On 01/01/19 11:53, Francois PINOT wrote:
>     >     > It was an xml parsing error. I fixed the opcodeparser.py
>     script in git
>     >     > and I adapted it to work with python3 as well.
>     >     > By the way isn't this script deprecated?
>     >     >
>     >     > François
>     >     >
>     >     > Le dim. 30 déc. 2018 à 22:30, joachim heintz
>     <jh@joachimheintz.de <mailto:jh@joachimheintz.de>
>     >     <mailto:jh@joachimheintz.de <mailto:jh@joachimheintz.de>>
>     >     > <mailto:jh@joachimheintz.de <mailto:jh@joachimheintz.de>
>     <mailto:jh@joachimheintz.de <mailto:jh@joachimheintz.de>>>> a écrit :
>     >     >
>     >     >     jh@lenov2:~/src/csound-manual-git$ /usr/bin/python
>     opcodeparser.py
>     >     >     Traceback (most recent call last):
>     >     >        File "opcodeparser.py", line 51, in <module>
>     >     >          xmldoc = minidom.parseString(newfile)
>     >     >        File "/usr/lib/python2.7/xml/dom/minidom.py", line
>     1928, in
>     >     >     parseString
>     >     >          return expatbuilder.parseString(string)
>     >     >        File "/usr/lib/python2.7/xml/dom/expatbuilder.py",
>     line 940, in
>     >     >     parseString
>     >     >          return builder.parseString(string)
>     >     >        File "/usr/lib/python2.7/xml/dom/expatbuilder.py",
>     line 223, in
>     >     >     parseString
>     >     >          parser.Parse(string, True)
>     >     >     xml.parsers.expat.ExpatError: syntax error: line 1849,
>     column 0
>     >     >
>     >     >     any idea?  this is debian linux 9.6.
>     >     >     thanks -
>     >     >             joachim
>     >     >
>     >
>