New release breaks on python 3.5

[pyo3]

New release breaks on python 3.5

[mtreinish]

I had a similar issue on some packages I maintained when I dropped 2.7 support. The only way I can think of to do this gracefully is to push out a 0.11.5 that removes the fstring usage and works with 3.5 so pip will prefer that over 0.11.4. Then push out 0.11.6 which sets the python_requires=">=3.6" in the package metadata.

Or the alternative is to just assume anyone still supporting python 3.5 will set a cap like I did in Qiskit/rustworkx#190 and push out a 0.11.5 with python_requires=">=3.6". Although looking at: https://pypistats.org/packages/setuptools-rust I'm kinda surprised how many downloads are still on python 3.5.

[davidhewitt]

Yikes, thanks for reporting. I think the cleanest way is probably the two releases as you suggest. I'll take a look at this tonight.

[mtreinish]

I pushed up a PR #86 that removes the fstring usage, I briefly tested a build locally and it worked on 3.5 for me locally.