Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Spyder vs pkgsrc, the Slant community recommends Spyder for most people. In the question“What are the best developer tools for Mac OSX?” Spyder is ranked 24th while pkgsrc is ranked 28th. The most important reason people chose Spyder is:
Released under the MIT license.
Specs
Question Ranking
Pros
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 Enables to write consistent code
Pylint integration enables to check the code for PEP8 style guide and detect errors.
Pro Powerful autocompletion
Spyder's autocomplete features are made possible by a library called rope which gives Spyder powerful autocompletion.
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 Helps you to use documentation
Pro Intuitive interface
Pro Relatively lightweight
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
Pro pkgin is an apt-like tools for installing binaries from pkgsrc
pkgin aims to be a tool similar to apt/yum for managing pkgsrc binaries by relying on pkg_summary for installing, removing and upgrading packages and dependencies, using a remote repo.
Pro Adapted for use on over a dozen different operating systems
Has been adopted to be used on several Unix-like operating systems and Windows. It's also the default package manager of DragonflyBSD and of the (now discounted) Bluewall Linux distro.
Pro Installs and works in the same way as MacPorts
Installs its own dependencies which means that it is very secure. Cannot install anything unless you use the "sudo" command which is in keeping with the Unix philosophy.
Pro Both binary packages and source build possible
Fast software installation is possible by using binary packages. It's also easy to build from source which allows for different compile-time options (like different UI backends) as well as gaining access to pre-release versions of software in certain cases.
Pro Offering tooling for backporting fixes
Backporting fixes can be done by cherry-picking updates from a newer branch (pkgsrc is released every 3 months) and creating a package. Sometimes bugs need to be fixed for production and there is neither a fix in newer pkgsrc nor the softwares upstream. So pkgsrc has tools like pkgdiff, mkpatches, etc. that help with developing patches and building binary packages from that. A bit of documentation about that process can be found here.
Pro Does not need Xcode command line tools or Xcode.
This means that you can install it fresh on a new installation of MacOS and have all your favorite apps installed right from the start.
Pro Works easily with Ansible
Can be used from within Ansible to install packages on macOS.
Pro Easy installation if you use 3rd party scripts
This one works brilliantly.
Cons
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.
Con Consumes a lot of memory
If you're working with large data, especially arrays, another IDE should be considered as spyder uses at least 200-300Mb of memory.
Con Relatively complicated setup and installation
Installing and setting pkgsrc up is a bit more complicated than in other package managers where it often consists in running a single script.
Con Not so broadly used on MacOS as compared with MacPorts
You do not hear about Pkgsrc as openly as you hear the words "HomeBrew" or "MacPorts".
Con Outdated packages
Some packages are outdated.
Con Can't install some packages
Even building well known packages (except MacPorts) from source using the ports can fail.
