← All tasks
pythonjupyter/jupyter_core #120Not a task: already works

__pycache__ in the wheel

envgap__jupyter__jupyter_core-120

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
51185b86423a370e62455211fe051fc569472513
Manifest
setup.cfg
Reproduce
Awaiting issue-specific recipe
Run under trace
Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

jupyter/jupyter_core #120 · read the original issue
In the wheel on PyPI there are the following directories:

```

jupyter_core/tests/__pycache__/

jupyter_core/tests/dotipython/profile_default/__pycache__/

jupyter_core/tests/dotipython_empty/profile_default/__pycache__/

```



Should they be there?



I noticed this because we only deploy `.pyc` files so after the pip install I pull the `.pyc` files out of `__pycache__` and into the location of the `.py` files using this script.



https://bitbucket.org/Siecje/restore_pyc/src/9834a5c2c16acf29b5b330ebd7590585bc20126b/restore_pyc.py?at=default&fileviewer=file-view-default



I noticed that the resulting `.pyc` had a different magic code. There is likely a bug in the `restore_pyc.py` script linked above as it should be finding the `.pyc` file that was created during the pip install.



But I figured I would report that there are `__pycache__` directories in the wheel.
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
[]