pythonmpdavis/python-jose #161Not a task: already works

Cannot run setup.py if setup.py is not in sys.path

envgap__mpdavis__python-jose-161

Original GitHub issue ↗Dated source checkout ↗Opened 2019-12-14

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not a benchmark task.

The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit: 13903924ef952e8b247127088ae6eb824bac7dee
Manifest: setup.cfg
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

mpdavis/python-jose #161 · read the original issue

`setup.py` can only currently be run if the `jose` can be imported. It is presumably assumed that the source root will be somewhere near the top of `sys.path` but this is not always the case. 



There are, therefore, two failure modes possible. If `python-jose` is not already installed, `setup.py` cannot be run at all. If `python-jose` _is_ installed, then the version from the installed copy is used to generate the version for `setup.py`.



Switching to using `setup.cfg`:

```

[metadata]

version = attr: jose.__version__

```

allows `setup.py` to be run even if the source root is not on the path.

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]