Last modified: 2014-09-18 13:06:51 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 T57013, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 55013 - Optimize multiple replace.py instances
Optimize multiple replace.py instances
Status: NEW
Product: Pywikibot
Classification: Unclassified
Other scripts (Other open bugs)
core-(2.0)
All All
: Unprioritized enhancement
: ---
Assigned To: Pywikipedia bugs
: performance
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-05 04:04 UTC by Kunal Mehta (Legoktm)
Modified: 2014-09-18 13:06 UTC (History)
2 users (show)

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


Attachments

Description Kunal Mehta (Legoktm) 2013-10-05 04:04:13 UTC
Originally from: http://sourceforge.net/p/pywikipediabot/feature-requests/333/
Reported by: Anonymous user
Created on: 2013-03-12 21:11:04
Subject: Optimize multiple replace.py instances
Original description:
Since the biggest part of the time and I/O resources, in a replace.py based on a xml file, is reading and uncompressing the xml file itself. When this action is done, execute 10 or 50 regex is very similar. I think that the replace.py should be able to apply more -fix in the same time. Also, if the -save parameter is active, each -fix should go in a different file. 

I think that passing an array to -fix and -save to be able to do this. This implementation is only an idea, obviusly ;\)


python version.py
Pywikipedia trunk/pywikipedia/ \(r11200, 2013/03/09, 11:43:52, OUTDATED\)
Python 2.7.3 \(default, Sep 26 2012, 21:51:14\) 
\[GCC 4.7.2\]
config-settings:
use\_api = True
use\_api\_login = True
unicode test: ok
Comment 1 Kunal Mehta (Legoktm) 2013-10-05 04:04:16 UTC
The idea is good, but much more command-line parameters are involved, practically each except -xml and -xmlstart.
Do you have any measurements on time consumption?

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


Navigation
Links