Skip to content

Releases: microsoft/vscode-python

2018.9.1

18 Oct 20:52
26bd9d6
Compare
Choose a tag to compare
Make a 2018.9.1 release (#2951)

2018.9.0

09 Oct 18:57
Compare
Choose a tag to compare
typo file -> filed (#2810)

2018.8.0

05 Sep 22:45
cf167fe
Compare
Choose a tag to compare
Update changelog with last-minute fix (#2485)

2018.7.1

24 Jul 01:31
b81dea5
Compare
Choose a tag to compare
2018.7.1 release (#2235)

* Bump version number

* Touch up news entries

* Update changelog

* 2018.7.1 release for new language server

2018.7.0

19 Jul 19:13
6af8f99
Compare
Choose a tag to compare

2018.7.0 release

2018.6.0

20 Jun 19:21
0907018
Compare
Choose a tag to compare
2018.6.0 final release (#2020)

2018.5.0

05 Jun 19:13
90cf55c
Compare
Choose a tag to compare
Final release preparations (#1866)

2018.4.0

02 May 18:34
a8f2df6
Compare
Choose a tag to compare
Bump to final for 2018.4.0 (#1562)

2018.3.0

29 Mar 18:28
0759f88
Compare
Choose a tag to compare
2018.3.0 release details (#1227)

Hotfix for Pipfile case-sensitivity detection

09 Mar 18:24
Compare
Choose a tag to compare
Cherry-pick Pipfile detection fix for 2018.2.1 (#1002)

* Detect pipenv by looking for Pipfile, not pipfile (#994)

On platforms with case-sensitive filesystems, like Linux, these are not
equivalent. pipenv documents that the file should be called Pipfile[0]
and `Pipfile.find()` only finds files matching this exact case[1].

As a result, even if `pipenv --venv` in `cwd` would return success, it
will never be run on Linux, and Code never detects the pipenv. (You can
work around this with `touch pipfile`.) With this change, it's detected
successfully. I believe there's no need to add a backwards-compatibility
check for the old case, because on platforms where the old, incorrect
check worked, so will the new, correct one.

[0] https://docs.pipenv.org/basics/#example-pipfile-pipfile-lock
[1] https://github.com/pypa/pipfile/blob/5acb9ac7/pipfile/api.py#L76-L85

* Prep for 2018.2.1