SourceLair Blog

  • Choosing Python version

    SourceLair's default Python version currently is 2.7.6. One of the most popular requests from our users in the support channel is a way to change the Python version to 3+.

    We have now documented a fast and easy way to change your Python version. With a single and simple command you can switch the Python version back and forth between 2.7.6 and 3.4.3. The command also takes care of switching between your pip from pip2 to pip3 and vise versa. Just be sure to restart your terminal and your server for the change to take place. Also, if you've already installed any packages, after changing your Python version make sure to reinstall them.

    You can find the documentation and commands for the version switching at

  • Say hello to Django 1.9 Beta1

    Woah, a new Django version popped out in SourceLair and it's 1.9!

    Django version selection

    While Django 1.9 is still in Beta, we have already committed to support Django Beta versions within 24 hours of their release. Why Beta you ask?

    Django is stable, well tested and written with good care, but in software like this there always might be websites or applications that fall into corner cases never thought before. By trying out your existing, or new applications in Beta versions, you help by finding bugs or proposing enhancements before the production-ready release comes out. If you come up to a bug, you can always use the issue tracker to report it.

    With SourceLair, that's just 3 clicks away, just go on, create or clone your Django project and try out the awesome new features introduced in 1.9!

  • Node.js meets native Heroku support

    Starting today, you will think no more if your Node.js project will work nicely in Heroku.

    Setting up your development environment is always tricky. You want to spend the least time and resources possible, while at the same time make sure it is as close as possible to your production infrastructure.

    With deployment platforms like Heroku, this becomes even trickier as you usually don't know how your application runs.

    Heroku Projects in SourceLair

    As Heroku is one of the first deployment platforms we supported, extending such support by providing you with a Heroku powered environment was the least we could do for you. That's why, we're glad to announce a new project type, which is powered by this environment, flavored in a way that keeps all these features you already love about SourceLair, like dependency management, great Git and Mercurial support, server reloading on file system changes and lots more.

    All you have to do, is switch to the Heroku tab while choosing a project type and select one of the Heroku flavored environments for your project. For the time being, we leave you with a fully-fleshed Node.js environment and a promise that more platforms are coming in the near future.

    Enough reading, time for action. Just sign in to SourceLair, create or clone a new Heroku Node.js project and enjoy frictionless Heroku deployments with the new Heroku based environment.

  • Enhanced Python autocompletion

    Even though SourceLair has supported Python autocomplete for a while, it was not quite right. The autocomplete suggestions where restricted to keywords and to file-wide variables and function names.

    This obviously did not provide the coding experience we want to provide. One where your tools work for you and remove the friction from your workflow.

    So we changed it!

    We're very happy to announce that SourceLair's Python autocomplete is now powered by Jedi. By using this awesome autocompletion and static analysis library we are able to provide sophisticated and precise suggestions for autocompletion, accompanied by their documentation!


    Autocompletion is normally triggered by Ctrl + Space and you can also toggle triggering on keystroke in the editor settings.

    Furthermore, also thanks to jedi, when you are inside a function call the expected arguments of the function appear to help you save time from searching for the definition and ensuring you gave the correct arguments. arguments And the amazing thing is that the even though the extensive analysis is server-side and there is network involved in the whole process, the speed is great, the responses immediate and the experience native-like!

    Just sign in to SourceLair and try it out for yourself.

  • Customizing JavaScript linting

    Being able to get real-time warnings on source code as you type helps to greatly reduce the time you'll spend later on polishing and debugging your code.

    SourceLair has been using JSHint for JavaScript linting for a while now. All you have to do is enable JavaScript linting from your Editor Settings and you'd instantly get warnings and errors in the gutter right next to your code. JavaScript Linting

    However, in order for the warnings to be useful and not distracting, you have to be able to define yourself what is - and what is not - a warning.

    Starting today, you can customize the type of warnings you get, when having Javascript linting enabled, simply by including a .jshintrc file in your project's root. The .jshintrc is a simple JSON file that specifies which JSHint options to turn on or off. Alternatively, if you're writing Nodejs, you can include your jshint config into your project's package.json file under the jshintConfig property. You can find the full list of the supported options here. sample-jshintrc

    Go to your project at, utilize JSHint with the options of your preferece, simplify your life and enhance your workflow.