Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename blacklist #11

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

ericdill
Copy link

@ericdill ericdill commented Jun 6, 2020

Language matters.
https://twitter.com/leahculver/status/1269109776983547904
https://twitter.com/alessandramakes/status/1269116696834437121

I'd also be in ok with any of these *-list prefixes:

  • go / green / nice / safe
  • stop / red / naughty

This introduces a rename of blacklist -> denylist and whitelist -> allowlist. Backwards compatibility is enabled until such a time as we want to get rid of the backwards compat layer. In the warning message it says "until the next minor release", but that's sort of up to you all since you own the fork now.

@FaustinCarter
Copy link

As a frequent user of this package I strongly support this idea.

@codecov
Copy link

codecov bot commented Jun 7, 2020

Codecov Report

Merging #11 into master will decrease coverage by 1.08%.
The diff coverage is 80.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #11      +/-   ##
==========================================
- Coverage   90.36%   89.27%   -1.09%     
==========================================
  Files           3        3              
  Lines         415      429      +14     
==========================================
+ Hits          375      383       +8     
- Misses         40       46       +6     
Impacted Files Coverage Δ
conda_mirror/conda_mirror.py 87.30% <80.00%> (-1.37%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 15287b6...31ee5e2. Read the comment docs.

@xhochy
Copy link
Member

xhochy commented Jun 8, 2020

What about using the more common terms include and exclude?

@ericdill
Copy link
Author

ericdill commented Jun 8, 2020

@xhochy i'd be fine with those too

@analog-cbarber
Copy link

The code has changed enough that this pull request should be closed and do this over. I am definitely in favor of just using include and exclude. I think we should also support dependencies using the same format as in conda environment files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants