pyupgrade
yapf
pyupgrade | yapf | |
---|---|---|
23 | 21 | |
3,330 | 13,655 | |
- | 0.3% | |
7.9 | 8.0 | |
8 days ago | 8 days ago | |
Python | Python | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pyupgrade
-
A Tale of Two Kitchens - Hypermodernizing Your Python Code Base
pyupgrade and flynt are examples of tools that modify your code base from earlier python versions into the newest python syntax, rewriting all string formats into f-strings and similar things.
-
Conversion from the f-string literals to format method in python
pyupgrade - A tool (and pre-commit hook) to automatically upgrade syntax for newer versions of the language.
-
Which is your favourite or go-to YouTube channel for being up-to-date on Python?
He made yesqa and pyupgrade (among others), and also works on flake8. His main job is for https://sentry.io/.
-
Reasons Python Sucks
That's a decade to make a 30 second change. Add something like https://github.com/asottile/pyupgrade to your pre-commit hooks and you won't even need 25 of those seconds.
-
Is there a way to convert python 2 to 3 without finding every single line and fix it?
There is also pyupgrade: https://github.com/asottile/pyupgrade
-
I've recently learned about better support for type-hinting. What other 'best practices' have been introduced in Python 3.10 or newer?
pyupgrade is a useful tool that can help you find some of these things.
-
Flake8 took down the gitlab repository in favor of github
and last a little plug or two -- because I do this all for free and despite millions benefiting I receive zero proportional benefit from the maintenance work I put in -- consider sponsoring or maybe check out pre-commit.ci which would have automatically fixed this problem for you a year and a half ago
-
Django upgrade services?
Running https://github.com/adamchainz/django-upgrade with https://github.com/asottile/pyupgrade recursively will give an idea about how much work is there on Django side. Still, there may have dependency on third party libraries (both django+python). Another thing to consider is which role Django performing here, serving APIs or html views. As good test coverage is already there, you are on lucky side.
-
It’s Time to Say Goodbye to These Obsolete Python Libraries
Such goodness here and even points to an interesting project I’d never heard of for automated “de-deprecation”
https://github.com/asottile/pyupgrade
-
Is there a linter which would suggest using elif rather than an else in an if clause?
I do would like to recommend pyupgrade. Just pip install as expected and then run pyupgrade --py310-plus to drag your code kicking and screaming into $CURRENT_YEAR. Or at least into whatever version you're using :)
yapf
-
Enhance Your Project Quality with These Top Python Libraries
YAPF (Yet Another Python Formatter): YAPF takes a different approach in that it’s based off of ‘clang-format’, a popular formatter for C++ code. YAPF reformats Python code so that it conforms to the style guide and looks good.
-
Why is Prettier rock solid?
I think I agree about the testing and labor of complicated translation rules.
But it doesn't appear that almost every pretty printer uses the Wadler pretty printing paper. It seems like MOST of them don't?
e.g. clang-format is one of the biggest and best, and it has a model that includes "unwrapped lines", a "layouter", a line break cost function, exhaustive search with memoization, and Dijikstra's algorithm:
https://llvm.org/devmtg/2013-04/jasper-slides.pdf
The YAPF Python formatter is based on this same algorithm - https://github.com/google/yapf
The Dart formatter used a model of "chunks, rules, and spans"
https://journal.stuffwithstuff.com/2015/09/08/the-hardest-pr...
It almost seems like there are 2 camps -- the functional algorithms for functional/expression-based languages, and other algorithms for more statement-based languages.
Though I guess Prettier/JavaScript falls on the functional side.
I just ran across this survey on lobste.rs and it seems to cover the functional pretty printing languages influenced by Wadler, but functional style, but not the other kind of formatter ("Google" formatters perhaps)
https://arxiv.org/pdf/2310.01530.pdf
-
A Tale of Two Kitchens - Hypermodernizing Your Python Code Base
To get all your code into a consistent format the next step is to run a formatter. I recommend black, the well-known uncompromising code formatter, which is the most popular choice. Alternatives to black are autoflake, prettier and yapf, if you do not agree with blacks constraints.
-
Front page news headline scraping data engineering project
Use yapf to format code -> https://github.com/google/yapf
-
Confused by Google's docstring "Attributes" section.
Google is surprisingly rigorous when it comes to code formatting. I have been a software engineer at Amazon and it was nothing like what the book says happens at Google. So the conventions you see for python docstring formatting are primarily designed to integrate with Google's internal tooling. By using docstrings following the Google conventions, you will ultimately end up with automated documentation and other fancy automated things (like type checking which they did in the docstring before there were type hints). Also notably, Google has an open source python formatting tool that they use internally called YAPF (which stands for "Yet Another Python Formatter". So if you really want to go all-in on Google python style, grab that, too.
- Alternate python spacing.
-
Not sure if this is the worst or most genius indentation I've seen
https://github.com/google/yapf has configs, do ctrl+f SPLIT_COMPLEX_COMPREHENSION in the readme
- Google Python Style Guide
-
Enable hyphenation only for code blocks
Only as recommendation: If the lines of the source code (here: you C code you aim to document) are kept short, in manageable bytes (similar to entries parser.add_argument in Clark's "Tiny Python Projects", example seldomly pass beyond the frequently recommended threshold of 80 characters/line), reporting with listings becomes easier (equally, the reading of the difference logs/views by git and vimdiff), than with lines of say 120 characters per line. Though we no longer are constrained to 80 characters per line by terminals/screens and punch cards (when Fortran still was FORTRAN), this is a reason e.g., yapf for Python allows you to choose between 4 spaces/indentation (PEP8 style), or 2 spaces/indentation (Google style).
-
3 popular Python style guides that will help your team write better code
There is also a formatter for Python files called yapf that your team can use to avoid arguing over formatting conventions. Plus, Google also provides a settings file for Vim, noting that the default settings should be enough if you're using Emacs.
What are some alternatives?
pre-commit-hooks - Some out-of-the-box hooks for pre-commit
black - The uncompromising Python code formatter
flynt - A tool to automatically convert old string literal formatting to f-strings
isort - A Python utility / library to sort imports.
flake8
pep585-upgrade - Pre-commit hook for upgrading type hints
autopep8 - A tool that automatically formats Python code to conform to the PEP 8 style guide.
autoflake - Removes unused imports and unused variables as reported by pyflakes
awesome-python-typing - Collection of awesome Python types, stubs, plugins, and tools to work with them.
black - The uncompromising Python code formatter [Moved to: https://github.com/psf/black]
pyright - Static Type Checker for Python