-
-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unwanted behaviour of the no_checksum option for EuropeanArticleNumber13 #43
Comments
Bump.
instead of |
Can you confirm if #98 fixes the issue for you? If so, I'll add some tests and merge it in. Thanks! |
I am too lazy to figure out how to build/install it :D But yeah, looks correct. Maybe adding some validation for the number of digits would be good.
hm, I did not have any crashes. 🤔 |
hello, is this bug fixed? i tried python-barcode 0.14.0 on windows 10 py 3.9.0, the last digit/checksum can not be disabled
|
The `ean` variable was shadowed early, so a custom 13th digit was lost when ignoring checksums. Fixes: #43
The `ean` variable was shadowed early, so a custom 13th digit was lost when ignoring checksums. Fixes: #43
The `ean` variable was shadowed early, so a custom 13th digit was lost when ignoring checksums. Fixes: #43
The `ean` variable was shadowed early, so a custom 13th digit was lost when ignoring checksums. Fixes: #43
If the no_checksum option is passed, A 13 digits code should be accepted as it is.
At the moment, the last digit is replaced by a 0 and it cannot be otherwise:
len(ean) > self.digits
is never going to happenThe text was updated successfully, but these errors were encountered: