# For bazel-in-bazel testing

# Trick bazel into treating BUILD files under examples/* and e2e/* as being regular files

# This lets us glob() up all the files inside the examples to make them inputs to tests

# (Note, we cannot use `common --deleted_packages` because the bazel version command doesn't support it)

# To update these lines, run this command:

# sed -i.bak "/^[^#].*--deleted_packages/s#=.*#=$(find examples/*/* \( -name BUILD -or -name BUILD.bazel \) | xargs -n 1 dirname | paste -sd, -)#" .bazelrc && rm .bazelrc.bak

build --deleted_packages=examples/pip/boto,examples/pip/extras,examples/pip/helloworld

query --deleted_packages=examples/pip/boto,examples/pip/extras,examples/pip/helloworld

3.3.1

* @thundergolfer @andyscott

/python/ @brandjon @lberki

/python/pip.bzl @thundergolfer @andyscott

/python/whl.bzl @thundergolfer @andyscott

/python/requirements.txt @thundergolfer @andyscott

/proposals/ @brandjon @lberki

/LICENSE @brandjon @lberki

/CONTRIBUTING.md @brandjon @lberki

In the interest of fostering an open and welcoming environment, we as

contributors and maintainers pledge to making participation in our project and

our community a harassment-free experience for everyone, regardless of age, body

size, disability, ethnicity, sex characteristics, gender identity and expression,

level of experience, education, socio-economic status, nationality, personal

appearance, race, religion, or sexual identity and orientation.

Examples of behavior that contributes to creating a positive environment

include:

* Using welcoming and inclusive language

* Being respectful of differing viewpoints and experiences

* Gracefully accepting constructive criticism

* Focusing on what is best for the community

* Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or

advances

* Trolling, insulting/derogatory comments, and personal or political attacks

* Public or private harassment

* Publishing others' private information, such as a physical or electronic

address, without explicit permission

* Other conduct which could reasonably be considered inappropriate in a

professional setting

Project maintainers are responsible for clarifying the standards of acceptable

behavior and are expected to take appropriate and fair corrective action in

response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or

reject comments, commits, code, wiki edits, issues, and other contributions

that are not aligned to this Code of Conduct, or to ban temporarily or

permanently any contributor for other behaviors that they deem inappropriate,

threatening, offensive, or harmful.

This Code of Conduct applies both within project spaces and in public spaces

when an individual is representing the project or its community. Examples of

representing a project or community include using an official project e-mail

address, posting via an official social media account, or acting as an appointed

representative at an online or offline event. Representation of a project may be

further defined and clarified by project maintainers.

Instances of abusive, harassing, or otherwise unacceptable behavior may be

reported by contacting the project team at bazel-discuss@googlegroups.com. All

complaints will be reviewed and investigated and will result in a response that

is deemed necessary and appropriate to the circumstances. The project team is

obligated to maintain confidentiality with regard to the reporter of an incident.

Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good

faith may face temporary or permanent repercussions as determined by other

members of the project's leadership.

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,

available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see

name: "\U0001F41EBug report"

about: Report a bug in rules_python

<!-- ✍️edit: --> The issue is caused by the rule:

<!-- ✍️--> Yes, the previous version in which this bug was not present was: ....

<!-- ✍️--> A clear and concise description of the problem...

<pre><code>

</code></pre>

**Operating System:**

<pre>

<code>

</code>

</pre>

**Output of `bazel version`:**

<pre>

<code>

</code>

</pre>

**Rules_python version:**

<pre>

<code>

</code>

</pre>

**Anything else relevant?**

name: "\U0001F680Feature request"

about: Suggest a feature for rules_python

<!-- ✍️--> A clear and concise description of the problem or missing capability...

<!-- ✍️--> If you have a solution in mind, please describe it.

<!-- ✍️--> Have you considered any alternative solutions or workarounds?

Please check if your PR fulfills the following requirements:

- [ ] Does not include precompiled binaries, eg. `.par` files. See [CONTRIBUTING.md](/CONTRIBUTING.md) for info

- [ ] Tests for the changes have been added (for bug fixes / features)

- [ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?

- [ ] Bugfix

- [ ] Feature (please, look at the "Scope of the project" section in the README.md file)

- [ ] Code style update (formatting, local variables)

- [ ] Refactoring (no functional changes, no api changes)

- [ ] Build related changes

- [ ] CI related changes

- [ ] Documentation content changes

- [ ] Other... Please describe:

Issue Number: N/A

- [ ] Yes

- [ ] No

The bulk of this repo is owned and maintained by the Bazel Python community.

However, since the core Python rules (`py_binary` and friends) are still

bundled with Bazel itself, the Bazel team retains ownership of their stubs in

this repository. This will be the case at least until the Python rules are

fully migrated to Starlark code.

Practically, this means that a Bazel team member should approve any PR

concerning the core Python logic. This includes everything under the `python/`

directory except for `pip.bzl`, `whl.bzl`, and `requirements.txt`.

Issues should be triaged as follows:

- Anything concerning the way Bazel implements the core Python rules should be

filed under [bazelbuild/bazel](https://github.com/bazelbuild/bazel), using

the label `team-Rules-python`.

- If the issue specifically concerns the rules_python stubs, it should be filed

here in this repository and use the label `core-rules`.

- Anything else, such as feature requests not related to existing core rules

functionality, should also be filed in this repository but without the

`core-rules` label.

Bazel team, provides support for the code. However, this repository is part of

`WORKSPACE` file:

name = "rules_python",

url = "https://github.com/bazelbuild/rules_python/releases/download/0.0.2/rules_python-0.0.2.tar.gz",

strip_prefix = "rules_python-0.0.2",

sha256 = "b5668cde8bb6e3515057ef465a35ad712214962f0b3a314e551204266c7be90c",

If you want to use the pip packaging rules, also add:

load("//python:pip.bzl", "pip_repositories")

pip_repositories()