You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the context of fixing current issues within basemap, one easy step is to use static analysis tools, since they can catch the most evident problems.
I open this issue as a reminder to enable flake8 in the development workflow; flake8 will catch the most evident code mistakes, and it will also give advice on changes that will make the code more pep8-compliant. Enabling pylint at this moment is not recommended, because it will complain too much.
The text was updated successfully, but these errors were encountered:
Ideally we should run flake8also in the examples. I remember that once I tried to run all of them and some were triggering errors (I cannot remember more details).
I considered this about 5 years ago. Unfortunately, the codebase is very
much not PEP8-compliant (I wouldn't be surprised if most of it predates a
lot of PEP8). At the time, my goal was to shut down this project, so I
didn't see any value in cleaning up the codebase. But, since your goals are
different from mine, it might make sense to do some cleanup. I should note
that the test suite is extremely sparse, and so I would stay away from
auto-formatting tools like `black` that could make inadvertent, subtle
changes that aren't covered by unit tests.
If anything, I'd suggest starting with converting the manually-run tests
and turning them into automated image tests.
In the context of fixing current issues within
basemap
, one easy step is to use static analysis tools, since they can catch the most evident problems.I open this issue as a reminder to enable
flake8
in the development workflow;flake8
will catch the most evident code mistakes, and it will also give advice on changes that will make the code more pep8-compliant. Enablingpylint
at this moment is not recommended, because it will complain too much.The text was updated successfully, but these errors were encountered: