Ok, I’m trying to use Scons and finally had half a day to finally get some sort of IDE going. Anaconda for Sublime is pretty cool. Complicated to setup, you actually have to paste in Python code if you can believe it, but the punchline is that it lets you do a goto any definition which is pretty useful, so in my favorite vintage (e.g. vi mode), if you go to a module and type gd then it will go to the definition and open the module.
And if you right click on an string you can:
- Find all the places the object is used
-
Print out the docstring documentation
-
Rename it across all its usages.
Pretty neat, then you can use the Sublime build system (Ctrl-B in Linux) to compile and run the thing)
Then there is the lint system. This time we use sublime linter and it produces error messages that are running and you right click on it.
Scons building with Sublime
Well this is pretty cool, but using Sublime Text 2 build and Sublime Text 3 build as an example, you can actually test your Sconscript by creating a file in ~/.config/sublime-text-3/Packages/User/Scons.sublime-build
{
  "name": "SCons",
  "shell_cmd": "scons",
  "working_dir": "${project_path:${folder:${file_path}}}\..",
  "variants":
  [
   {
     "name": "Clean",
     "cmd": ["scons", "-c"]
   }
  ]
}
Â
