Merge remote-tracking branch 'upstream/master'

* upstream/master:
  Debug specific unittest test ends up running all failed tests (#671)
  Fix unhandled promise rejections (#702)
  🐛 Fixes #700 replace back slashes in fie paths with forward slashes (#707)
  Validate file execution handler (#698)
  Update contributing guide (#687)
  Formatting on Enter (#649)
  Start the 2018.2.0 alpha (#685)
  Prep for 2018.1 final (#683)
  Speed up interpreter locators (#676)
  Create a release candidate (#663)
  Activation of terminal using conda activate and fixes to powershell script execution (#665)
  Register linter commands (#653)
  Preserve focus when sending text to a terminal (#651)
  Work around VSC issue with formatting on save #624 (#635)
  Korean translation (#540)
  Improving getting started instructions in README and minor updates to contributors guide (#605)
  Bump to a beta version for some testing (#630)
  Activate extension when command 'Create Terminal' is invoked (#632)

Author: DonJayamanne

CHANGELOG.md

@@ -1,5 +1,58 @@
 # Changelog
 
+## 2018.2.0
+
+XXX
+
+## 2018.1.0 (01 Feb 2018)
+
+### Thanks
+
+Thanks to everyone who contributed to this release, including
+the following people who contributed code:
+
+* [jpfarias](https://github.com/jpfarias)
+* [Hongbo He](https://github.com/graycarl)
+* [JohnstonCode](https://github.com/JohnstonCode)
+* [Yuichi Nukiyama](https://github.com/YuichiNukiyama)
+* [MichaelSuen](https://github.com/MichaelSuen-thePointer)
+
+### Fixed issues
+
+* Support cached interpreter locations for faster interpreter selection ([#666](https://github.com/Microsoft/vscode-python/issues/259))
+* Sending a block of code with multiple global-level scopes now works ([#259](https://github.com/Microsoft/vscode-python/issues/259))
+* Automatic activation of virtual or conda environment in terminal when executing Python code/file ([#383](https://github.com/Microsoft/vscode-python/issues/383))
+* Introduce a `Python: Create Terminal` to create a terminal that activates the selected virtual/conda environment ([#622](https://github.com/Microsoft/vscode-python/issues/622))
+* Add a `ko-kr` translation ([#540](https://github.com/Microsoft/vscode-python/pull/540))
+* Add a `ru` translation ([#411](https://github.com/Microsoft/vscode-python/pull/411))
+* Performance improvements to detection of virtual environments in current workspace ([#372](https://github.com/Microsoft/vscode-python/issues/372))
+* Correctly detect 64-bit python ([#414](https://github.com/Microsoft/vscode-python/issues/414))
+* Display parameter information while typing ([#70](https://github.com/Microsoft/vscode-python/issues/70))
+* Use `localhost` instead of `0.0.0.0` when starting debug servers ([#205](https://github.com/Microsoft/vscode-python/issues/205))
+* Ability to configure host name of debug server ([#227](https://github.com/Microsoft/vscode-python/issues/227))
+* Use environment variable PYTHONPATH defined in `.env` for intellisense and code navigation ([#316](https://github.com/Microsoft/vscode-python/issues/316))
+* Support path variable when debugging ([#436](https://github.com/Microsoft/vscode-python/issues/436))
+* Ensure virtual environments can be created in `.env` directory ([#435](https://github.com/Microsoft/vscode-python/issues/435), [#482](https://github.com/Microsoft/vscode-python/issues/482), [#486](https://github.com/Microsoft/vscode-python/issues/486))
+* Reload environment variables from `.env` without having to restart VS Code ([#183](https://github.com/Microsoft/vscode-python/issues/183))
+* Support debugging of Pyramid framework on Windows ([#519](https://github.com/Microsoft/vscode-python/issues/519))
+* Code snippet for `pubd` ([#545](https://github.com/Microsoft/vscode-python/issues/545))
+* Code clean up ([#353](https://github.com/Microsoft/vscode-python/issues/353), [#352](https://github.com/Microsoft/vscode-python/issues/352), [#354](https://github.com/Microsoft/vscode-python/issues/354), [#456](https://github.com/Microsoft/vscode-python/issues/456), [#491](https://github.com/Microsoft/vscode-python/issues/491), [#228](https://github.com/Microsoft/vscode-python/issues/228), [#549](https://github.com/Microsoft/vscode-python/issues/545), [#594](https://github.com/Microsoft/vscode-python/issues/594), [#617](https://github.com/Microsoft/vscode-python/issues/617), [#556](https://github.com/Microsoft/vscode-python/issues/556))
+* Move to `yarn` from `npm` ([#421](https://github.com/Microsoft/vscode-python/issues/421))
+* Add code coverage for extension itself ([#464](https://github.com/Microsoft/vscode-python/issues/464))
+* Releasing [insiders build](https://pvsc.blob.core.windows.net/extension-builds/ms-python-insiders.vsix) of the extension and uploading to cloud storage ([#429](https://github.com/Microsoft/vscode-python/issues/429))
+* Japanese translation ([#434](https://github.com/Microsoft/vscode-python/pull/434))
+* Russian translation ([#411](https://github.com/Microsoft/vscode-python/pull/411))
+* Support paths with spaces when generating tags with `Build Workspace Symbols` ([#44](https://github.com/Microsoft/vscode-python/issues/44))
+* Add ability to configure the linters ([#572](https://github.com/Microsoft/vscode-python/issues/572))
+* Add default set of rules for Pylint ([#554](https://github.com/Microsoft/vscode-python/issues/554))
+* Prompt to install formatter if not available ([#524](https://github.com/Microsoft/vscode-python/issues/524))
+* work around `editor.formatOnSave` failing when taking more then 750ms ([#124](https://github.com/Microsoft/vscode-python/issues/124), [#590](https://github.com/Microsoft/vscode-python/issues/590), [#624](https://github.com/Microsoft/vscode-python/issues/624), [#427](https://github.com/Microsoft/vscode-python/issues/427), [#492](https://github.com/Microsoft/vscode-python/issues/492))
+* Function argument completion no longer automatically includes the default argument ([#522](https://github.com/Microsoft/vscode-python/issues/522))
+* When sending a selection to the terminal, keep the focus in the editor window ([#60](https://github.com/Microsoft/vscode-python/issues/60))
+* Install packages for non-environment Pythons as `--user` installs ([#527](https://github.com/Microsoft/vscode-python/issues/527))
+* No longer suggest the system Python install on macOS when running `Select Interpreter` as it's too outdated (e.g. lacks `pip`) ([#440](https://github.com/Microsoft/vscode-python/issues/440))
+* Fix potential hang from Intellisense ([#423](https://github.com/Microsoft/vscode-python/issues/423))
+
 ## Version 0.9.1 (19 December 2017)
 
 * Fixes the compatibility issue with the [Visual Studio Code Tools for AI](https://marketplace.visualstudio.com/items?itemName=ms-toolsai.vscode-ai) [#432](https://github.com/Microsoft/vscode-python/issues/432)

CONTRIBUTING.md

@@ -4,7 +4,7 @@
 
 ### Prerequisites
 
-1. Node.js (>= 8.9.1, < 9.0.0)
+1. Node.js (>= 8.9.1, < 9.0.0), and [Yarn](https://yarnpkg.com/lang/en/docs/install/)
 2. Python 2.7 or later (required only for testing the extension and running unit tests)
 3. Windows, OS X or Linux
 4. Visual Studio Code
@@ -20,6 +20,8 @@ cd vscode-python
 yarn install
 ```
 
+You may see warnings that ```The engine "vscode" appears to be invalid.```, you can ignore these.
+
 ### Incremental Build
 
 Run the `Compile` and `Hygiene` build Tasks from the [Command Palette](https://code.visualstudio.com/docs/editor/tasks) (short cut `CTRL+SHIFT+B` or `⇧⌘B`)
@@ -91,7 +93,7 @@ for a release are tracked in a
 [milestone](https://github.com/Microsoft/vscode-python/milestones)
 (which is actively updated as plans change).
 
-The overall schedule for a release is to code freeze for on the last
+The overall schedule for a release is to feature freeze for on the last
 Monday of the month to coincide with Visual Studio Code's code freeze.
 We then aim to release later that week so the latest version of the
 extension is already live by the time Visual Studio Code launches
@@ -102,16 +104,10 @@ between scheduled releases as necessary.
 All development is actively done in the `master` branch of the
 repository. It is what allows us to have an
 [insiders build](#insiders-build) which is expected to be stable at
-all times. We do keep the previous release as a branch in case the
+all times. We do keep the most recent release as a branch in case the
 need for a bugfix release arises. But once a new release is made we
-convert the older branch into a tag and delete the branch as
-Visual Studio Code's automatic updating makes keeping old versions
-around unnecessary.
-
-Since we try to spend about 25% of our development time fixing bugs
-and removing technical debt, the week of a release is mostly spent
-focusing on that topic. That way we don't ignore the health of the
-code base by accidentally focusing on new features exclusively.
+delete the older release branch (all releases are appropriately
+tagged, so history is lost).
 
 ### Issue triaging
 
@@ -140,21 +136,17 @@ lexicographically sort from earliest stage to latest stage). The
 suffix term for each label then specifies what is currently blocking
 the issue from being closed.
 
-* `1-`
-  * [`decision`](https://github.com/Microsoft/vscode-python/labels/awaiting%201-decision):
-    The issue is a feature enhancement request and a decision has not
-    been made as to whether we would accept a pull request
-    implementing the enhancement
-  * [`more info`](https://github.com/Microsoft/vscode-python/labels/awaiting%201-more%20info):
-    We need more information from the OP (original poster)
-  * [`verification`](https://github.com/Microsoft/vscode-python/labels/awaiting%201-verification):
-    We need to verify that the issue can be replicated
+* [`1-decision`](https://github.com/Microsoft/vscode-python/labels/awaiting%201-decision):
+The issue is a feature enhancement request and a decision has not
+been made as to whether we would accept a pull request
+implementing the enhancement
+* [`1-more info`](https://github.com/Microsoft/vscode-python/labels/awaiting%201-more%20info):
+We need more information from the OP (original poster)
+* [`1-verification`](https://github.com/Microsoft/vscode-python/labels/awaiting%201-verification):
+    We need to verify that the issue is reproducible
 * [`2-PR`](https://github.com/Microsoft/vscode-python/labels/awaiting%202-PR):
   The issue is valid and is now awaiting a fix to be created and
   merged into the `master` branch
-* [`4-validation`](https://github.com/Microsoft/vscode-python/labels/awaiting%204-validation):
-  A pull request has been merged and resolution of the issue should be
-  independently validated
 
 #### Closed issues
 
@@ -166,22 +158,21 @@ it should have an appropriate `closed-` label.
 
 1. Check that there is an issue corresponding to what the pull request
    is attempting to address
-   * If an issue exists, make sure it has reached the stage of being
-     labeled `awaiting 2-PR`
+   * If an issue exists, make sure it has reached the stage of
+     `awaiting 2-PR`
    * If no issue exists, open one and wait for it to reach the
      `awaiting 2-PR` stage before submitting the pull request
-1. Open the pull request, mentioning the appropriate issue(s) in the
+1. Create the pull request, mentioning the appropriate issue(s) in the
    pull request message body
    * The pull request is expected to have appropriate unit tests
    * The pull request must pass its CI run before merging will be
      considered
-   * Code coverage is expected to not worsen
+   * Code coverage is expected to (at minimum) not worsen
 1. Make sure all status checks are green (e.g. CLA check, CI, etc.)
 1. Address any review comments
 1. [Maintainers only] Merge the pull request
 1. [Maintainers only] Update affected issues to be:
    1. Closed (with an appropriate `closed-` label)
-   1. The stage is set to `awaiting 4-validation`
    1. The issue(s) are attached to the current milestone
    1. Register OSS usage
    1. Email CELA about any 3rd-party usage changes
@@ -192,11 +183,12 @@ Starting in 2018, the extension switched to
 [calendar versioning](http://calver.org/) since the extension
 auto-updates and thus there is no need to track its version
 number for backwards-compatibility. As such, the major version
-is the current year, the minor version is the current month, and
-the micro version is how many releases there have been that month in
-the year (starting at 0). For example, the first release in July 2018
-would be `2018.7.0`, the second release that month would be
-`2018.7.1`, etc.
+is the current year, the minor version is the month when feature
+freeze was reached, and the micro version is how many releases there
+have been since that feature freeze (starting at 0). For example
+the release made when we reach feature freeze in July 2018
+would be `2018.7.0`, and if a second release was necessary to fix a
+critical bug it would be `2018.7.1`.
 
 ## Insiders Build
 
@@ -212,7 +204,7 @@ file, please follow the instructions on
 [this page](https://code.visualstudio.com/docs/editor/extension-gallery#_install-from-a-vsix)
 to install the extension.
 
-The insiders build of the extension ...:
+The insiders build of the extension:
 
 * Will be replaced with new releases published onto the
   [VS Code Marketplace](https://marketplace.visualstudio.com/VSCode).