Development Tools
sosey opened this issue · 14 comments
Things people use to help with their development:
flake8 (pyflakes + pep8)
pylint
autopep8
Valgrind
Some of these can be encorperated into your editor for on the fly style checking
General debugging arsenal:
- strace - system call monitoring (linux)
- dtruss - system call monitoring (osx)
- gdb - low level process debugging (i.e.
gdb --args python [script_here]) - pdbpp - high level Python debugger with highlighting, similar to gdb
- pudb - high level Python debugger with a nice TUI interface
- faulthandler - For trapping segmentation faults in extensions
What's all these fancy pants? What's wrong with this good ol' method?
print('HERE!')
# tested codes
print('HERE NOW!')Thu, Jul 28th, noon - 1 pm, S322 - PEP 8 practicalities.
(Let me know if it's not a good time.)
We will go over how to configure editors to conform to PEP 8. We have volunteers to help with vi, emacs, wing, atom. Let me know if you are using a different editor.
We'll also cover other tools that help with PEP 8.
On Jul 25, 2016, at 11:00 AM, Nadia Dencheva notifications@github.com wrote:
We will go over how to configure editors to conform to PEP 8. We have volunteers to help with vi, emacs, wing, atom. Let me know if you are using a different editor.
Komodo Edit
Ah, yes, the goal is to share experience and eventually fix that failing PEP8 test in the JWST test suite 😏
For various reasons, moving this meeting to next Mon, Aug 1st, at noon, in the Boardroom.
@nden, above you had asked about editors. I use PyCharm. What I like about it is that it has git built in and subtly highlights the code inconsistencies with PEP8. It also has great debugging and one can step through code (in/out/over) really easily (even JWST code).
If not PyCharm, then vim, no question on that one. Hehehe
Reminder: today in the boardroom
Confirmed: cl-mode can highlight both CL and SPP codes in Emacs. Bet you can't do that with the others... 👻
The downside of having automatic PEP8 check in my editor is that I feel like the editor is constantly judging me...
I am sure you could find some colleagues to judge you instead :-)
Things have changed since. Nowadays, it is tox and black in the Python world. C is still the same.