Upgrading wolframalpha package to 3.0 broke this module on my instance (Py2.7).
[01:32:15] <~dgw> ;wa dgw
[01:32:23] <&Kaede> TypeError: object of type 'itertools.imap' has no len()
(file "/usr/local/lib/python2.7/dist-packages/sopel_modules/wolfram
/wolfram.py", line 52, in wa_query)
Prior to this update it was working fine. Reinstalling wolframalpha 2.4 and restarting the bot fixed it.
There will be two steps to fixing this issue, and a third step for the future once enough time has passed:
[x] Update requirements.txt to request wolframalpha>=2.0,<3.0 (done in #6)
[x] Rewrite code to handle both 2.0 and 3.0; require wolframalpha>=2.0,<4.0 (done shortly — 12/21) (done; "shortly" is relative, see discussion in #11 — May 10, 2017)
[ ] [Future] Drop support for 2.0 and require wolframalpha>=3.0,<4.0 Not needed; both versions can be supported in parallel with minimal code smell
The most pressing issue right now is preventing users from upgrading to wolframalpha 3.0, so a new release with the first requirements update will be pushed soon was pushed shortly after posting of this issue.
Upgrading
wolframalpha
package to 3.0 broke this module on my instance (Py2.7).Prior to this update it was working fine. Reinstalling
wolframalpha
2.4 and restarting the bot fixed it.There will be two steps to fixing this issue,
and a third step for the future once enough time has passed:requirements.txt
to requestwolframalpha>=2.0,<3.0
(done in #6)wolframalpha>=2.0,<4.0
(done shortly — 12/21) (done; "shortly" is relative, see discussion in #11 — May 10, 2017)[Future] Drop support for 2.0 and requireNot needed; both versions can be supported in parallel with minimal code smellwolframalpha>=3.0,<4.0
The most pressing issue right now is preventing users from upgrading to
wolframalpha
3.0, so a new release with the first requirements updatewill be pushed soonwas pushed shortly after posting of this issue.