Strict dependency on black prevents usage of the latest black
See original GitHub issuepipenv-setup
depends on black==19.10b0
, while the latest black version is 20.8b1
. This prevents the usage of pipenv-setup
in any project which requires the latest black version (downgrading black
is not an option, because 19.10b0
complains about formatting of the files 20.8b1
is happy with).
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:19 (10 by maintainers)
Top Results From Across the Web
Black/African American - SAMHSA
The Opioid Crisis and the Black/African American Population: An Urgent Issue This issue brief provides an overview of the contextual factors influencing opioid ......
Read more >Black specifies a requirement for click>=7.1.2 but ... - GitHub
The specific use case I have for this is I need to run black on in different processes at the same time. There...
Read more >The Black code style - Black 22.12.0 documentation
The coding style used by Black can be viewed as a strict subset of PEP 8. Black reformats entire files in place. It...
Read more >Less Drinking, Yet More Problems: Understanding African ...
Sempos and colleagues (2003) reported there were no beneficial effects of moderate alcohol consumption, especially for African American men.
Read more >EDR: Dependency issues when installing Server packages
Environment EDR Server: 6.3.x RedHat Linux (RHEL): 7.x or CentOS 7.x Symptoms Running yum install cb-enterprise stops with message Error: Package:
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@jshwi I think #88 is about setup now. It ended up taking a while to work out the
usage.yml
workflow, but I believe it tests what we want to test in order to close this issue.When resolving the failing tests, I’ll also take a swing at calling a function provided by
black
; it shouldn’t take much 🙂I think its possible to call
black.__main__.main
, or it has a main function called_patched_main
or something. On that last point, sounds like there is a solution. tbh, never gotautopep8
to work a few years ago, so gave up on it. I like pep8, personally, so I wanted to make it work. If black never releases this mythical stable release and pipenv can’t find a compromise, a new formatter would be the go lol.