Development Tools - Githubissues

spacetelescope / braindump

A place to collect notes from code discussions

2 stars 5 forks source link

Development Tools #6

Open sosey opened 8 years ago

sosey commented 8 years ago

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

jhunkeler commented 8 years ago

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

pllim commented 8 years ago

What's all these fancy pants? What's wrong with this good ol' method?

print('HERE!')
# tested codes
print('HERE NOW!')

nden commented 8 years ago

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.

bernie-simon commented 8 years ago

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

http://komodoide.com/komodo-edit/

pllim commented 8 years ago

Real programmers

nden commented 8 years ago

Ah, yes, the goal is to share experience and eventually fix that failing PEP8 test in the JWST test suite :smirk:

nden commented 8 years ago

For various reasons, moving this meeting to next Mon, Aug 1st, at noon, in the Boardroom.

brechmos-stsci commented 8 years ago

@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

nden commented 8 years ago

Reminder: today in the boardroom

pllim commented 8 years ago

Confirmed: cl-mode can highlight both CL and SPP codes in Emacs. Bet you can't do that with the others... :ghost:

cdsontag commented 8 years ago

Its a Good Thing that others may not do that...

pllim commented 8 years ago

The downside of having automatic PEP8 check in my editor is that I feel like the editor is constantly judging me...

brechmos-stsci commented 8 years ago

I am sure you could find some colleagues to judge you instead :-)

pllim commented 1 year ago

Things have changed since. Nowadays, it is tox and black in the Python world. C is still the same.