Biip

Latest version: v3.5.2

Safety actively analyzes 687881 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 6

2.2.1

Bug fixes

- Fix `.without_variable_measure()` for 14-digit RCNs. This bug was introduced in the RCN refactoring in Biip 2.2.0. (PR: 132)

If you're using Biip, please add yourself to the [list of users](https://github.com/jodal/biip/wiki/Users)!

2.2.0

Changes

- Drop Python 3.6 support, as it has reached end-of-life. This is not considered a breaking change as Python 3.6 users will get the previous release when install Biip. (PR: 118)
- Deprecate `RcnRegion.from_iso_3166_1_numeric_code()` as this functionality is deemed out of scope for Biip. The method will be removed in Biip 3.0. (PR: 130)
- RCN: Add support for extracting weight/price/count and normalizing RCNs from:
- Denmark (PR: 126)
- Germany (PR: 129)

If you're using Biip, please add yourself to the [list of users](https://github.com/jodal/biip/wiki/Users)!

2.1.0

Changes

- Add support for parsing and validating Global Location Numbers (GLNs). This also includes GLNs embedded in GS1 Element Strings. (PR: 108)
- Add Python 3.10 to the test matrix. (PR: 105)

If you're using Biip, please add yourself to the [list of users](https://github.com/jodal/biip/wiki/Users)!

2.0.0

This release contains a couple of breaking changes, thus the version bump to 2.0.

Breaking changes

- When a prefix looks valid but cannot be found in Biip's list of known GS1 Prefixes `GS1Prefix.extract()` now returns `None` instead of raising an exception. (Fixes: 93, PR: 94)
- Following from the above, `Gtin.prefix` and `Sscc.prefix` can now be `None`. This makes it possible to parse and validate GTINs and SSCCs with prefixes missing from Biip's list of known GS1 Prefixes. (Fixes: 93, PR: 94)
- The deprecated RCN region `RcnRegion.BALTICS` has been removed. Use `ESTONIA`, `LATVIA`, or `LITHUANIA` instead. (PR: 100)

Bug fixes

- Parsing a GTIN-14 can no longer return the `Rcn` subclass. RCN is only defined for GTIN-8, GTIN-12, and GTIN-13. (PR: 96)
- `Rcn.without_variable_measure()` no longer zeroes out digits from RCNs without variable measures. (PR: 97)

Changes

- Added a no-op method `Gtin.without_variable_measure()` so that `Gtin` and `Rcn` instances can be used interchangeably in more cases. This should reduce the need for `isinstance(gtin, Rcn)` checks.
- The RCN rules are now defined in a declarative data structure, making it a lot easier to contribute RCN rules for new geographical regions. (PR: 98)
- Added `FINLAND` as a supported RCN region. (PR: 95)

If you're using Biip, please add yourself to the new [list of users](https://github.com/jodal/biip/wiki/Users)!

1.2.0

This release improves the RCN region support:

- Add `RcnRegion.ESTONIA`, `RcnRegion.LATVIA`, and `RcnRegion.LITHUANIA`. All follow the same rules as `RcnRegion.BALTICS`.
- Deprecated `RcnRegion.BALTICS`. Even though Estonia, Latvia, and Lithuania share the same RCN rules, they're different RCN regions. This means that RCNs can be reused within the different countries in the Baltics. To encourage the correct modeling of this, `RcnRegion.BALTICS` will be removed in a future version of Biip, and all users are encouraged to be more specific and use one of the newly added regions instead.
- Add `RcnRegion.from_iso_3166_1_numeric_code()` to make it easy to get the correct `RcnRegion` instance from an ISO 3166-1 country code, like 578 for Norway.

If you're using Biip, please add yourself to the new [list of users](https://github.com/jodal/biip/wiki/Users)!

1.1.0

- This release adds extended support for UPC, especially the UPC-E format. (Fixes: 77, PR: 78)

- Parse 12-digit UPC-A. This is the same as GTIN-12, so it is strictly already supported.
- Parse 6-digit UPC-E, with implicit number system 0 and no check digit.
- Parse 7-digit UPC-E, with an explicit number system and no check digit.
- Parse 8-digit UPC-E, with an explicit number system and a check digit.
- Expand UPC-E to UPC-A.
- Suppress UPC-A to UPC-E, for the values where it is supported.

- The top-level parser has been slightly changed so that the first successful parse result from each parser is the result that is kept. E.g. if parsing a number that is both a valid GTIN-8 and UPC-E, the `gtin` field will contain the result of parsing it as GTIN-8, not the result of expanding the UPC-E result to a UPC-A (which is the same as GTIN-12) set in the `gtin` field.

If you're using Biip, please add yourself to the new [list of users](https://github.com/jodal/biip/wiki/Users)!

Page 3 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.