https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INSTRM-1320 Instrument control development <p>Apply <tt>black -l 110 -S</tt> to all python code in the three FPS packages. Not really what we want to do (black is a crude and ugly tool), but there is just too much variability in the code formatting.</p> INSTRM-1320

Unify FPS code formatting

Task Normal Done Done cloomis cloomis PFI Mon, 12 Jul 2021 09:51:00 +0000 Thu, 23 Feb 2023 05:55:26 +0000 Thu, 23 Feb 2023 05:55:26 +0000 ics_cobraCharmer ics_fpsActor ics_mcsActor 0 1 <p>Like most other projects we require basic PEP8 compliance. So instead of <tt>black</tt> I ran the gentler <tt>autopep8</tt>, using the recommended LSST invocation: <tt>autopep8 --ignore E133,E226,E228,E266,N802,N803,N806,W503 --max-line-length 110</tt>. That resulted in fewer disturbing rewrites.</p> <p>Merged to <tt>ics_cobraCoach</tt>, <tt>ics_mcsActor</tt>, <tt>ics_fpsActor</tt>. We should try to keep the code from diverging again.</p> <p>n.b. The <a href="https://developer.lsst.io/index.html" class="external-link" rel="nofollow">LSST Developer guide</a> discusses PEP8, etc. and has recommendations for configuring emacs/Sublime/vim/VS Code. PFS is not LSST, but we do share some development.</p> <p>It was conformed this was done at the ASIAA meeting</p> Development Rank 0|zzs8jk: