Skip to content
This repository was archived by the owner on Apr 14, 2022. It is now read-only.
This repository was archived by the owner on Apr 14, 2022. It is now read-only.

Language server not recognising True or False as builtins #394

Closed

Description

From Josh Smeaton (@jarshwah) on November 9, 2018 12:17

Environment data

  • VS Code version: 1.28.2
  • Extension version (available under the Extensions sidebar): 2018.10.0
  • OS and version: OSX
  • Python version (& distribution if applicable, e.g. Anaconda): python2.7 pyenv
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): pyenv virtualenv

Language Server: Microsoft Python Language Server version 0.1.60.0 (from startup logs)

Actual behavior

False and True are now being marked as use before defined, suggesting they're no longer recognised as built ins.

false-undefined

Expected behavior

The poor booleans are not targeted as being issues.

Steps to reproduce:

See screenshot above.

Copied from original issue: microsoft/vscode-python#3274

Activity

  1. DonJayamanne commented on Nov 14, 2018

    @DonJayamanne
    Author

    Interesting, I cannot replicate this at my end.
    Are you able to replicate this consistently?

  2. DonJayamanne commented on Nov 14, 2018

    @DonJayamanne
    Author

    From Joel Hock (@joelhock) on November 13, 2018 16:16

    i have the same issue; even a simple test case like this triggers it:

    if True:
        print "hi"

    VS Code version: 1.28.2 and 1.29.0
    Extension version (available under the Extensions sidebar): 2018.10.0
    OS and version: OSX 10.14
    Python version (& distribution if applicable, e.g. Anaconda): python 2.7.15 from homebrew
    Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
    Language Server: Microsoft Python Language Server version 0.1.60.0 (from startup logs)

  3. DonJayamanne commented on Nov 14, 2018

    @DonJayamanne
    Author

    From Jake Bailey (@jakebailey) on November 13, 2018 23:38

    I can make this happen on my machine, but only once, then it goes away for all files. I'll look into this upstream (and keep discussion there).

  4. DonJayamanne commented on Nov 14, 2018

    @DonJayamanne
    Author

    This is a dup

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions