Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need a way to get a path to python interpeter #7002

Closed
solomatov opened this issue Dec 27, 2018 · 3 comments
Closed

Need a way to get a path to python interpeter #7002

solomatov opened this issue Dec 27, 2018 · 3 comments
Labels
P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) team-Rules-Python Native rules for Python type: feature request

Comments

@solomatov
Copy link

Description of the problem / feature request:

I want to run a python based tool such as pylint

Feature requests: what underlying problem are you trying to solve with this feature?

I don't want people running our build install pylint manually as well as running from manually installed virtual environment. I want it to be installed via repository rule without any extra actions.

What operating system are you running Bazel on?

OSX and Linux

What's the output of bazel info release?

release 0.20.0-homebrew

Have you found anything relevant by searching the web?

I found that there're tool variables for C/C++ and Java but there's no such a variable for Python

Any other information, logs, or outputs that you want to share?

No

@aiuto aiuto added untriaged team-Rules-Python Native rules for Python labels Jan 2, 2019
@brandjon
Copy link
Member

You're asking for pylint to be distributed via Bazel to users using a repository rule? This seems to be treating Bazel as a package manager rather than a build tool. Or do you mean you want pylint automatically invoked as part of the build process, and to block the build if it detects any warnings/errors?

@brandjon brandjon added type: feature request P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) and removed untriaged labels Mar 14, 2019
@brandjon
Copy link
Member

See also #7805.

@sgowroji sgowroji added the stale Issues or PRs that are stale (no activity for 30 days) label Feb 16, 2023
@sgowroji
Copy link
Member

Hi there! We're doing a clean up of old issues and will be closing this one. Please reopen if you’d like to discuss anything further. We’ll respond as soon as we have the bandwidth/resources to do so.

@sgowroji sgowroji closed this as not planned Won't fix, can't repro, duplicate, stale Feb 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) team-Rules-Python Native rules for Python type: feature request
Projects
None yet
Development

No branches or pull requests

4 participants