-
Notifications
You must be signed in to change notification settings - Fork 5
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
Comments
General debugging arsenal:
|
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. 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:
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: |
Its a Good Thing that others may not do that...
|
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 |
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
The text was updated successfully, but these errors were encountered: