aboutsummaryrefslogtreecommitdiffhomepage
path: root/examples/py
Commit message (Collapse)AuthorAge
* Automated rollback of commit 0f9c6ea574918dda094cf5423fa3822112846c30.Gravatar lberki2018-02-14
| | | | | | | | | | | | | | | | | | | *** Reason for rollback *** Breaks Kokoro and I accidentally submitted the change without presubmit checks. *** Original change description *** Make __init__.py files creation optional Introduce a new attribute to py_binary and py_test to control whether to create `__init__.py` or not. Fixes https://github.com/bazelbuild/rules_python/issues/55 Closes #4470. PiperOrigin-RevId: 185676592
* Make __init__.py files creation optionalGravatar Mouad Benchchaoui2018-02-14
| | | | | | | | | | | Introduce a new attribute to py_binary and py_test to control whether to create `__init__.py` or not. Fixes https://github.com/bazelbuild/rules_python/issues/55 Closes #4470. PiperOrigin-RevId: 185672243
* Remove unnecessary python skylark rules and update example Gravatar Yu Yi2017-02-28
| | | | | | | | | | | | | | | | | | | | | | | * We already have native python rules, so the skylark ones are no longer unnecessary now * Leaving `load skylark rules` statement in the example may be misleading for newcomers Testing done: * re-compile bazel * use it to build example folder and run py target ``` shell ./compile.sh compile /usr/bin/bazel /home/yiyu/opt/bazel/output/bazel build //examples:all /home/yiyu/opt/bazel/output/bazel run //examples/py:bin ``` -- Change-Id: Icd82afff2b74e77c0bcc80687b04225baf28f6ad Reviewed-on: https://cr.bazel.build/9070 PiperOrigin-RevId: 148646895 MOS_MIGRATED_REVID=148646895
* Turn //tools/build_rules into a package.Gravatar Julio Merino2016-02-17
| | | | | | | | | This is in preparation for another change that will add a new helper script to the tools/build_rules directory, and such script requires a BUILD rule of its own. -- MOS_MIGRATED_REVID=114898083
* Use labels in load statementsGravatar Damien Martin-Guillerez2016-02-02
| | | | | | | | | | | | This will fix some issue with loading skylark rules from @bazel_tools. Tested with ./compile.sh all and also a project that use pkg_tar from @bazel_tools (which is broken at HEAD). -- Change-Id: Iffbb7134ef5fee497890c4d01b85084973d45ad0 Reviewed-on: https://bazel-review.googlesource.com/2800 MOS_MIGRATED_REVID=113508661
* Fix tests with python3 as default python.Gravatar Peter Foley2015-07-06
| | | | | | | | | | | If the system python interpreter is set to python3, some tests fail because python3 requires parenthesies for the print statement. Fix this by adding the required parenthesies, which are a no-op for python2. -- Reviewed-on: https://github.com/google/bazel/pull/282 MOS_MIGRATED_REVID=97571926
* Open-source Bazel integration testsGravatar Damien Martin-Guillerez2015-03-25
| | | | | | | | | It is a first batch of integration tests for Bazel. They tests some basic behaviors and nominal cases of Bazel rules (especially they tests the behavior of the examples provided in //examples). -- MOS_MIGRATED_REVID=89440074
* Move all examples into Bazel workspaceGravatar Damien Martin-Guillerez2015-03-24
Those examples will be used for Bazel integration tests and their sources should be available directly to the Bazel workspace itself. -- MOS_MIGRATED_REVID=89380736
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-17 11:06:26 +0000