Comments (2)
For the first one, see if SPLIT_COMPLEX_COMPREHENSION might help. (I think it will still split after the k: v
part though.) As for the second example, you might try adjusting SPLIT_PENALTY_AFTER_OPENING_BRACKET. However, it may have other side effects.
from yapf.
Thanks for the suggestions!
Example 1
With split_complex_comprehension = true
, it generates:
donated = {
k: v
for k, v in very_long_dict_name.items()
if k not in self.copy_keys}
I think this looks better. Not ideal, but I assume having a line balancing heuristic (i.e. avoiding very short lines) might be too tricky to consider?
Example 2
I tried different values of split_penalty_after_opening_bracket
(default is 300, I tried 1, 100, 1000, 10000). None of those changed the generated output. I think it's probably because both breakpoints (the first one YAPF chooses and the second one that would be desired) are after an opening brackets, so the penalty would be the same either way?
Perhaps the current penalty system would already make it feasible to achieve the desired balancing behavior by adding a small penalty for based on line shortness (i.e. 79 minus line length, summed over all lines in the formatted expression)?
from yapf.
Related Issues (20)
- [Question]: Why removing the verify module, how can this be substituted ? HOT 3
- `SPLIT_ALL[_TOP_LEVEL]_COMMA_SEPARATED_VALUES` breaks on tuple unpacking HOT 1
- Grammar caching causes EOFError and race condition when used as pre-commit hook HOT 4
- Unecessary line break and incorrect indentation? HOT 1
- How to avoid line break before comparison operator? HOT 1
- How to keep as many function arguments on each same line as possible? HOT 1
- Incorrect dict indentation inside nested context? HOT 5
- Support 3.12 feature: PEP 695 Type Parameter Syntax
- May I ask how to automatically add a space after "#" when using yapf? I haven't found such configuration. Thank you. HOT 2
- Format long list of lists HOT 1
- SPACE_INSIDE_BRACKETS does not work for closing curly bracket HOT 1
- Format error when async method after comment
- Crash when parsing function with unexpected await
- yapf: input filenames did not match any python files - VS code, formatting doesn't work HOT 1
- `NO_SPACES_AROUND_SELECTED_BINARY_OPERATORS` crashes yapf when configured with `%`
- Broken parser: `case` is a valid variable name
- [Bug] Some space out of range strip when using `-l` argument. HOT 2
- The NO_SPACES_AROUND_SELECTED_BINARY_OPERATORS format option doesn't work correctly.
- Remove the blank line between docstring and function head
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from yapf.