pywikibot

pywikibot@lists.wikimedia.org

3 participants
6830 discussions

Archivebot fails on abuse filter
by Bináris 05 Jun '18

05 Jun '18

A village pump in Hungarian Wikipedia had not been archived for a long time before we noticed it. Investigation showed that the bot had hit a warning-type abuse filter upon copying the text to archive and saving. In this case the abuse filter displays a warning and lets the user press Save again if he/she wants to do it anyway. Of course, the archivebot - did not save the page for the second time (could it?) - did not pass the problematic section and archive the remainder - did not let the owner know about the problem. It just silently failed, with logging being the only action. So what would the desired behaviour be in a similar case? Please keep in mind that archivebot is tyoically run with cron or other timing, not in interactive mode. To see the log click on https://tools.wmflabs.org/ato/log/archive.txt and ctrl f for ERROR: editpage: abusefilter-warning -- Bináris

8 15

Fwd: Forward of moderated message
by Merlijn van Deen (valhallasw) 04 Jun '18

04 Jun '18

Hi all, If you use Eventstreams in pywikibot, the message below is of interest to you. My apologies for the slow forward; this message had been kept back in a mailing list filter. Best, Merlijn ---------- Forwarded message ---------- From: Andrew Otto <otto(a)wikimedia.org> To: "A mailing list for the Analytics Team at WMF and everybody who has an interest in Wikipedia and analytics." <analytics(a)lists.wikimedia.org>, Services Mailing List <services(a)lists.wikimedia.org>, Internal discussion of WMF Research Team <research-internal(a)lists.wikimedia.org>, Research into Wikimedia content and communities <wiki-research-l(a)lists.wikimedia.org>, huggle(a)lists.wikimedia.org, pywikibot-announce(a)lists.wikimedia.org, mediawiki-api-announce(a)lists.wikimedia.org, Operations LIst < ops(a)lists.wikimedia.org> Cc: Bcc: Date: Tue, 15 May 2018 11:43:29 -0400 Subject: EventStreams offset reset - June 5 2018 Hi all! *If you are not an active user of the EventStreams service, you can ignore this email.* We’re in the process of upgrading <https://phabricator.wikimedia.org/T152015> the backend infrastructure that powers the EventStreams service. When we switch EventStreams to the new infrastructure <https://phabricator.wikimedia.org/T185225>, the ‘offsets’ AKA Last-Event-IDs will change. Connected EventStreams SSE clients will reconnect and not be able to automatically consume from the exact position in the stream where they left off. Instead, reconnecting clients will begin consuming from the latest messages in the stream. This means that connected clients will likely miss any messages that occurred during the reconnect period. Hopefully this will be a very small number of messages, as your SSE client should reconnect quickly. This switch is scheduled to happen on June 5 2018, at around 17:30 UTC. Let us know if you have any questions. Thanks! - Andrew Otto Senior Systems Engineer, WMF

1 0

Pywikibot stable release 3.0.20180603
by info＠gno.de 03 Jun '18

03 Jun '18

Hi folks, a new stable release 3.0.20180603 was deployed which is available at pypi (as side package without scripts) or from our repository with the tag "3.0.20180603". The following changes where made since 3.0.20180505: * Move main categories to top in cosmetic_changes * shell.py always imports pywikibot as default * New roundrobin_generators in tools * New BaseBot method "skip_page" to adjust page counting * Family class is made a singleton class * New rule 'startcolon' was introduced in textlib * BaseBot has new methods setup and teardown * UploadBot got a filename prefix parameter (T170123) * cosmetic_changes is able to remove empty sections (T140570) * Pywikibot is following PEP 396 versioning * pagegenerators AllpagesPageGenerator, CombinedPageGenerator, UnconnectedPageGenerator are deprecated * Some DayPageGenerator parameters has been renamed * unicodedata2, httpbin and Flask dependency was removed (T102461, T108068, T178864, T193383) * new projects where provided * Bugfixes and improvements * Documentation updates * Localisation updates (T194893) * Translation updates Also a lot of improvements for scripts where made. For older changes refer HISTORY.rst. Some methods where deprecated but are still working. You may run your private scripts in debugging mode to find out deprecated parts. Also please remember that support for Python 2.7.2 and Python 2.7.3 may be dropped in near future (see Phabricator task T191192) By the way older releases of pywikibot are still reachable through the release tag. This could be imported if older Python or Mediawiki versions are no longer supportable. Many thanks to all contributors and reviewers for their improvements and ideas, also thanks to all bot owners sharing this framework, also for bug reports and feature requests. Best xqt

