Use f-strings instead of .format about nats.py HOT 9 CLOSED

Yep no rush, totally a cosmetic update.

from nats.py.

I'd like to tackle this @wallyqs just wanted to call it out in issues as to get your thoughts and to not duplicate effort.

from nats.py.

@charliestrawn this sounds good to me! I was thinking of cutting a release for 0.9.0 today, would you like me to wait or can we include this in v0.9.1 maybe?

from nats.py.

Actually had already uploaded asyncio-nats-client 0.9.0 so we can add this to the next release. Thanks Charlie.

from nats.py.

Hello, if you still want to do this change. I could get a jump on it.

from nats.py.

@Bernolt that would be great, thanks!

from nats.py.

Actually, I ran a pyupgrade to get rid of them, it additinally got rid of:

• old-style class definition

class C(object): pass     # class C: pass
class C(B, object): pass  # class C(B): pass

• super calls

class C(Base):
    def f(self):
        super(C, self).f()   # super().f()

and of course switched f-strings instead of .format.

Do you mind if I keep those changes or you would prefer to stick to the f-string change only?

Also, f-string change will break compatibily with version of python below 3.6. Are you ok with that?

from nats.py.

Thanks for the PR, I think it is fine to allow for 3.6 as the minimum version.

from nats.py.

Yeah I'm pretty sure we are already using some things that bind us to 3.6 or later. Closing as addressed in #152

from nats.py.