jsumners / jsumners/feedparser
Ampersand in URLs are handled incorrectly on Windows (XP?)
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. Parse a feed with URLs containing ampersand
Expected output:
http://somehost.net/torrents.php?action=download&authkey=removed&torrent_pass=re
moved&id=137212
The link in items dictionary looks like this:
http://somehost.net/torrents.php?action=download&authkey=removed&torrent_p
ass=removed&id=137212
What version of the product are you using? On what operating system?
This problem occurs only on Windows (tested only Windows XP)
feedparser v5.1
Please provide any additional information below.
Original issue reported on code.google.com by bendi...@gmail.com on 17 May 2012 at 10:43
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
Start by reproducing the feed parsing case with ampersand-containing URLs on Windows, using the example feed and item dictionary output in the issue. Trace where URL text is transformed during parsing; done means the item URL preserves literal ampersands rather than adding the displayed amp-related text, while other platforms remain unaffected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100