Richard Levasseur

Allow repository_ctx.extract to be told the file type explicitly

1

### Description of the feature request: I have some zip files that don't have a .zip extension (Python `.whl` files). In order to extract them, I have to create a...

Allow using arbitrary wheel files with arbitrary constraints in pypi integration

5

Sometimes you want to use a custom wheel that can't be represented by Python packaging constraints, or simply want to use a particular whl at a particular location for your...

doc how to access entry points / bin / scripts from wheels

1

In a non-bazel venv, distributions make executables available by putting them in `$venv/bin`, which gets added to PATH. In older versions of rules python, py_binary's were generated for these. It...

doc how to setup dev vs non-dev pypi dependencies

1

It's common for projects to have dev-only dependencies. We should document how to do similar using pip.parse. The basic steps are: * Have a separate `@dev_pypi` hub * Separate requirements.txt...

sphinxdocs: implement a persistent worker mode

1

Right now, sphinxdocs runs as a fresh process every time. For iterative development, this adds unnecessary overhead in the setup and execution of sphinx. It also creates barriers to make...

sphinxdocs: implement content-based change detection plugin

1

Sphinx has change detection to facilitate incremental rebuilding, but it's timestamp based. Bazel doesn't reliably preserve timestamps, nor are timestamps highly reliable, so this functionality isn't usable. This means sphinx...

Remove automatic __init__.py generation (set incompatible_default_to_explicit_init_py to true)

1

The automatic generation of `__init__.py` files has been a source of odd, surprising, and incorrect behavior. e.g. it makes directories importable that shouldn't be importable. This is because it's logic...

Right now, repo roots are added to sys.path. This is problematic for a variety of reasons * It causes the repos with external pip deps to end up on sys.path,...

Currently, the PyInfo's imports field returns all imports paths defined in a target, combined with the ones from its transitive dependencies, as defined here There's no way to retrieve the...

GitHub actions support specially formatted output that can then show up in the ui: https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions#setting-a-warning-message So the idea would be: have a bazel flag and/or sphinx plugin that transforms warning/error...