1 0

Fwd: [Wikidata] First experiment of lexicographical data is out
by John Mark Vandenberg 24 May '18

24 May '18

cliff notes: Wikidata has a new entity type which is quite different from existing entity types. https://www.mediawiki.org/wiki/Extension:WikibaseLexeme/Data_Model ---------- Forwarded message ---------- From: Léa Lacroix <lea.lacroix(a)wikimedia.de> Date: Wed, May 23, 2018 at 7:33 PM Subject: [Wikidata] First experiment of lexicographical data is out To: "Discussion list for the Wikidata project." <wikidata(a)lists.wikimedia.org> Hello all, After several years discussing about it, and one year of development and discussion with the communities, the development team has now released the first version of lexicographical data support on Wikidata. Since the start of Wikidata in 2012, the multilingual knowledge base was mainly focused on concepts: Q-items are related to a thing or an idea, not to the word describing it. Starting now, Wikidata stores a new type of data: words, phrases and sentences, in many languages, described in many languages. This information will be stored in new types of entities, called Lexemes, Forms and Senses. It will allow editors to describe precisely all words in all languages, and will be reusable, just like the whole content of Wikidata, by multiple tools and queries, everything that the community creates to play with words. Lexicographical data can be reused inside and outside the Wikimedia projects, and can provide support for Wiktionary. The first release A new namespace and several new entity types have been created in order to model words and phrases. If you’re new to this project, you can learn more by looking at the documentation, briefly describing the data model and the interface. The technical structure is set, but the editors remain free to model and organize data as they prefer, with the usual open discussions and community processes that we apply on Wikidata. Some discussions about new properties to create have already started: if you want to be involved in the early stage of the project to shape it, please participate! Please note that the version that is now deployed is a first experiment, that will be continuously improved in the future. Some features are missing, some bugs may certainly occur. Here are the features that are included in the first release: Add, edit and delete Lexemes, Forms, statements, qualifiers, references Link between the different entity types (Item to Lexeme, Form to Item, etc.) Entity suggestion when adding a property or a value And the following features will not be included in the first version, but are planned for the future: Find Lexemes and Forms via Special:Search RDF support (which also means: the ability to query it with query.wikidata.org) Support for Senses Merging of Lexemes Including the data on other Wikimedia projects, such as Wiktionary How to try it? The features described above are now deployed on Wikidata.org. Here are some suggestions of what you can do to explore this new territory: If you’re not familiar with the structure of Lexemes, have a look at the documentation Look at what is already existing. Please note that Special:Search and the search bar on the top right corner of pages is not supporting Lexemes yet. We’re working on this. Create a new Lexeme with Special:NewLexeme If a property that you need is missing, you can suggest it here Discuss about how to model words and ask questions on Wikidata talk:Lexicographical data Report bugs or issues that you may encounter: either on the talk page or on Phabricator, if you’re comfortable using it (create a task, add the tag Lexicographical data, and add Lea_Lacroix_(WMDE) as a subscriber) About mass imports and tools We kindly ask you to not plan any mass import from any source for the moment. There are several reasons behind that: first of all, like mentioned above, the release is a first version and we need to observe how our system reacts to the manual edits before starting considering automatic ones. The system may not be ready for big massive imports at the beginning. Second reason is legal. Lexicographical data in Wikidata is released under CC0, and the responsibility of each editor is to make sure that the data they will add is compatible with CC0. For more information, you can have a look at the advice of WMF Legal team. Finally, we strongly encourage you to discuss with the communities before considering any import from the Wiktionaries. Wiktionary editors have been putting a lot of efforts during years to build definitions, and we should be respectful of this work, and discuss with them to find common solutions to work on lexicographical data and enjoy the use of it together. We also suggest you to wait a bit before building tools or scripts on the top of lexicographical data. The interface and its API are probably going to evolve during the next months, and the system may not be stable enough to support such tools. We will inform you as soon as it will be possible. Next steps After this first release, some improvements will be made on a very regular basis (new deployments every week). Once you tried playing with the new data, feel free to give us feedback. We’re looking especially to know what are the most important features for you to be worked on next. What did you experiment while editing lexicographical data? What went wrong or was unexpected? What bugs or troubles during the process did you encounter? What are the features that are, in your opinion, the most important? Which one should we work on next? If you’re interested in following the discussions and further announcements about lexicographical data, I encourage you to follow Wikidata:Lexicographical data and its talk page, where we will discuss about how to organize and structure data, new features to be added, ideas of tools and queries, and a lot of other things. Additional note: with this new kind of data enabled on Wikidata, we expect some new editors to get interest in it, edit Lexemes, suggest properties or ask questions. They may not be familiar with all of our community processes and our ways to organize content. They will need help and support as well as links to useful resources to understand how the Wikidata community works. I hope that we will all be kind and patient, both with other editors and with the software that may not work exactly as we want it to at the beginning :) Thanks to the people who tested the model and the interface before the release, who showed support and curiosity about lexicographical data on Wikidata! If you have any question or idea, feel free to write on Wikidata talk:Lexicographical data or contact me. -- Léa Lacroix Project Manager Community Communication for Wikidata Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207. _______________________________________________ Wikidata mailing list Wikidata(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata -- John Vandenberg

