Installing a Python package from Github fails

[gkabbe]

When I try to install a Flit package from Github, for example via

flit installfrom github:takluyver/flit

Flit only complains with the following message:

Neither pyproject.toml nor flit.ini found, and no other config file path specified

This also happens if I specify the full URL (https://github.com/takluyver/flit)

[takluyver]

Oh, it's checking for that file before it goes into the installfrom subcommand. I think you can work around it by running the command from a directory that has a pyproject.toml file in. I'll fix it for the next release (and at some point, the installfrom command will be redundant once pip supports PEP 518).

[flying-sheep]

now we’re stuck between a rock and a hard place: this is still an issue and pip still doesn’t support PEP 518 fully (i.e. still expects setup.py)

[takluyver]

Paul Moore is working on PEP 517 support in pip.

But this is a separate issue: it should just skip the checks for the toml/ini files when you use installfrom.

[flying-sheep]

exactly. right now the situation is that you can’t install a flit-powered package directly from a git repo in one short command. The options are

1. git clone → pushd → flit install → popd → rm -rf (cumbersome)
2. add a flituptools-based setup.py (bloat, confusing presence of a otherwise unnecessary setup.py)
3. wait for this issue to be fixed and released (future)
4. wait for pip with PEP 517 support to be released (future)

Is #206 already enough?

[takluyver]

4. Cd to a directory containing project.toml, and use flit installfrom from there.

…

On Wed, 5 Sep 2018, 11:19 a.m. Philipp A., ***@***.***> wrote: exactly. right now the situation is that you can’t install a flit-powered package directly from a git repo in one short command. The options are 1. git clone → pushd → flit install → popd → rm -rf 2. wait for this to be fixed and released 3. wait for pip with PEP 517 support to be released — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#158 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAUA9Q03erOO0ygMMDzmzJ64lyzbXReGks5uX5cKgaJpZM4ReV1t> .

[flying-sheep]

true! but if #206 is enough, we could just quickly release 1.1.1 with that, right?