 | This user account is a bot that uses Python and mwparserfromhell, operated by Garzfoth (talk). It is used to make repetitive automated or semi-automated edits that would be extremely tedious to do manually, in accordance with the bot policy. The bot is currently inactive but retains the approval of the community. Administrators: if this bot is malfunctioning or causing harm, please block it. |
| This user is a bot | |
|---|---|
| (talk · contribs) | |
| Status | Inactive |
| Operator | Garzfoth (talk) |
| Author | Garzfoth (talk) |
| Approved? | Yes (BRFA) |
| Flagged? | Yes |
| Task(s) | Fixing various widespread issues with certain infoboxes (currently limited to Infobox power station and Infobox dam). |
| Edit rate | Limited to no more than 6 edits per minute during operation. |
| Edit period(s) | As needed |
| Automatic or manual? | Semi-automatic |
| Programming language(s) | Python/mwparserfromhell |
| Exclusion compliant? | Yes |
| Source code published? | Editing: Yes! Parsing: Not currently Database: Not currently Scraping: Not currently |
| Emergency shutoff-compliant? | No |
Documentation edit
Technical details edit
InfoboxBot is written in Python and consists of three primary components:
- Scrapers (one per infobox type)
- Parsers (one per infobox type)
- An editor
All major components are written in Python. The editor & parser use mwparserfromhell. Data retrieved by the parsers is stored in a MySQL database.
Runs are manually initiated.
Exclusion compliance edit
InfoboxBot is fully exclusion compliant.
Emergency shutoff edit
The bot currently does NOT have emergency shutoff capability implemented, and there are no short term plans to implement this capability.
Modifying the "Shutoff" parameter in the Infobox bot template on this page will NOT disable the bot, so please don't touch it.