As the last release of Python 2 is finally out, the July release of
Pywikibot is going to be the **last release that supports Python 2**.
Support of Python 3.4 and MediaWiki older than 1.19 is also going to be
dropped. After this release, Pywikibot is not going to receive any further
patches and bug fixes related to those Python and MediaWiki versions.
Functions and other stuff specific to Python 3.4, Python 2.x or MediaWiki
older than 1.19 will be removed.
For your convenience, this release is marked with a "python2"
git tag and it is also the last 3.0.x release. In case you really need it,
the Pywikibot team created /shared/pywikibot/core_python2 repository in
Toolforge and a python2-pywikibot package in software repositories of some
operating systems.
The Pywikibot team strongly recommends that you migrate your scripts from
Python 2 to Python 3. The migration steps were described in the previous
message, which can be found here:
https://lists.wikimedia.org/pipermail/pywikibot/2020-January/009976.html
Detailed plan of Python 2 deprecation with dates is described here:
https://www.mediawiki.org/wiki/Manual:Pywikibot/Compatibility
If you encounter any problems with the migration, you can always ask us
here: https://phabricator.wikimedia.org/T242120
Best regards,
Pywikibot team
Together with the last Python 2 release from April, 2020, Pywikibot team
will release the **last version that supports Python 2**. We created a
**python2" tag** marking the version, so you can continue running your
Python 2 scripts using this tag, if you really need to.
After that version, Pywikibot is not going to receive any further patches
and bug fixes related to Python 2. Its code is going to be cleaned from
Python 2 specific functions, patches, deprecations and other stuff, so make
sure you'll use this tag if you still want to run Pywikibot using Python 2.
Pywikibot team strongly recommends to migrate your scripts to Python 3. To
make it happen, you can use Python 2to3 script installed by default with
Python 2.6+, see https://docs.python.org/2/library/2to3.html. You can also
just try to run your script using Python 3 (the "-simulate" parameter could
be handy) and fix all the issues. If you encounter problems with the
migration, you can always ask us here:
https://phabricator.wikimedia.org/T242120
Best regards,
Martin Urbanec and Dvorapa
(Apologies if you receive this message duplicate)
Dear bot operators and pywikibot users:
I hope that this email find you well.
I'd like to announce that the branch 2.0 of pywikibot-core is being
proposed for deprecation and deletion. The reasons for this are that
2.0 is years ahead from our master branch, and has since no longer
been mantained.
If any of you still use this branch or depends on it, the pywikibot
mantainers advice you to switch to the currently mantained master
branch of pywikibot which can be located at
<https://phabricator.wikimedia.org/diffusion/PWBC/>.
It has been proposed that the deprecation and deletion of the 2.0
branch happen in 2 weeks from the sending of this email. If you'd like
to flag any issues, problems or opposition to this please comment on
<https://phabricator.wikimedia.org/T169734>.
Best regards,
- M. A.
Hi everyone!
Wikimedia is releasing a new service today: EventStreams
<https://wikitech.wikimedia.org/wiki/EventStreams>. This service allows us
to publish arbitrary streams of JSON event data to the public. Initially,
the only stream available will be good ol’ RecentChanges
<https://www.mediawiki.org/wiki/Manual:RCFeed>. This event stream overlaps
functionality already provided by irc.wikimedia.org and RCStream
<https://wikitech.wikimedia.org/wiki/RCStream>. However, this new service
has advantages over these (now deprecated) services.
1.
We can expose more than just RecentChanges.
2.
Events are delivered over streaming HTTP (chunked transfer) instead of
IRC or socket.io. This requires less client side code and fewer special
routing cases on the server side.
3.
Streams can be resumed from the past. By using EventSource, a
disconnected client will automatically resume the stream from where it left
off, as long as it resumes within one week. In the future, we would like
to allow users to specify historical timestamps from which they would like
to begin consuming, if this proves safe and tractable.
I did say deprecated! Okay okay, we may never be able to fully deprecate
irc.wikimedia.org. It’s used by too many (probably sentient by now) bots
out there. We do plan to obsolete RCStream, and to turn it off in a
reasonable amount of time. The deadline iiiiiis July 7th, 2017. All
services that rely on RCStream should migrate to the HTTP based
EventStreams service by this date. We are committed to assisting you in
this transition, so let us know how we can help.
Unfortunately, unlike RCStream, EventStreams does not have server side
event filtering (e.g. by wiki) quite yet. How and if this should be done
is still under discussion <https://phabricator.wikimedia.org/T152731>.
The RecentChanges data you are used to remains the same, and is available
at https://stream.wikimedia.org/v2/stream/recentchange. However, we may
have something different for you, if you find it useful. We have been
internally producing new Mediawiki specific events
<https://github.com/wikimedia/mediawiki-event-schemas/tree/master/jsonschema…>
for a while now, and could expose these via EventStreams as well.
Take a look at these events, and tell us what you think. Would you find
them useful? How would you like to subscribe to them? Individually as
separate streams, or would you like to be able to compose multiple event
types into a single stream via an API? These things are all possible.
I asked for a lot of feedback in the above paragraphs. Let’s try and
centralize this discussion over on the mediawiki.org EventStreams talk page
<https://www.mediawiki.org/wiki/Talk:EventStreams>. In summary, the
questions are:
-
What RCStream clients do you maintain, and how can we help you migrate
to EventStreams? <https://www.mediawiki.org/wiki/Topic:Tkjkee2j684hkwc9>
-
Is server side filtering, by wiki or arbitrary event field, useful to
you? <https://www.mediawiki.org/wiki/Topic:Tkjkabtyakpm967t>
-
Would you like to consume streams other than RecentChanges?
<https://www.mediawiki.org/wiki/Topic:Tkjk4ezxb4u01a61> (Currently
available events are described here
<https://github.com/wikimedia/mediawiki-event-schemas/tree/master/jsonschema…>
.)
Thanks!
- Andrew Otto
Hi everyone,
A change was deployed which changed the behavior of the login api. As a
result Pywikibot bots can't login to any of the WMF wiki's. I asked Brad
to undo his change so bots can login again. This problem is being
tracked in https://phabricator.wikimedia.org/T142155 .
Maarten
Hello,
Since Wikidata is awesome and now replaced all of Template:Link FA and its
similar templates with badges. We decided
<https://phabricator.wikimedia.org/T109210> to archive featured.py and keep
it for historical reasons. The script is moved to "archive" folder in
scripts directory. You still can run it using "python pwb.py featured" and
some tests will be ran over the script but it won't be maintained anymore.
It would be good to write a new script to add badges to Wikidata Even
though it's a easy task that humans should do ;). This change
<https://gerrit.wikimedia.org/r/267410> is merged in master branch but
we'll port it to 2.0 branch soon so if you still use this script in your
wiki please note this deprecation.
Also it's the first script to be archived, I think we can archive a lot
more now.
Best
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
Hello,
Please join us on the next Wikimedia Bugday:
20:00 Thursday, October 24, 2013 - Sunday, October 27 22:00 UTC[1]
in #pywikipediabot on Freenode IRC [2]
We will be triaging bug reports pywikibot [3]. Pywikibot recently
moved its code repository from SVN to Git and its bugtracker from
SourceForge to Wikimedia Bugzilla. Now many older tickets need
retesting and cleanup (around 700 bugs). We will be focusing on
retesting, and we will comment on bug reports that need status
updates, and have a good time working together on improving Pywikibot!
Everyone is welcome to join, and no technical knowledge needed! It's
an easy way to get involved in the community or to give something
back.
This even is part of a weekly QA activity [4], so we encourage you to
triage throughout the week and record your activity on the bug day
etherpad [5].
This information and more can be found here:
https://www.mediawiki.org/wiki/Bug_management/Triage/20131024
For more information on triaging in general, check out
https://www.mediawiki.org/wiki/Bug_management/Triage
I look forward to seeing you there.
Amir on behalf of Pywikibot developers
[1] Timezone converter: http://www.timeanddate.com/worldclock/converter.html
[2] See http://meta.wikimedia.org/wiki/IRC for more info on IRC chat
[3] https://www.mediawiki.org/wiki/Bug_management/Triage/20131024
[4] https://www.mediawiki.org/wiki/QA/Weekly_goals
[5] http://etherpad.wmflabs.org/pad/p/BugTriage
--
Amir