fprettify

fprettify copied to clipboard

Introduce automatic splitting of long lines

6

It's a useful feature and should not be too hard to implement

pseewald

Old Fortran construct for numbered do loops are not properly "de-dented" This construct is still supported in more modern Fortran as far as I know. Example 1, the ````end```` statement...

meteokid

[Feature request] Impose whitespace formatting only on selected "classes"

1

Right now whitespace formatting can be turned on/off for everything and some options allow to add/remove whitespaces around "operators". There is no option to leave whitespace "as-is" for selected "operators"....

meteokid

There are two different testing mechanisms in place: 1) unit tests (hard-coded Fortran snippets) 2) testing by cloning Fortran projects For 1) non-default command line options can be tested, but...

pseewald

...by not overriding n or more consecutive whitespace characters. The number n (by default n=2) should be a command line option. For discussion, see #12 and #29

pseewald

[Feature request] Support formatting options as modules

1

I've seen a code which mixes `.gt.` and `>` - awful! Thought about contributing this... but stumbled across the longish `__init__.py`. It's very difficult to find out where such a...

marmistrz

Precompiler directives break indentation

1

Hi, precompiler directives such as `#ifdef` can break indentation, see for example this piece of code after reformatting with `fprettify`: ```fortran module pure function lo_frobnorm(m) result(nrm) real(flyt), dimension(:, :), intent(in)...

flokno

Swap into using pyproject.toml and setup.cfg

3

- [x] Moves the build from setup.py to setup.cfg and pyproject.toml, since setup.py will soon be deprecated. - [x] Uses setuptools_scm for automatic version incrementation. Can be inferred from git...

gnikit

docs: update shields and README format

2

Updates shields for CI and PyPi Liecense PyPi version and formatted Markdown

gnikit

Update testing framework

2

The existing `unittests` framework does not appear to be catching all errors. I propose we swap to `pytest` for mainly 2 reasons: - allows for parallel runs e.g. pytest -n...

gnikit