When comparing Bluefish vs Spyder, the Slant community recommends Spyder for most people. In the question“What are the best Python IDEs or editors?” Spyder is ranked 8th while Bluefish is ranked 35th. The most important reason people chose Spyder is:
Spyder's autocomplete features are made possible by a library called [rope](https://github.com/python-rope/rope) which gives Spyder powerful autocompletion.
Ranked in these QuestionsQuestion Ranking
Bluefish highlights matching blocks for start and end markers (for both brackets and tags).
Pro Emmet support
Support Emmet or Zen Coding.
Pro Auto-completion and auto-tag-closing
Pro Light and fast
Bluefish starts really quick (even on a netbook) and loads hundreds of files within seconds.
Pro Very powerful search and replace
Bluefish supports Perl Compatible regular expressions, sub-pattern replacing, and search and replace in files on disk
Pro Powerful autocompletion
Spyder's autocomplete features are made possible by a library called rope which gives Spyder powerful autocompletion.
Pro Free and open-source
Released under the MIT license.
Pro Graph plotting support
Spyder can plot graphs and provide the list of all variables.
Pro Has cross platform support - Linux, Mac, and even Windows
Spyder (formerly Pydee) has support for all of the major operating platforms - Linux, Mac, and even Windows.
Pro Relatively lightweight
Pro Helps you to use documentation
Pro Intuitive interface
Pro Enables to write consistent code
Pylint integration enables to check the code for PEP8 style guide and detect errors.
Pro Has support for Vim bindings via plugin support
Aside from being an open sourced, actively developed IDE, vim key-binding support is also available. If you remember Pydee - this is it, albeit with a new name.
Pro Good GitHub project
Pro Excellent variable explorer
Dynamic variable explorer with editor and visualizer
Pro Completely Python
Con Not beautiful
The default theme is not beautiful. And there are not many themes.
Con The documentation is poor when it comes to debugging
Not a lot of information about debugging is available in the documentation.