[GNC-dev] Python code formatter - black
jralls at ceridwen.us
Tue Jul 7 11:06:25 EDT 2020
Is there a reason you don't want to use PyLint?
> On Jul 6, 2020, at 10:22 PM, c.holtermann at gmx.de wrote:
> I have used it as is without config. I'll have a look which options
> are for configuration and if what you have in mind is configurable.
> Christoph Holtermann
> Am 2020-07-07 05:21, schrieb John Ralls:
>> It's mostly OK, but some of the vertical space changes are excessive
>> in particular gncinvoice_jinja.py line 213 and latex_invoices.py line
>> I don't much care for the way it handled gncinvoice_jinja.py line 207
>> either: I'd prefer to move the comment above the line and if it's
>> still too wide drop the whole call, like so:
>> # something like 2004-11-01
>> filename_date =
>> But that's probably too much to ask of an automated tool.
>> John Ralls
>>> On Jul 6, 2020, at 1:10 PM, c.holtermann at gmx.de wrote:
>>> Hello folks,
>>> I'd like to use a code formatter on the python bindings. I tried black
>>>  and liked what I saw. Would you be ok with reformatting the whole
>>> python bindings with it?
>>> I used it on two example scripts:
>>> Christoph Holtermann
>>>  https://github.com/psf/black
>>> gnucash-devel mailing list
>>> gnucash-devel at gnucash.org
More information about the gnucash-devel