1 1

pagefromfile.py
by Etienne Ruedin 30 Apr '18

30 Apr '18

3 3

Dropping support for python 2.7.2 and 2.7.3
by Dalba 08 Apr '18

08 Apr '18

Hi everyone, This is just a quick announcement to let you know that Pywikibot is going to drop support for Python 2.7.2 and 2.7.3. See T191192[1] for more info. [1]: https://phabricator.wikimedia.org/T191192

1 0

archivebot.py: make the script listen to templates to trigger an archive run
by MarcoAurelio 07 Apr '18

07 Apr '18

Hi, This is a request to have a look if at all possible at < https://phabricator.wikimedia.org/T72249>. To increase the usability of the script, it would be good if the bot could instead or in adittion to the age param, listen to on-wiki templates that signals that the thread can be archived. I'm thinking on noticeboards where threads are marked as {{done}}/{{not done}} where this could be really useful. Could the same be done for archivebot.py? Best regards, M.

1 0

gerrit settings
by info＠gno.de 23 Mar '18

23 Mar '18

Hi folks, was there any setting changes for gerrit few weeks ago. I feel since few weeks a lot of merge conflicts are indicated at gerrit but when rebasing there aren't any conflicts. Best xqt

2 2

Ordered list of disambiguation pages
by Bináris 27 Feb '18

27 Feb '18

Hi folks, a long time ago in a very near galaxy I worked a lot with disambiguation pages. Those times there was some tool to list them ordered by number of references, so as we knew which disambiguation page to work on. The tool was not perfect for us for multiple reasons, and we don't find it any more <https://hu.wikipedia.org/w/index.php?title=Wikip%C3%A9dia:Botgazd%C3%A1k_%C…>. So I decided to write a script, here it is: https://hu.wikipedia.org/wiki/Szerkeszt%C5%91:BinBot/disambcounter.py Feel free to use it. One idea is that number of references is not useful in itself. So number of referring templates will be counted separately, because in many cases the number of references may be drastically decreased by manual edit of a few templates (navboxes, infoboxes, userboxes etc.). In Hungarian Wikipedia botless users helped to correct a lot of bad references caused by these templates. After this we get a clearer number of references to be corrected by bot. The other point of view was that many disambiguation pages are just disturbing, and we don't want to work on them, so we can exclude them from listing. In huwiki these were the disambiguation pages of bus/metro/tram lines which crosslink to each other, generating 110 thousend bad references, and they are about 3-400. They flooded the beginning of the list, but now they don't flood any more. You may also set the namespaces, where to count. As we often don't correct references in talk namespaces, we don't want to count them. Now we have a list that is useful to choose the subejct of botwork. -- Bináris

1 0

Mass hiding
by Bináris 25 Feb '18

25 Feb '18

We have a long term vandal who finds his pleasure in decorating user pages with obscene pictures, and users often want them to be hiden from page history. Can Pywikibot do this for me? I would give the user name of the vandal, and the bot would mass hide the contents (or contents, comment, user name) of the versions. Of course, with admin rigths. -- Bináris

4 5

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

pywikibot