Remove all configuration from Tox file #165
No reviewers
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#165
Loading…
Reference in New Issue
No description provided.
Delete Branch ":cifix/tox-remove-config"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This puts tool configuration in their familiar and standard locations and simplifies the Tox configuration to just laying out the environments and factors.
This also allows users who do not want to deal with overhead of Tox (for whatever reasons ...) to run pytest/black/etc. and have the same behaviour.
Opened up witten/borgmatic#166 for a discussion on "officially" supporting more versions.
CI failure is quite an annoying ...
See https://github.com/pypa/pip/issues/6434.
I'll add the recommended work-around.
@ -0,0 +1,4 @@
[tool.black]
line-length = 100
target-version = ['py37']
Doesn't that mean the output formatted files will only support Python 3.7? I think the default behavior when this option is omitted is probably fine. From the black docs: "default: per-file auto-detection". Alternatively, if that's not good enough, 'py35' probably works as a target version here.
@ -0,0 +1,4 @@
[tool.black]
line-length = 100
target-version = ['py37']
skip-string-normalization = true
What on Earth is a
pyproject.toml
file? Seems like I'm not the first person to ask that question.hehe ... "the future" apparently ...
Thank you so much for doing this! Looks like a good improvement.
Cool! Comments addressed 👍
Looks like the work-around doesn't work on older versions of pip:
Hmmmm ... some notes in https://pypi.org/project/tox-pip-version/.
Do you expose
VIRTUALENV_NO_DOWNLOAD=1
? It should get the latest ...Not using
VIRTUALENV_NO_DOWNLOAD
. I thought any given virtualenv pins a particular version of pip?Well, it's not pretty, but this appears to work: witten/borgmatic#175