search

dephell / dephell_archive

Pathlib for archives
MIT License
1 stars 6 forks source link

Installation using pip 19.3.1 using git+ fails #10

Open jayvdb opened 4 years ago

jayvdb commented 4 years ago

./bin/pip install 'git+https://github.com/dephell/dephell works, but the same doesnt work here 'git+https://github.com/dephell/dephell_archive' because it doesnt have a setup.py/.cfg/etc. I appreciate that you likely dont want to create these files for all repos, but maybe there is a workaround, or possibly a new dephell tool?.

./bin/pip install 'git+https://github.com/dephell/dephell_archive'
Collecting git+https://github.com/dephell/dephell_archive
  Cloning https://github.com/dephell/dephell_archive to /tmp/pip-req-build-ozd9kiqg
  Running command git clone -q https://github.com/dephell/dephell_archive /tmp/pip-req-build-ozd9kiqg
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
    Preparing wheel metadata ... done
Building wheels for collected packages: UNKNOWN
  Building wheel for UNKNOWN (PEP 517) ... done
  Created wheel for UNKNOWN: filename=UNKNOWN-0.0.0-cp37-none-any.whl size=1788 sha256=2fbed720ce0681e2e09b4da90a395e31ee224dd3ad086344d4fd1b83b12fa6f0
  Stored in directory: /tmp/pip-ephem-wheel-cache-mfoqfw4o/wheels/1d/e9/34/a547e91f29439fb316449bcc47f1738c9264b2706e352fd0d9
Successfully built UNKNOWN
Installing collected packages: UNKNOWN
Successfully installed UNKNOWN-0.0.0

lib/python3.7/site-packages/UNKNOWN-0.0.0.dist-info/top_level.txt is empty, so nothing was installed.

Likely there is an upstream issue in pip project about it, worth finding and tracking.

jayvdb commented 4 years ago

I will have an update for this in a few days. (related to https://github.com/dephell/dephell_specifier/issues/13, https://github.com/dephell/dephell_pythons/pull/8 and https://github.com/dephell/dephell_shells/pull/3)

orsinium commented 4 years ago

I'm going to make PEP-518 interface for DepHell, it will solve such cases

jayvdb commented 4 years ago

@orsinium , any progress with the PEP-518 interface? Is it an existing issue/PR for that?

I guess this could be solved by adding adding a poetry PEP-517 handler into pyproject.toml for each @dephell project, like

[build-system]
requires = ["poetry>=0.12"]
build-backend = "poetry.masonry.api"

fwiw, I have built https://github.com/jayvdb/pypidb to make it possible to generically build tools that bridge the gap between PyPI name and SCM.