5 Commits (de0330a07c9f8608ea3079eb77e565b2766690d0)

Author	SHA1	Message	Date
implr	cae27ecd99	Replace rules_pip with rules_python; use bazel built upstream grpc ... instead of Python packages As usual with Python sadness, the @pydeps wheels are built on the bazel host, so stuffing them inside a container_image (or py_image) will cause new and unexpected kinds of misery. Change-Id: Id4e4d53741cf2da367f01aa15c21c133c5cf0dba	2020-07-08 18:55:34 +02:00
Serge Bazanski	cd0e01bb7a	third_party/py: add wtforms ... Change-Id: Iabb4fa35ee9369aa0c6592d18fbe69855edf0c7f	2019-12-19 18:29:45 +01:00
Serge Bazanski	d828c685ce	third_party/py: add cockroachdb ... Change-Id: I0c2f1e820b67bdebc98dd58429048c8a89d37416	2019-12-19 14:44:56 +01:00
q3k	43189235bd	third_party/py: add flask-spaceauth deps ... Change-Id: I3e153f8992b2a987ce2b0e1db8f869f6cca40f4b	2019-12-18 14:11:00 +01:00
q3k	5f9b1ecd67	rules_pip: update to new version ... rules_pip has a new version [1] of their rule system, incompatible with the version we used, that fixes a bunch of issues, notably: - explicit tagging of repositories for PY2/PY3/PY23 support - removal of dependency on host pip (in exchange for having to vendor wheels) - higher quality tooling for locking We update to the newer version of pip_rules, rename the external repository to pydeps and move requirements.txt, the lockfile and the newly vendored wheels to third_party/, where they belong. [1] - https://github.com/apt-itude/rules_pip/issues/16 Change-Id: I1065ee2fc410e52fca2be89fcbdd4cc5a4755d55	2019-09-25 14:05:07 +02:00