Raphaël Hertzog

@ederag I see that you have thought hard to support quite some corner case but I believe it's not the good trade off that you picked.

> 3. The main motivation was not to "satisfy user requests" (@mwilck never believes me, :sigh:), > but to get an interface as clean, user-friendly, and robust as the infrastructure....

@elbenfreund I have the same problem too here and I tracked it down to some calls that you incorrectly re-introduced when you updated the coding style. Please merge #296.

FWIW, this is caused by https://github.com/AdamLaurie/RFIDIOt/blob/4eaf194f764442befd1a4bde511a0cd4c193d28d/rfidiot/__init__.py#L194 and https://github.com/AdamLaurie/RFIDIOt/blob/4eaf194f764442befd1a4bde511a0cd4c193d28d/rfidiot/RFIDIOt.py#L100

Python 2.x will no longer be supported by their upstream developers in 2020. Thus Debian developers are actively removing Python 2 support in Debian Testing with the goal of getting...

Ah I see you already submitted the merge request here: https://github.com/EarToEarOak/RTLSDR-Scanner/pull/51

Hi, is there any plan to address this? Most distributions are busy to organize the switch to ffmpeg 5 and if ccextractor doesn't keep up, the package will end up...

> Yes, this will be a part of the HardsubX rewrite. While we are working on it, a short term solution would be to compile CCExtractor without HardsubX support. Thanks...

Forget this pkg_resources is part of setuptools... it's just that Debian packages this separately. I'm not sure that you have anything to do really.

Thinking a bit more I believe it would make sense for you to document the dependency on setuptools in requirements.txt / setup.py. I have seen other projects do this.