Bugs item #3053539, was opened at 2010-08-26 10:05
Message generated for change (Tracker Item Submitted) made by djbarrett
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=603138&aid=305353…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Daniel Barrett (djbarrett)
Assigned to: Nobody/Anonymous (nobody)
Summary: category.py move ignores noinclude, includeonly
Initial Comment:
When running "python category.py move", if the old category is enclosed in
<noinclude> or <includeonly> tags, the new, replaced category is not, which is
a problem. For example, this construction:
<includeonly>[[Category:Foo]]</includeonly>
when operated on by:
python category.py move -from:"Foo" -to:"Bar"
produces:
<includeonly></includeonly>
[[Category:Bar]]
which is wrong.
This bug has existed for a long time, at least a few years.
$ python version.py
Python 2.4.3 (#1, Sep 3 2009, 15:37:37)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-46)]
config-settings:
use_api = True
use_api_login = True
$ svn info
Revision: 8319
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=603138&aid=305353…