pywikibot May 2015

pywikibot@lists.wikimedia.org

10 participants
10 discussions

[Pywikipedia-l] Urlencoded section titles
by Bináris 13 Sep '18

13 Sep '18

Happy Monday, There are strange people who make such links (kindof urlencoded?): [[Második világháború#Partrasz.C3.A1ll.C3.A1s Szic.C3.ADli.C3.A1ban .28Huskey hadm.C5.B1velet.29|Huskey hadműveletben]] So the section title must have been copied from the URL. Do we have a ready tool to fix these? -- Bináris

3 11

[Pywikipedia-l] Template parsing code
by Hannes Röst 02 Sep '16

02 Sep '16

Hello all >From one of my assignments as a bot operator I have some code which does template parsing and general text parsing (e.g. Image/File tags). It is not using regex and thus able to correctly parse nested templates and other such nasty things. I have written those as library classes and written tests for them which cover almost all of the code. I would now really like to contribute that code back to the community. Would you be interested in adding this code to the pywikibot framework? If yes, can I send the code to someone for code review or how do you usually operate? Greetings Hannes PS: wiki userpage is http://en.wikipedia.org/wiki/User:Hannes_R%C3%B6st

5 13

[Pywikipedia-l] Renaming pywikipedia-l, pywikipedia-announce, pywikipedia-bugs
by Amir Ladsgroup 30 May '15

30 May '15

Hey, We are renaming pywikipedia-l, pywikipedia-announce, pywikipedia-bugs to pywikibot, pywikibot-announce, and pywikibot-bugs respectively. It's planned to happen in the mailing list maintenance window at 2015-06-02 17:00 to 19:00 UTC. The task in phabricator is T100707 <https://phabricator.wikimedia.org/T100707>, Feel free to comment. Best -- Amir

1 0

[Pywikipedia-l] Pywikibot 2.0 RC 1 published, and tarball releases not updated
by John Mark Vandenberg 28 May '15

28 May '15

At the Lyon Hackthon, updates to the tarball releases were turned off, and Pywikibot 2.0 release candidate (RC) 1 was published onto PYPI. https://pypi.python.org/pypi/pywikibot The tarball releases are currently locked to the git revision before the Lyon Hackathon. This was done to prevent large code merges affecting users of the tarballs and Wikimedia labs shared pywikibot. There was one large change merged for RC 1, and there are a few more large changes which will be merged before the final pywikibot 2.0. I suggest bot operators avoid the unstable master by not updating regularly using git, but using the labs shared version or the pip package. We'll announce each new release candidate for people to upgrade to. Anyone wanting only the library, without any of the traditional scripts, can now use: $ sudo pip install --pre pywikibot The --pre is needed because the current published version is a pre-release, and modern pip doesnt install those without being explicitly told to do that. Technical documentation, including an up-to-date API reference, is now being published at https://doc.wikimedia.org/pywikibot/ https://doc.wikimedia.org/pywikibot/api_ref/ If you are using pywikibot for your own script, you can now package it as a pypi package and add a dependency in your setup.py on 'pywikibot'. The pywikibot package doesnt include i18n data, and it detects when it is not present. pywikibot core now uses JSON i18n messages, and these can be included in your own package. To enable your own JSON i18n messages, place them in an i18n subdirectory of your package, and your script needs to call pywikibot.i18n.set_messages_package('your_package_name.i18n') https://doc.wikimedia.org/pywikibot/api_ref/pywikibot.html#pywikibot.i18n.s… pywikibot does not require a user-config.py. It can be skipped by setting envvar PYWIKIBOT2_NO_USER_CONFIG. This can be done before calling python, or inside python but before importing pywikibot. e.g. >>> os.environ['PYWIKIBOT2_NO_USER_CONFIG'] = '1' >>> import pywikibot Many thanks to all the developers of 'rewrite' over the years - it is nearly finished ;-) -- John Vandenberg

2 1

[Pywikipedia-l] Moving pages (templates, articles, categories, etc.) from one Wiki to another
by Brenton Horne 19 May '15

19 May '15

Hi, I noticed a script, `pageimport.py`, that I think might do what I want (based on its name & nothing else, granted, there's minimal documentation @ mediawiki.org), which is: * Import Wiki page(s) specified at the command-line, or listed in a text file input from one Wiki to another. * Also transfer images embedded in the page(s) being imported. Making this part of its function loosely similar to that of `imagetransfer.py` * Optionally import all templates used on the page(s). So I wanted to ask, does it? If not, is there any script that can do this for me? Thanks for your time, Brenton

1 0

[Pywikipedia-l] [RFC] Compat deprecation
by Amir Ladsgroup 17 May '15

17 May '15

Hey all, There is a task in phabricator about deprecating compat [1]. Compat "de facto" is deprecated already, and It's more matter of community engagement and helping people to migrate. Please feel free to comment. [1] https://phabricator.wikimedia.org/T99365 Best

1 0

[Pywikipedia-l] Rebasing
by Fabian Neundorf 11 May '15

11 May '15

Hi this is probably not important for long if we transition to Phabricator, but I want to ask if developers could rebase only if necessary (merge conflicts with master) and if you rebase do it in a separate patchset. The reason being that when you compare two patchsets to determine the changes to a version you've already reviewed that this is ugly if there was a rebase in between as the changes due to the rebase are included in that. This means gerrit now show unrelated changes and it's harder to determine which change were introduced due to the rebase and which were intentionally added by the dev to the new patch set. Thank you in advance ;) For example the change to generate_user_files between PS25 and PS26 [0] are neither a part of PS25 nor PS26. Fabian [0]: https://gerrit.wikimedia.org/r/#/c/195105/25..26/generate_user_files.py

2 1

[Pywikipedia-l] temporary breaking change: cosmetic changes moved into library
by John Mark Vandenberg 07 May '15

07 May '15

cosmetic_changes.py has been moved from scripts/ into pywikibot/ , so that the library package 'pywikibot' is not dependant on the 'scripts' package. https://gerrit.wikimedia.org/r/#/c/190715 The script can still be run using its new location explicitly; e.g. $ python3 pwb.py pywikibot/cosmetic_changes.py -family:wikipedia -lang:en -page:Main_Page -simulate If you have a script that was importing cosmetic changes, you will need to update your import statement to import pywikibot.cosmetic_changes . We have a change pending to re-add 'scripts/cosmetic_changes.py', so the breakage is only temporary, however import statements should be updated anyway. https://gerrit.wikimedia.org/r/#/c/205843/ Another way to reduce the impact of the move is allowing pwb to find & execute commands located in the pywikibot/ directory. https://gerrit.wikimedia.org/r/#/c/209429/ -- John Vandenberg

2 2

[Pywikipedia-l] Python MediaWiki developers meetup at Lyon hackathon
by Legoktm 06 May '15

06 May '15

Hello, A few people who work on some Python MediaWiki libraries started talking on IRC today about how much duplication there is in the ecosystem, resulting basically in wasted effort. We've set up a meeting at the Lyon hackathon so we can talk about what we're working on, and how we can collaborate together: <https://phabricator.wikimedia.org/T97950>. Also, are people interested in doing some kind of Pywikibot sprint? Looking at the attendee list (<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2015/Attendees>) I see multichill, valhallasw, jayvdb, and myself. Is anyone else planning to attend (or did I miss anyone :/)? -- Legoktm

4 4

[Pywikipedia-l] Connecting to github community
by Amir Ladsgroup 05 May '15

05 May '15

Hey, Github has a huge community of developers that collaborating with them can be beneficial for us and them but Wikimedia codes are in gerrit (and in future in phabricator) and our bug tracker is in phabrictor. sometimes It feels we are in another planet. Wikimedia has a mirror in github but we close pull requests immediately and we barely check issues raised there. Also there is a big notice in github[1], "if you want to help, do it our way". Suddenly I got an idea that if we can synchronize github activities with gerrit and phabricator, it would help us by letting others help in their own way. It made me so excited that I wrote a bot yesterday to automatically duplicates patches of pull requests in gerrit and makes a comment in the pull request stating we made a patch in gerrit. I did a test in pywikibot and it worked well [2][3]. Note that the bot doesn't create a pull request for every gerrit patch but it creates a gerrit patch for every (open) pull requests. But before I go on we need to discuss on several important aspects of this idea: 1- Is it really necessary to do this? Do you agree we need something like that? 2-I think a bot to duplicate pull requests is not the best idea since it creates them under the bot account and not under original user account. We can create a plugin for phabrictor to do that but issues like privacy would bother us. (using OAuth wouldn't be a bad idea) What do you think? What do you suggest? 3- Even if we create a plugin, still a bot to synchronize comments and code reviews is needed. I wrote my original code in a way that I can expand this to do this job too, but do you agree we need to do this? 4- We can also expand this bot to create a phabricator task for each issue that has been created (except pull requests). Is it okay? I published my code in [4]. [1]: https://github.com/wikimedia/pywikibot-core "Github mirror of "pywikibot/core" - our actual code is hosted with Gerrit (please see https://www.mediawiki.org/wiki/Developer_access for contributing" [2]: https://github.com/wikimedia/pywikibot-core/pull/5 [3]: https://gerrit.wikimedia.org/r/208906 [4]: https://github.com/Ladsgroup/sync_github_bot Best

3 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

pywikibot May 2015