

The output is extremely useful as a memory aide for large programs and modules.
Bbedit python code#
I love this, it encourages me to properly document my code as I write with pydoc strings for each function. The final entry in this menu ”Show Module Documentation” displays a new text window with the output from running pydoc across your file. You will find “Check Syntax under the ”#!“ menu which also allows you to run your Python code. At the top of your project directory tree, on the command line bbedit -maketags will generate a tags file and now “Find Definition” will work across all the Python files in the tree.īBEdit can also run a syntax check across your source. Not only can BBEdit use a tags file but it can (using the open source utility ctags) generate them. This is a file that lists all the function definitions and variables used in all the files in a directory tree. The other neat item under the Search menu is “Find Definition”, this will find where in your file a function is defined – useful if you have a long source file.īut how does that work if our project is in multiple source files? Well, Unix has long known of that problem and had a solution. Dash will search across all your documentation sets but it is easy to set the sort order so the Python entries are close to the top and in the Dash results window there is a little Python icon next to the Python results.

Just select a library call and choose “Find In Reference…” under the Search menu and BBEdit will pass the search to Dash. This is a brilliant tool for searching documentation sets and can be easily searched from BBEdit. There are a number of things you can do to improve BBEdit as a Python IDE.

There are two tasks that I use an editor for, writing Python and writing Markdown so those are the two that I looked at. I have to say BareBones Software’s tag line for BBEdit is true “BBEdit – It doesn’t suck!”. Recently, with version 11, BBEdit introduced a demo mode so I thought to take another look at the big brother of TextWrangler.
