I suspect we'll need a more actively maintained docs tool that supports
versions etc in future. Unfortunately Sphinx and Pydoc both seem more
heavyweight than I'd like right now, and I can't find any other great
options.
Signed-off-by: Nic Cope <nicc@rk0n.org>
I _think_ this should push to PyPI only when the CI workflow is run with
a version input, similar to how builds work for functions.
Signed-off-by: Nic Cope <nicc@rk0n.org>
without this change, running 'hatch build' in my environment (Ubuntu LTS
22.04) fails with:
File
"/home/jo.diaz/.local/share/hatch/env/virtual/function-sdk-python/wwDZoZBv/function-sdk-python-build/lib/python3.11/site-packages/hatchling/builders/wheel.py",
line 231, in default_only_include
return self.default_file_selection_options.only_include
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File
"/home/jo.diaz/.pyenv/versions/3.11.6/lib/python3.11/functools.py", line
1001, in __get__
val = self.func(instance)
^^^^^^^^^^^^^^^^^^^
File
"/home/jo.diaz/.local/share/hatch/env/virtual/function-sdk-python/wwDZoZBv/function-sdk-python-build/lib/python3.11/site-packages/hatchling/builders/wheel.py",
line 219, in default_file_selection_options
raise ValueError(message)
ValueError: Unable to determine which files to ship inside the wheel
using the following heuristics:
https://hatch.pypa.io/latest/plugins/builder/wheel/#default-file-selection
At least one file selection option must be defined in the
`tool.hatch.build.targets.wheel` table, see:
https://hatch.pypa.io/latest/config/build/
As an example, if you intend to ship a directory named `foo` that
resides within a `src` directory located at the root of your project,
you can define the following:
[tool.hatch.build.targets.wheel]
packages = ["src/foo"]
with the change, the build succeeds
Signed-off-by: Joel Diaz <jo.diaz@celonis.com>
renovate[bot]
Nic Cope
Bob Haddleton
Joel Diaz