jayvdb created this task.
jayvdb claimed this task.
jayvdb added a subscriber: jayvdb.
jayvdb added a project: Pywikibot-tests.
TASK DESCRIPTION
aspects.py provides similar functionality to the package testscenarios. https://pypi.python.org/pypi/testscenarios
Features of aspects that are missing should be added to testscenarios, so that we could adopt it by essentially renaming TestCase.sites to TestCase,scenarios , plus any parts of aspects that may not be able to be easily generalised.
TASK DETAIL
https://phabricator.wikimedia.org/T85899
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>.
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: jayvdb
Cc: Aklapper, jayvdb, pywikipedia-bugs
jayvdb added a comment.
We can know what each Debian version contains, and I think we should at least determine this for all the major distributions of MediaWiki so that they are properly supported.
wheezy : http://anonscm.debian.org/viewvc/pkg-mediawiki/mediawiki/branches/wheezy/de…
trunk/jessie: http://anonscm.debian.org/viewvc/pkg-mediawiki/mediawiki/trunk/debian/patch…
I dont see any patch which would cause the API to work differently from the released version for pywikibot. A few might make the server work correctly, where the released version doesnt work, however they are not cases where pywikibot does not currently try to workaround a bug in the server.
trunk has two extra patches
allow_pdf.patch
fix_variable_use.patch
Debian at least identifies itself. Fedora also packages MediaWiki, and it doesnt appear that it identifies itself, so we cant know whether its API has backports which cause it to operate differently.
However we should fallback on a sensible value, with a UserWarning to indicate that it isnt a fully supported or understood version. i.e. anything starting with 1.19.20 should be treated as 1.19.20 .
TASK DETAIL
https://phabricator.wikimedia.org/T96813
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>.
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: jayvdb
Cc: XZise, jayvdb, Aklapper, pywikipedia-bugs
jayvdb created this task.
jayvdb added a subscriber: jayvdb.
jayvdb added a project: pywikibot-core.
Restricted Application added subscribers: Aklapper, pywikipedia-bugs.
TASK DESCRIPTION
https://github.com/GreenSteam/pep257/pull/107 has been merged, but is not yet released on https://pypi.python.org/pypi/pep257
When it is released, and if we can force all our tools to use the new released version...
1. we can remove non-informative docstrings from our .setters ,
2. we should update the property getter docstring to be less 'get' specific.
tools.LazyRegex.flags and tools.LazyRegex.raw are clear examples of a docstring on .setter which is unnecessary
Page.text is a case where we shouldnt change anything, as the have very important information which is different.
I think Bot.current_page and Bot.site could be improved by merging the docstrings.
api's Request.mime setter docstring could be merged into the getter docstring, but I'm not 100% sure about that one.
threadedhttp 's .data look like it shouldnt be changed.
TASK DETAIL
https://phabricator.wikimedia.org/T97382
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>.
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: jayvdb
Cc: pywikipedia-bugs, jayvdb, Aklapper
Ladsgroup lowered the priority of this task from "Unbreak Now!" to "Low".
Ladsgroup set Security to None.
TASK DETAIL
https://phabricator.wikimedia.org/T70613
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>.
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Ladsgroup
Cc: Ladsgroup, gerritbot, jayvdb, Ricordisamoa, Mpaa, pywikipedia-bugs
Ladsgroup added a subscriber: Ladsgroup.
Ladsgroup added a comment.
Since change Ic55cd1a3 is merged, it won't break any test but it still is a valid bug so I refrain from closing this bug but I reduce priority.
TASK DETAIL
https://phabricator.wikimedia.org/T70613
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>.
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Ladsgroup
Cc: Ladsgroup, gerritbot, jayvdb, Ricordisamoa, Mpaa, pywikipedia-bugs