jsumners / jsumners/feedparser
./tests/illformed/undeclared_namespace.xml fails on python 3.3.2 on RHEL-6
Open
Nobody has claimed this yet.
auto-migrated
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
What steps will reproduce the problem?
1.run tests on the above mentioned configuration (while building a Fedora
package for 5.1.3)
2.
3.
What is the expected output? What do you see instead?
======================================================================
FAIL: ./tests/illformed/undeclared_namespace.xml: undeclared namespace
----------------------------------------------------------------------
Traceback (most recent call last):
File "feedparsertest.py", line 752, in <lambda>
self.failUnlessEval(xmlfile, evalString)
File "feedparsertest.py", line 166, in failUnlessEval
raise self.failureException, failure
AssertionError: not eval(bozo)
WITH env({'bozo': 0,
'encoding': u'utf-8',
'entries': [],
'feed': {'subtitle': u'Foo',
'subtitle_detail': {'base': u'',
'language': None,
'type': u'text/plain',
'value': u'Foo'}},
'namespaces': {},
'version': u'rss20'})
----------------------------------------------------------------------
What version of the product are you using? On what operating system?
python-feedparser-5.1.3-7 from Fedora rebuilt on RHEL-6 with
python3-3.3.2-10.0.1.bundledExpat.el6.x86_64
Please provide any additional information below.
Original issue reported on code.google.com by matej.c...@gmail.com on 22 Jul 2014 at 9:08
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure on Python 3.3.2 on RHEL-6 using tests/illformed/undeclared_namespace.xml. Read feedparsertest.py around lines 752 and 166 to understand the failing evaluation, then compare the bozo result with the expected test behavior. Done means this test passes on the reported configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100