Last modified: 2014-10-31 05:52:10 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T57155, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 55155 - LEFT-TO-RIGHT MARK makes categories() fail
LEFT-TO-RIGHT MARK makes categories() fail
Status: NEW
Product: Pywikibot
Classification: Unclassified
General (Other open bugs)
core-(2.0)
All All
: High major
: ---
Assigned To: Pywikipedia bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-05 04:34 UTC by Kunal Mehta (Legoktm)
Modified: 2014-10-31 05:52 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Kunal Mehta (Legoktm) 2013-10-05 04:34:34 UTC
Originally from: http://sourceforge.net/p/pywikipediabot/bugs/1571/
Reported by: nu11zer0
Created on: 2013-01-30 19:36:16
Subject: LEFT-TO-RIGHT MARK makes categories() fail
Original description:
In categories\(\) from class Page, if there is LEFT-TO-RIGHT MARK or other hidden characters in "\[\[Category:", pywikibot will fail to capture this category. I noticed that in constructor of class Page, there is the code for stripping many hidden characters. So why don't we apply this code with category and others \(I'm not sure if there are other things which need stripping hidden characters. Interwiki link? At least, I see many regular expressions for capturing links, these actions can fail with hidden character too.\)

Pywikipedia trunk/pywikipedia/ \(r11014, 2013/01/28, 20:55:48, ok\)
Python 2.7.3 \(default, Sep 26 2012, 21:53:58\)
\[GCC 4.7.2\]
config-settings:
use\_api = True
use\_api\_login = True
unicode test: ok
Comment 1 John Mark Vandenberg 2014-10-31 05:52:10 UTC
This was report as a compat issue, but I suspect this issue also exists in core, so setting this bug to be a core bug until it can be confirmed that it isnt.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links