Bug#970901: black: cannot run, "ModuleNotFoundError: No module named '_black_version'"

2020-10-06 Thread Nicholas D Steeves
Control: block 971214 by -1 While investigating 971214 in an i386 chroot I encountered this bug, thus at this point my hypothesis is that 970901 is causing Elpy's callback to error. 'hope to see it fixed soon! Thank you, Nicholas signature.asc Description: PGP signature

Processed: Re: Bug#970901: black: cannot run, "ModuleNotFoundError: No module named '_black_version'"

2020-10-06 Thread Debian Bug Tracking System
Processing control commands: > block 971214 by -1 Bug #971214 [src:elpy] elpy: FTBFS: tests failed 971214 was not blocked by any bugs. 971214 was not blocking any bugs. Added blocking bug(s) of 971214: 970901, 971131, and 971137 -- 970901:

Bug#970901: black: cannot run, "ModuleNotFoundError: No module named '_black_version'"

2020-09-26 Thread Chris Lamb
tags 970901 + patch thanks Hi, > black: cannot run, "ModuleNotFoundError: No module named '_black_version'" The following patch works for me, but there is likely a cleaner solution; seems like the Black package maintainers are doing special things with the version handling and I am missing some

Bug#970901: black: cannot run, "ModuleNotFoundError: No module named '_black_version'"

2020-09-25 Thread Nicolas Noirbent
Package: black Version: 20.8b1-1 Severity: grave Justification: renders package unusable Dear Maintainer, The new black package version 20.8b1-1 seems to be missing some files: % black Traceback (most recent call last): File "/usr/lib/python3/dist-packages/black/__init__.py", line 63, in