gerritbot added a comment.
Change 229683 **abandoned** by Xqt:
[pywikibot/core@master] [FEAT] Add basic support for signature and replace
getargspec
Reason:
in favour of fullgetargspec, see
https://gerrit.wikimedia.org/r/c/pywikibot/core/ /610271
https://gerrit.wikimedia.org/r/2
jayvdb added a comment.
In https://phabricator.wikimedia.org/T106209#1764676, @jayvdb wrote:
> Looks like the Python deprecation might be reverted.
>
> http://bugs.python.org/issue20438#msg253473
>
> resulting in
>
> http://bugs.python.org/issue25486
And it was reverted. The docs still refer t
jayvdb added a comment.
Looks like the Python deprecation might be reverted.
http://bugs.python.org/issue20438#msg253473
resulting in
http://bugs.python.org/issue25486
TASK DETAIL
https://phabricator.wikimedia.org/T106209
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel
gerritbot added a comment.
Change 225537 merged by jenkins-bot:
[FIX] Implement getargspec in tools
https://gerrit.wikimedia.org/r/225537
TASK DETAIL
https://phabricator.wikimedia.org/T106209
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: XZise, g
gerritbot added a comment.
Change 241147 merged by jenkins-bot:
[FEAT] Test Python 3.5 on Travis
https://gerrit.wikimedia.org/r/241147
TASK DETAIL
https://phabricator.wikimedia.org/T106209
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: XZise, gerr
gerritbot added a comment.
Change 241147 had a related patch set uploaded (by XZise):
[FEAT] Test Python 3.5 on Travis
https://gerrit.wikimedia.org/r/241147
TASK DETAIL
https://phabricator.wikimedia.org/T106209
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailprefere
gerritbot added a comment.
Change 229683 had a related patch set uploaded (by XZise):
[FEAT] Add basic support for signature and replace getargspec
https://gerrit.wikimedia.org/r/229683
TASK DETAIL
https://phabricator.wikimedia.org/T106209
EMAIL PREFERENCES
https://phabricator.wikimedia.or
XZise added a comment.
While the deprecation warning is more of a problem for tests (because they
might not expect it) it should be resolved as soon as possible (and sensible)
anyway. For now we could wait on `future` to implement a backport and use that
instead. We also only need few parts so