Remove support for python 2.7 and 3.4

[non-Jedi]

We had a long conversation in
#matrix-python-sdk:matrix.org
a couple weeks ago about the benefit of only supporting versions of python that
support asyncio and came to the conclusion that unless there are major projects
using python 2 or 3.4 that need this sdk, it would be beneficial to the project
to move to being 3.5+ only.

I'd like it if everyone who has a project using this sdk could comment here
briefly saying whether a switch to 3.5+ only would negatively affect their
project or not. It would be great if you could comment regardless of whether it
would or would not affect you.

[non-Jedi]

I'll start: none of my projects making use of this sdk would be negatively affected by switching to 3.5+ only. And several would benefit if this sdk were to have a async api.

[jfrederickson]

I maintain a Matrix plugin for a chatbot that doesn't yet have Python 3 support, so this would negatively affect me.

(Granted, this may be more incentive for the primary developer of that chatbot to switch... :P)

[johnpwarren]

No problems with that here (to be fair I just started a project).

[eternal-flame-AD]

Not a problem for me. My project was built and tested under 3.6+

[turt2live]

Several of my projects (personal and for other organizations) use the python SDK, and are unlikely to switch to python 3 any time soon. That being said, they can keep using the pinned version of the SDK without issue, therefore they aren't greatly affected (until I get the time to update them).

[Cadair]

All of my projects are already 3.5+ and having async/await support would be a massive usability improvement for me.

[Zil0]

No problem here and I think it is the right way to go.

[mvgorcum]

No problem for me.

[jahschwa]

re: @jfrederickson I plan to move the mentioned project to python3 and this would be a good motivator
jahschwa/sibyl#35

[4nd3r]

just do it

[slipeer]

In our company, internal projects use only 2.7. Therefore, we will have to maintain our fork.
I do not quite understand why you can not leave this SDK and make 3.5+ fork, for example matrix-python-async-sdk.
For many simple tasks, asynchrony is an unnecessary complication.

[Cadair]

I hope the impression is not given that the plan is to make everything async. My understanding is that it would be optional parts of the SDK.

Also, there are many other advantages to being 3+ only other than the async/await syntax.

[Croydon]

@slipeer I'm curious, does your company already have a migration plan towards Python 3?

http://pythonclock.org

[joeky888]

It would be great if this SDK supports micropython,

micropython uses async keyword.

See also https://github.com/micropython/micropython

MicroPython implements the entire Python 3.4 syntax (including exceptions, with, yield from, etc., and additionally async/await keywords from Python 3.5)

[andrevmatos]

Here at https://github.com/raiden-network/raiden we are on python 3.6+, so we wouldn't be affected by the switch, although we use a gevent-based wrapper and don't plan to switch to async/await (of course, we wouldn't mind it being optional, and plan to ready and contribute back upstream our optional gevent support)

[non-Jedi]

@joeky888 just now seeing this. Please feel free to create an issue to document this feature request or a PR. I'm not entirely convinced that the sdk won't already work on micropython, so it might just be a matter of adding something to the CI/test config to make sure tests are run against micropython as well as cpython.

[joeky888]

@non-Jedi

Sure, here it is.

#287

[cy8aer]

uuuh, just trying to build a client for SailfishOS (python 3.4)

[ptman]

What's the sailfishOS devs take on providing python3 with asyncio?

[cy8aer]

Just a naive question: is this needed?

,---
| Sailfish OS 3.0.1.11 (Sipoonkorpi)
'---
[nemo@wilf ~]$ python3
Python 3.4.3 (default, Aug 10 2018, 07:11:41) 
[GCC 4.8.3 `20140401` (Mer 4.8.3-1)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import asyncio
>>> 

It looks like it is in python since 3.4alpha4 and in __init__.py 3.3 is mentioned too (there selectors module is missing).