Universal Feed Parser issue

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • i3dmaster
    #1

    Universal Feed Parser issue

    I have a sample Atom feed like this:

    <?xml version='1.0' encoding='utf-8'?>
    <feed xmlns='http://www.w3.org/2005/Atom' xmlns:foo='http ://
    app.example.com/app/2007'>
    <id>http://app.example.com/fjie4id939xdl3i o23</id>
    <title type='text'>foo </title>
    <author>
    <name>bar</name>
    <email>foo@foo. com</email>
    </author>
    <updated>2007-04-09T22:14:15.000 Z</updated>
    <link rel='http://app.example.com/#event' type='applicati on/atom
    +xml' href='http://www.foo.com/app/feeds/#app1'></link>
    <foo:timezone value='America/Mountain'></foo:timezone>
    <foo:status value='confirme d'></foo:status>
    </feed>

    After parsed by feedparser, the timezone element does not get the
    attribute "America/Mountain". Same thing on status element. This does
    not sound an expected result. I am wondering if it should be
    considered a bug...

    Tags: None
    • Gabriel Genellina
      #2
      Re: Universal Feed Parser issue

      En Tue, 10 Apr 2007 14:58:42 -0300, i3dmaster <i3dmaster@gmai l.com>
      escribió:
      I have a sample Atom feed like this:
      >
      <?xml version='1.0' encoding='utf-8'?>
      <feed xmlns='http://www.w3.org/2005/Atom' xmlns:foo='http ://
      app.example.com/app/2007'...
      <foo:timezone value='America/Mountain'></foo:timezone>
      <foo:status value='confirme d'></foo:status>
      </feed>
      >
      After parsed by feedparser, the timezone element does not get the
      attribute "America/Mountain". Same thing on status element. This does
      not sound an expected result. I am wondering if it should be
      considered a bug...
      Usually it's a good idea to read the documentation.. .
      http://www.feedparser.org/docs/namespace-handling.html


      --
      Gabriel Genellina

        Comment

        • i3dmaster
          #3
          Re: Universal Feed Parser issue

          On Apr 10, 6:45 pm, "Gabriel Genellina" <gagsl-...@yahoo.com.a r>
          wrote:
          En Tue, 10 Apr 2007 14:58:42 -0300, i3dmaster <i3dmas...@gmai l.com>
          escribió:
          >
          I have a sample Atom feed like this:
          >
          <?xml version='1.0' encoding='utf-8'?>
          <feed xmlns='http://www.w3.org/2005/Atom'xmlns:foo= 'http://
          app.example.com/app/2007'...
          <foo:timezone value='America/Mountain'></foo:timezone>
          <foo:status value='confirme d'></foo:status>
          </feed>
          >
          After parsed by feedparser, the timezone element does not get the
          attribute "America/Mountain". Same thing on status element. This does
          not sound an expected result. I am wondering if it should be
          considered a bug...
          >
          Usually it's a good idea to read the documentation.. . http://www.feedparser.org/docs/namespace-handling.html
          >
          --
          Gabriel Genellina

          I did. Perhaps its because of not 100% atom compatible of my feed
          format? See if I use gnosis xml utility to parse it, it works fine
          though...

            Comment

            • Gabriel Genellina
              #4
              Re: Universal Feed Parser issue

              En Wed, 11 Apr 2007 01:51:13 -0300, i3dmaster <i3dmaster@gmai l.com>
              escribió:
              On Apr 10, 6:45 pm, "Gabriel Genellina" <gagsl-...@yahoo.com.a r>
              wrote:
              >En Tue, 10 Apr 2007 14:58:42 -0300, i3dmaster <i3dmas...@gmai l.com>
              >escribió:
              >>
              <?xml version='1.0' encoding='utf-8'?>
              <feed xmlns='http://www.w3.org/2005/Atom'xmlns:foo= 'http://
              app.example.com/app/2007'...
              <foo:timezone value='America/Mountain'></foo:timezone>
              <foo:status value='confirme d'></foo:status>
              </feed>
              >>
              After parsed by feedparser, the timezone element does not get the
              attribute "America/Mountain". Same thing on status element. This does
              not sound an expected result. I am wondering if it should be
              considered a bug...
              >>
              >Usually it's a good idea to read the documentation.. .
              >http://www.feedparser.org/docs/namespace-handling.html
              >
              I did. Perhaps its because of not 100% atom compatible of my feed
              format? See if I use gnosis xml utility to parse it, it works fine
              though...
              The link above answers *exactly* your question - have you actually read
              the page?

              --
              Gabriel Genellina

                Comment

                • i3dmaster
                  #5
                  Re: Universal Feed Parser issue

                  On Apr 11, 12:06 am, "Gabriel Genellina" <gagsl-...@yahoo.com.a r>
                  wrote:
                  En Wed, 11 Apr 2007 01:51:13 -0300, i3dmaster <i3dmas...@gmai l.com>
                  escribió:
                  >
                  >
                  >
                  On Apr 10, 6:45 pm, "Gabriel Genellina" <gagsl-...@yahoo.com.a r>
                  wrote:
                  En Tue, 10 Apr 2007 14:58:42 -0300, i3dmaster <i3dmas...@gmai l.com>
                  escribió:
                  >
                  <?xml version='1.0' encoding='utf-8'?>
                  <feed xmlns='http://www.w3.org/2005/Atom'xmlns:foo= 'http://
                  app.example.com/app/2007'...
                  <foo:timezone value='America/Mountain'></foo:timezone>
                  <foo:status value='confirme d'></foo:status>
                  </feed>
                  >
                  After parsed by feedparser, the timezone element does not get the
                  attribute "America/Mountain". Same thing on status element. This does
                  not sound an expected result. I am wondering if it should be
                  considered a bug...
                  >
                  Usually it's a good idea to read the documentation.. .
                  >http://www.feedparser.org/docs/namespace-handling.html
                  >
                  I did. Perhaps its because of not 100% atom compatible of my feed
                  format? See if I use gnosis xml utility to parse it, it works fine
                  though...
                  >
                  The link above answers *exactly* your question - have you actually read
                  the page?
                  >
                  --
                  Gabriel Genellina
                  Hmm... well I don't know if I made my question clear then or you might
                  have misread it?... Anyway, the namespace handling wasn't the issue
                  of this question. feedparser handles it as expected but only when
                  there is a text value associated with it. Look at the rdf file you
                  will see the prism:issn element has a text value but in my case, the
                  foo:timezone element DOES NOT have a text value but a Attribute or
                  maybe attributes... What it looks like is feedparser simply ignores
                  all the attributes when parsing it. This behavior wasn't seen from
                  other xml parsers though.

                    Comment

                    • i3dmaster
                      #6
                      Re: Universal Feed Parser issue

                      On Apr 11, 12:06 am, "Gabriel Genellina" <gagsl-...@yahoo.com.a r>
                      wrote:
                      En Wed, 11 Apr 2007 01:51:13 -0300, i3dmaster <i3dmas...@gmai l.com>
                      escribió:
                      >
                      >
                      >
                      On Apr 10, 6:45 pm, "Gabriel Genellina" <gagsl-...@yahoo.com.a r>
                      wrote:
                      En Tue, 10 Apr 2007 14:58:42 -0300, i3dmaster <i3dmas...@gmai l.com>
                      escribió:
                      >
                      <?xml version='1.0' encoding='utf-8'?>
                      <feed xmlns='http://www.w3.org/2005/Atom'xmlns:foo= 'http://
                      app.example.com/app/2007'...
                      <foo:timezone value='America/Mountain'></foo:timezone>
                      <foo:status value='confirme d'></foo:status>
                      </feed>
                      >
                      After parsed by feedparser, the timezone element does not get the
                      attribute "America/Mountain". Same thing on status element. This does
                      not sound an expected result. I am wondering if it should be
                      considered a bug...
                      >
                      Usually it's a good idea to read the documentation.. .
                      >http://www.feedparser.org/docs/namespace-handling.html
                      >
                      I did. Perhaps its because of not 100% atom compatible of my feed
                      format? See if I use gnosis xml utility to parse it, it works fine
                      though...
                      >
                      The link above answers *exactly* your question - have you actually read
                      the page?
                      >
                      --
                      Gabriel Genellina
                      Hmm... well I don't know if I made my question clear then or you might
                      have misread it?... Anyway, the namespace handling wasn't the issue
                      of this question. feedparser handles it as expected but only when
                      there is a text value associated with it. Look at the rdf file you
                      will see the prism:issn element has a text value but in my case, the
                      foo:timezone element DOES NOT have a text value but a Attribute or
                      maybe attributes... What it looks like is feedparser simply ignores
                      all the attributes when parsing it. This behavior wasn't seen from
                      other xml parsers though.

                        Comment

                        • Gabriel Genellina
                          #7
                          Re: Universal Feed Parser issue

                          En Wed, 11 Apr 2007 14:07:15 -0300, i3dmaster <i3dmaster@gmai l.com>
                          escribió:
                          Hmm... well I don't know if I made my question clear then or you might
                          have misread it?... Anyway, the namespace handling wasn't the issue
                          of this question. feedparser handles it as expected but only when
                          there is a text value associated with it. Look at the rdf file you
                          will see the prism:issn element has a text value but in my case, the
                          foo:timezone element DOES NOT have a text value but a Attribute or
                          maybe attributes... What it looks like is feedparser simply ignores
                          all the attributes when parsing it. This behavior wasn't seen from
                          other xml parsers though.
                          Oh, sorry! I thought you were complaining about the namespace.
                          You're out of luck with this parser - see my own reply on January for a
                          similar issue:
                          404 Not Found
                          http://mail.python.org/pipermail/python-list/2007-January/422237.html


                          --
                          Gabriel Genellina

                            Comment

                            • i3dmaster
                              #8
                              Re: Universal Feed Parser issue

                              On Apr 11, 12:01 pm, "Gabriel Genellina" <gagsl-...@yahoo.com.a r>
                              wrote:
                              En Wed, 11 Apr 2007 14:07:15 -0300, i3dmaster <i3dmas...@gmai l.com>
                              escribió:
                              >
                              Hmm... well I don't know if I made my question clear then or you might
                              have misread it?... Anyway, the namespace handling wasn't the issue
                              of this question. feedparser handles it as expected but only when
                              there is a text value associated with it. Look at the rdf file you
                              will see the prism:issn element has a text value but in my case, the
                              foo:timezone element DOES NOT have a text value but a Attribute or
                              maybe attributes... What it looks like is feedparser simply ignores
                              all the attributes when parsing it. This behavior wasn't seen from
                              other xml parsers though.
                              >
                              Oh, sorry! I thought you were complaining about the namespace.
                              You're out of luck with this parser - see my own reply on January for a
                              similar issue:http://mail.python.org/pipermail/pyt...ry/422237.html
                              >
                              --
                              Gabriel Genellina

                              Ok no problem. Back to my original question, should this be considered
                              a bug (didn't see a bug reported though) ? Do you know if the
                              developer is considering fixing it in the future?

                              Thanks,
                              Jim

                                Comment

                                • Gabriel Genellina
                                  #9
                                  Re: Universal Feed Parser issue

                                  En Thu, 12 Apr 2007 00:23:36 -0300, i3dmaster <i3dmaster@gmai l.com>
                                  escribió:
                                  Ok no problem. Back to my original question, should this be considered
                                  a bug (didn't see a bug reported though) ? Do you know if the
                                  developer is considering fixing it in the future?
                                  I have no idea! The bug was reported more than a year ago:
                                  Just a moment...
                                  http://sourceforge.net/tracker/?func=browse&group_id=112328&atid=661937

                                  with no comments from the developer...
                                  Why don't you switch to a more general and supported tool, like
                                  ElementTree?

                                  --
                                  Gabriel Genellina

                                    Comment

                                    Previous template Next
                                    Working...