Exit code l0 is a non-sysexits compliant code

[alanhamlett]

Exit code l0 is a non-sysexits compliant code

[alanhamlett]

Fixed with 51074bb.

[alanhamlett]

It does default to zero exit code on success, and non-zero on error. The only time exit code 10 is used is when --nonzero-exit-code is present, so scripts can use the exit code when they need to know if packages were updated or not. This feature was added with #5.

[kkirsche]

Which doesn’t align with tools like black in check mode. The idea would be that even in non zero exit code you would still use 0 when no update is required. As such, why is 10 used instead when all is good and it was successful. It makes sense to return something when packages need an update but not when it ran successfully and it doesn’t have any packages to update

[alanhamlett]

Oh, got it. We can change that in a major release to exit zero when everything is up to date.

[alanhamlett]

@kichik and @pradyunsg, before we change the nonzero exit code behavior to exit with 0 instead of 10 when no packages were updated, I want to check with you first. Would 0 exit code work for you? The 11 exit code would still be used when --nonzero-exit-code present and any packages needed updating.

[pradyunsg]

I'm not sure why I've been mentioned here. I have no clue what this discussion is about. :)

[kichik]

Sorry for the very late reply, but I just now realized why you asked me and @pradyunsg and it's because of issue #5. I no longer use pur, so the change doesn't affect me. Thanks for checking!