bazel_rules_qt VS rules_python

Compare bazel_rules_qt vs rules_python and see what are their differences.

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
bazel_rules_qt rules_python
1 7
44 494
- 1.8%
0.0 9.5
about 2 years ago 3 days ago
Starlark Starlark
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

bazel_rules_qt

Posts with mentions or reviews of bazel_rules_qt. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-06-23.
  • Incremental Builds for Haskell with Bazel
    7 projects | news.ycombinator.com | 23 Jun 2022
    I migrated a mid-size polyglot project from Makefiles to Bazel and C++ was a large component of the project.

    Some obstacles:

    1. Building with QT5 MOC & UI files. There is a great library[0] for it but it has hardcoded paths to the QT binaries and header files assuming a system-wide installation. I had to patch the rule to point to our QT location. Then it worked fine.

    2. There is no rule to build a fully static library[1]. Since we were shipping a static library in our Makefile system, that was somewhat annoying.

    3. We were using system links like `$PROJECT_ROOT/links/GCC/vX.Y.Z/ -> /opt/gcc/...` to point to all the build tools, but these didn't work in Bazel I think because it required absolute paths for any binaries it calls. We ended up putting them in a .bazelrc but we would need a different one for Windows and Linux.

    4. Not good integration with IDEs

    Ultimately we did not keep using Bazel because we were building Python binaries and py_binary was too slow on Windows. And we didn't have enough time to write a PyInstaller rule.

    [0]: https://github.com/justbuchanan/bazel_rules_qt

    [1]: https://github.com/bazelbuild/bazel/issues/1920

rules_python

Posts with mentions or reviews of rules_python. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-10-24.
  • Things I've learned about building CLI tools in Python
    16 projects | news.ycombinator.com | 24 Oct 2023
    What's SV?

    I honestly don't know why anyone would use that... as in what does Bazel do better than virtually anything else that can provide this functionality. But, I used to be an ops engineer in a big company which wanted everything to be Maven, regardless of whether it does it well or not. So we built and deployed with Maven a lot of weird and unrelated stuff.

    Not impossible, but not anything I'd advise anyone to do on their free time.

    Specifically wrt' the link you posted, if you look here: https://github.com/bazelbuild/rules_python/blob/main/python/... it says that only pure Python wheels are supported, but that's also a lie, they don't support half of the functionality of pure Python wheels.

    So, definitely not worth using, since lots of functionality is simply not there.

  • Python coverage in Bazel has been broken for nearly 6 years
    1 project | news.ycombinator.com | 19 Aug 2023
  • Build faster with Buck2: Our open source build system
    14 projects | news.ycombinator.com | 6 Apr 2023
    Regarding bazel, the rules_python has a py_wheel rule that helps you creating wheels that you can upload to pypi (https://github.com/bazelbuild/rules_python/blob/52e14b78307a...).

    If you want to see an approach of bazel to pypi taken a bit to the extreme you can have a look at tensorflow on GitHub to see how they do it. They don't use the above-mentioned building rule because I think their build step is quite complicated (C/C++ stuff, Vida/ROCm support, python bindings, and multiOS support all in one before you can publish to pypi).

  • Incremental Builds for Haskell with Bazel
    7 projects | news.ycombinator.com | 23 Jun 2022
    Python support in Bazel now looks more promising with `rules_python`: https://github.com/bazelbuild/rules_python

    `rules_go` to my understanding is great too.

    Over years, Bazel is not as opinionated as before, mostly because adoptions in different orgs force it to be so.

  • Advantages of Monorepos
    6 projects | news.ycombinator.com | 7 Apr 2022
    I have personally run converted build systems to Bazel, and use it for personal projects as well.

    Bazel 1.0 was released in October 2019. If you were using it "a few years ago", I'm guessing you were using a pre-1.0 version. There's not some cutoff where Bazel magically got easy to use, and I still wouldn't describe it as "easy", but the problem it solves is hard to solve well, and the community support for Bazel has gotten a lot better over the past years.

    https://github.com/bazelbuild/rules_python

    The difficulty and complexity of using Bazel is highly variable. I've seen some projects where using Bazel is just super simple and easy, and some projects where using Bazel required a massive effort (custom toolchains and the like).

  • Experimentations on Bazel: Python & FastAPI (1)
    5 projects | dev.to | 18 Apr 2021
    load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive") #------------------------------------------------------------------------------ # Python #------------------------------------------------------------------------------ # enable python rules http_archive( name = "rules_python", url = "https://github.com/bazelbuild/rules_python/releases/download/0.2.0/rules_python-0.2.0.tar.gz", sha256 = "778197e26c5fbeb07ac2a2c5ae405b30f6cb7ad1f5510ea6fdac03bded96cc6f", )

What are some alternatives?

When comparing bazel_rules_qt and rules_python you can also consider the following projects:

toolchains_llvm - LLVM toolchain for bazel

uwsgi-nginx-flask-docker - Docker image with uWSGI and Nginx for Flask applications in Python running in a single container.

gcc-toolchain - A fully-hermetic Bazel GCC toolchain for Linux.

black - The uncompromising Python code formatter

nixpkgs - Nix Packages collection & NixOS

pip-upgrade - Upgrade your pip packages with one line. A fast, reliable and easy tool for upgrading all of your packages while not breaking any dependencies

llvm-project - The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.

python-streams - A Library to support Writing concise functional code in python

bazel-coverage-report-renderer - Haskell rules for Bazel.

TypeRig - Proxy API and Font Development Toolkit for FontLab

rules_pyenv - Bazel rules for pyenv (simple python version management)

catwiki - CatWiki is a simple wiki that stores its articles as text files