python 2 compatibility

[cgeering]

An f-string was added in #6 here, which is not valid py2; results in a SyntaxError when trying to import retrying in a py2 environment:

Seems like 1.3.5 is supposed to be py3 only, but pip install still let's you install 1.3.5 in a py2 environment.

[groodt]

Yes, I don't have any plans to support PY2.

I should add python_requires to prevent installation in older environments.

[hhgabelgaard]

How about Python 3.5 support?
The f strings breaks that

[groodt]

How about Python 3.5 support?
The f strings breaks that

Good point.

I think what I'm going to do is:

1. Fix things so that it supports Python 2 again
2. Release 1.3.6
3. Yank 1.3.5
4. Create a release at 1.4.0 that is python_requires='>=3.6'

[groodt]

v1.3.6 https://pypi.org/project/retrying/1.3.6/
v1.4.0 https://pypi.org/project/retrying/1.4.0/

[hhgabelgaard]

Thanks
Good solution

[shadchin]

Alas, Python 2 is still broken:

contrib/python/retrying/py2/tests/test_retrying.py:336: in test_with_stop_on_exception
    _retryable_test_with_stop(NoIOErrorAfterCount(5))
contrib/python/retrying/py2/retrying.py:55: in wrapped_f
    return Retrying(*dargs, **dkw).call(f, *args, **kw)
contrib/python/retrying/py2/retrying.py:275: in call
    raise attempt.get()
contrib/python/retrying/py2/retrying.py:312: in get
    raise exc.with_traceback(tb)
E   AttributeError: 'exceptions.IOError' object has no attribute 'with_traceback'

[groodt]

I'll try look into it and release 1.3.7 sometime this weekend

Or contributions welcome!

[groodt]

@shadchin Please try pip install retrying==1.3.7

[shadchin]

Everything is ok now, thanks