Skip to content
This repository has been archived by the owner on Feb 1, 2023. It is now read-only.

Remove pyproject causing pip install issues #54

Merged
merged 2 commits into from
Sep 8, 2020
Merged

Conversation

skovhus
Copy link
Contributor

@skovhus skovhus commented Sep 8, 2020

On some system the pip install step will fail if we have the pyproject.toml file (currently only used for configuring Black)... There is more context here:

As Black only supports using pyproject for configuration, the best option seems to be duplicating the config and provide it as CLI arguments.

Another option is to force users to install with the "--no-use-pep517" (which also works, but isn't as nice for the end user).

On non pep517 ready systems having the pyproject will fail... As Black only allows for using the pyproject file the best option seems to duplicate the config...

Another option is to force users to install with the "--no-use-pep517"
Copy link
Member

@madsnedergaard madsnedergaard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, as long as it's only so few arguments I think defining and duplicating like this is okay :)

@skovhus skovhus merged commit 8bb6a25 into master Sep 8, 2020
@skovhus skovhus deleted the ks/remove-pyproject branch September 8, 2020 10:37
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants