Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Development Tools #6

Open
sosey opened this issue Apr 15, 2016 · 14 comments
Open

Development Tools #6

sosey opened this issue Apr 15, 2016 · 14 comments

Comments

@sosey
Copy link
Member

sosey commented Apr 15, 2016

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
Copy link

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
Copy link
Contributor

pllim commented Apr 15, 2016

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

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

@nden
Copy link
Contributor

nden commented Jul 25, 2016

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
Copy link

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
Copy link
Contributor

pllim commented Jul 25, 2016

Real programmers

@nden
Copy link
Contributor

nden commented Jul 25, 2016

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

@nden
Copy link
Contributor

nden commented Jul 28, 2016

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

@brechmos-stsci
Copy link

brechmos-stsci commented Jul 29, 2016

@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
Copy link
Contributor

nden commented Aug 1, 2016

Reminder: today in the boardroom

@pllim
Copy link
Contributor

pllim commented Aug 1, 2016

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

@cdsontag
Copy link

cdsontag commented Aug 1, 2016 via email

@pllim
Copy link
Contributor

pllim commented Aug 3, 2016

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

@brechmos-stsci
Copy link

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

@pllim
Copy link
Contributor

pllim commented Apr 7, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants