Python2 Deprecation

[half-duplex]

• setup.py manual py2 version checks
• setup.cfg version restrictions
• sopel/cli/run.py py2 version check "sopel 8.0"
• remove unnecessary __future__s
• add available __future__s
• remove str = unicodes
• remove checkstyle.sh py3_unicode check
• audit sys.version_info uses
• replace tools.iteritems(x) uses with x.items()
• search for "py2"/"python2" comments

[smoothstreams]

Does anyone work anymore ?

[RhinosF1]

Does anyone work anymore ?

On the project or in real life?

Assuming you mean on the project, this will happen when Sopel 8 comes out.

[smoothstreams]

Does anyone work anymore ?

On the project or in real life?

Assuming you mean on the project, this will happen when Sopel 8 comes out.

Yes on the project. I see, good stuff. I see like 77 open issues, and its quite sad. I hate seeing open issues on projects.
I would love to pay someone to just work on this stuff full time.

Also Jan to now, for a release is like 11-12 months. How big and complicated is this really ?

[RustyBower]

Pull requests are open :)

[Exirel]

We are working on Sopel 7.1, lots of the selected issues have a PR opened at different state of approval.

[dgw]

In this project, many (probably most) issues represent things we want, not things that are broken. It's not "sad" to have future plans. Those of us who do work on Sopel mostly do so because it's fun and there's no time pressure. We don't want it to feel like a job.

Not sure why you think there hasn't been a release since January. The last update was less than two weeks ago. We're working on a smaller feature release that won't change Python version compatibility, and then once that's done someone (really, all of us) will start on removing old Python stuff for the next major version.

[Exirel]

Reading this about future imports it looks like we'll need only generator_stop and nothing else!