The PEP 263 define that if a Unicode string with a coding declaration is
passed to the compule() built-in function, a SyntaxError will be raised.
SublimeText 3 pass the buffers as Unicode strings, fix for this approach
on McCabe complexity checker
workaround to make JsonServer dont crash becasue Jedi https://github.com/davidhalter/jedi/issues/331 bug on Windows and PyQt4 reported in anaconda by @augusto2112 in #108
now we check if the linter is enabled before show commands related with, solve #107
added check for anaconda linting in get_lines command
update jedi library to commit 4ff8b921a3b252895ed43b9598a5a40f0cbd487c from stable branch
totally fixed problem with PyQt on Jedi library itself. this is related with issue #108
Workaround to mitigate the severe memory leaks that plugin_host suffer when objects are shared betwen threads. In the API doc of ST3 they said those _async methods are thread safe, but the objects that are created in local scopes into that functions are not being collected by the ST3 embedded python garbage collector and severe memory leaks appears much more often if your plugin is hardly based on asynchronous events (as anaconda is). This meant to solve (or at least strongly mitigate) the #97 issue
Fixes hang on Jedi connects that timed out

I haven't narrowed down exactly why this happened, yet, however after
having trouble with ST for ~3 days now, have found a fix.

After starting ST3, which resumed a session with about 6 previously open
windows, Anaconda would register a local handler, and a few seconds
later called `server_is_active` on the worker for it. At that time, ST3
would hang.

As it turns out, Anaconda couldn't connect to the worker it set up, but
didn't use a socket timeout for the `server_is_active` check. Without
specifying one, this could cause ST3 on OSX to hang for 5 minutes.

Once ST responded after 5mins, the expected 'timed out' exception
appeared in the console. Seemed to happen only once at startup no matter
how many windows I had open in the session.

At first, to temporarily get around this, I renamed my
`~/Library/Caches/Jedi` folder between ST runs to get it to build a
fresh caches folder. So something in there created/managed by Jedi seems
to be the root cause.

Ultimately, I was able to fix this altogether on the Anaconda side with
this addition of a 0.5sec timeout on the socket that
`BaseWorker.server_is_active` creates.

`BaseWorker.server_is_healthy` already uses the same 0.5sec timeout, so
the assumption of 0.5 seemed safe for checking whether it's simply
active.
master: Adding a [Set Python Interpreter] command to make it easier to set python path when working on many projects with  different virtual environment
Merge pull request #113 from briancline/local-jedi-timeout-fix

Fixes hang on Jedi connects that timed out
Merge pull request #114 from bhappyz/master

Feature: Adding a [Set Python Interpreter] command
Import new AnacondaSetPythonInterpreter class

AnacondaSetPythonInterpreter is present in __all__ list but not imported.
Merge pull request #115 from ihuston/patch-1

Import new AnacondaSetPythonInterpreter class
added utoimport feature to context menu
README.md updated, solved #117 in previous commit
Adding decorators to first line detection
Merge pull request #118 from bhappyz/master

Adding decorators to first line detection on auto import feature
Fix issue with ignore_pyflakes not working.  Essentially it was attempted to update a variable that bottomed out in a static class variable in Checker, so the update wasn't taking.  Thankfully Checker instead has an easy way to solve this by passing our ignore values to the builtins argument, so twas an easy fix.
Merge pull request #119 from jimjkelly/fix/pyflakes_ignore

Fix issue with ignore_pyflakes not working.
anaconda was linting non related files because a bug in the always linting behavior, this commit fixes #120