Re: Warning: Your Pyzor may be broken.

On 6/9/24 7:31 PM, John Hardin wrote:
> On Sun, 9 Jun 2024, Michael Orlitzky wrote:
> 
>> On 2024-06-08 14:45:34, Bill Cole wrote:
>>
>>> I went looking for a better fix and found a reported issue at
>>> https://github.com/SpamExperts/pyzor/issues/155 matching my original
>>> symptoms in which a workaround was provided: install directly from
>>> the GitHub project's master.zip link, i.e. a snapshot assembled from
>>> the current state of the repo, which claims to be v1.1.1. I do not
>>> like that solution at all, and added a comment to that issue
>>> suggesting that they fix the problem by cutting a release for
>>> PyPI. No response yet, but it has only been a matter of minutes.
>>
>> The same issue was reported in 2016 and ignored for eight years before
>> being closed out of frustration (rather than because they did
>> something about it):
>>
>>  https://github.com/SpamExperts/pyzor/issues/54
> 
> Perhaps the project should consider retiring Pyzor as "no longer effectively maintained"?
> 
I think this is a valid option, Perl implementation is a reverse engineering effort and absolutely not perfect.
  Giovanni

-----BEGIN PGP SIGNATURE-----

wsF5BAABCAAjFiEEqg3TnG6R3qYMxl94+r7qCYlyWOUFAmZm+g4FAwAAAAAACgkQ+r7qCYlyWOWY
FQ//aKEDtZCU7kdZ+3qtFryqVB1s3MnRi7CXOVtglTsXF72rW2SfhaUGSfHilVERfzH0IFed7E87
o8P1bcrc2qj3sf7MCSzoKGPyzXCS0tKP9ZGMZxsx59bzrZHmJzTFzUXa9NQv+boEPGI/uGRQiZNW
i81Uv46YH98pJZTQ4eLeYh84fsXRc9xFcb7CHBmDxNvAU99jF/XRtEtgUZyMUTs+Yw8jDJIduIFV
WVoQ/rKyeypO1AdWK3FMr9iHeImWaVQX3otzxhnNzX5MuY7sDhRFhvesJ43GmbYpCMsQvQQmNqAW
0STkC4SrV/oni7iMLIwGUvdrZp7+0vFI1eGY7nJ0sIjrhR2ax5f9N3YmgS1XR+C63zNRg4I5nE3l
KK63TwY90pg4EXchi/dlhETQbWJNyOISx/IMw4Yezr6MnkFB1nExzgXJS5SITIom05ckteIVQZq3
ZIdO7YkDoyyB0qlsouWZKggEgmwTUS9ejVK+tuMcDqSYpa+Mf1pdVTWRi+dohYZFWJJbbojQpJ3s
EZL0twZ8yjNm9/knsGZTgWsL+hVd74PqdsjnGLgV2mP8PvqOP/aRi4cGGlsd1q5nga92ziZV8l/D
+OMK9k9WOSd36uGotRuzW6EihszZAzXMdokd0xtMvymoY32yZUXFd7hyUA8/QWyN05Yjq16kKRmW
Tyg=
=ilUT
-----END PGP SIGNATURE-----