carloshatch/wi

Installer for Python Wheels

wi's Issues

Usage of format string literal necessitates Python 3.6

https://github.com/chromano/wi/blob/ee5ddf40c62a28524fa205143cb97d5e94792610/wi#L102

Since the usage is so trivial, it would be nice if a more backwards-compatible approach were used instead.

Support for manylinux

Currently, we are relying on the wheel module to find whether a .whl can be installed on the destination arch, however that module doesn't provide support for manylinux versions (i.e, it won't recognise packages distributed as such).

Allow to point to a private PyPI repo

At the moment the repo to pull from is hardcoded to be

PACKAGES_REPO_URL = 'https://pypi.python.org/pypi'

Allowing to connect to other repos will help a lot, ideally sharing the same argument options as pip (https://pip.pypa.io/en/stable/reference/pip/?highlight=trusted-host#cmdoption-trusted-host, https://pip.pypa.io/en/stable/reference/pip_wheel/#index-url ) for clarity

wi --index-url=http://my_own_repo.company.com --trusted-host my_own_repo.company.com

The trusted host is to avoid requiring https

Offline tests

In order to validate my rpm package, some sort of offline tests are needed.
https://build.opensuse.org/package/show/home:jayvdb:py-new/python-wi
Typical approach for pip tools is to use a fake pypi server, such as devpi.

Pick up dependencies from setup.py

It would be great if wi was able to pickup dependencies from setup.py instead of a requirements file.

Ideally with same extras syntax as pip, eg:

wi .[all]

Incompatible with wheel-0.33.6

[  162s] Traceback (most recent call last):
[  162s]   File "/home/abuild/rpmbuild/BUILDROOT/python-wi-0.0.2-lp151.4.1.x86_64/usr/bin/wi", line 28, in <module>
[  162s]     from wheel.install import WheelFile
[  162s] ModuleNotFoundError: No module named 'wheel.install'