python-twitter has stopped working after Twitter upstream removed an
endpoint it was querying. Switch to the better maintained tweepy,
which is basically the same.
tweepy doesn't automatically split tweets, so implement that. Split
tweets will now be in reply to each other, which is a feature.
Change-Id: Id40af0e314ce8a6cb542f6138f5deaa8a587b260
Our servers have, in the two years since we last needed to change
statusbot, switched to installing packages with pip for Python 3.x
instead of 2.7. Instead of figuring out how to unfurl that, just
roll forward and embrace the glorious pastfuture.
Update the simplemediawiki version to pull in a prerelease, since
that's the only way to get a version which supports Py3K.
Change-Id: I24100ad2e9d87e20b7fd9ce90399346846529985
Identify through SASL using the convenient ib3 mixins, and
get rid of a bunch of special-case code in the process.
This helps when dealing with channels set to require identified
users, as otherwise channel joins will race NickServ's processing of
the identify message and some channels will end up not serviced by
the bot (an alternative would be to delay joining channels until the
identify success is confirmed, but the implementation for that looks
like it would be at least as complex).
Note this also effectively drops non-SSL IRC support. Given
passwords are sent over this connection, I don't see it as a loss.
Change-Id: I0aa15d81f0158fcf2b74825cdb3968d62356fa1d
Co-Authored-By: Thierry Carrez <thierry@openstack.org>
Depends-On: https://review.openstack.org/599061
The latest release of python-twitter adds support for 280 character
tweets which will make the status updates much cleaner looking
in timelines.
Change-Id: I24b0e45ac69e65a803b4392e54327a0c1f21351f
This fixes some issues with pyflakes:
AttributeError: 'ClassDef' object has no attribute 'keywords'
Add requirements for six>=1.7.0
This is for jaraco.collections but something is draging in an older version.
Change-Id: I4733fb4be29463ae6dbfef1ecfb80b0aa8b45e5c
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Similar to replicating to github for the convenience of our
developer community, sending statuses ALSO to twitter seems
like a potentially low-impact way to communicate status on
an additional channel.
Change-Id: Ib4bdbb335e4bc12d75d5f0ec2a1b95c8a6b2e7d5
Ian Wienand