Our great sponsors
-
pyupgrade
A tool (and pre-commit hook) to automatically upgrade syntax for newer versions of the language.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
norfs
Normalized filesystem. This library offers a common interface to interact with multiple filesystems, local or remote.
pyupgrade seems to do lots of useful stuff; thx for link!
I guess you need the `--py36-plus` CLI option to reproduce the desired behaviour https://github.com/asottile/pyupgrade#f-strings
thought that might result in lots of other edits to the source, this in particular seems unwarranted "foo".encode("utf-8") --> "foo".encode() because the default encoding in py3+ is utf-8. What happened to explicit is better than implicit?
Some years ago I made a script to backport a project I had developed in py3.6 on my free time but when I wanted to use it in prod at work it had to be py3.4: https://github.com/Galbar/norfs/blob/adb2a4ea885997352a1e24d...
It was a fun experience :)
Related posts
- Implementing Quality Checks In Your Git Workflow With Hooks and pre-commit
- [Tool Anouncement] github-distributed-owners - A tool for managing GitHub CODEOWNERS using OWNERS files distributed throughout your code base. Especially helpful for monorepos / multi-team repos
- How to Write Impeccably Clean Code That Will Save Your Sanity
- I’m a hack and a fraud - what are some dead giveaways that someone is self taught?
- Conversion from the f-string literals to format method in python