Key | Value |
---|---|
FileName | ./usr/share/doc/python3-dacite/copyright |
FileSize | 1421 |
MD5 | 6040EBD21CD2098EA557081A1F533451 |
SHA-1 | 7DB53DAD41D900AD45509AA14BD401A73F30138D |
SHA-256 | 9DA14948B82537B7E367DE7BDE7B80920D7622F6AC26950A15A9648B95CF29BE |
SSDEEP | 24:gttcgUVFCsruPJH/H0ymS3gt8xLHc1hMK9QH0sUv4kOk4/+/U3oq4sFig:fgUVF/0Jvlm6Er5QH0s5ANU3oWFig |
TLSH | T18621E91B738007551A8A23D06679ACD4B737714DF45F9EC4942DE3045B19079D0FB424 |
hashlookup:parent-total | 3 |
hashlookup:trust | 65 |
The searched file hash is included in 3 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
FileSize | 18172 |
MD5 | C5DFF01E66CEF189845174B5C303D9EA |
PackageDescription | Simple creation of data classes from dictionaries Passing plain dictionaries as a data container between your functions or methods isn't a good practice. Of course you can always create your custom class instead, but this solution is an overkill if you only want to merge a few fields within a single object. . Fortunately Python has a good solution to this problem - data classes. Thanks to `@dataclass` decorator you can easily create a new custom type with a list of given fields in a declarative manner. Data classes support type hints by design. . However, even if you are using data classes, you have to create their instances somehow. In many such cases, your input is a dictionary - it can be a payload from a HTTP request or a raw data from a database. If you want to convert those dictionaries into data classes, `dacite` is your best friend. . This library was originally created to simplify creation of type hinted data transfer objects (DTO) which can cross the boundaries in the application architecture. . It's important to mention that `dacite` is not a data validation library. There are dozens of awesome data validation projects and it doesn't make sense to duplicate this functionality within `dacite`. If you want to validate your data first, you should combine `dacite` with one of data validation library. |
PackageMaintainer | Debian Python Team <team+python@tracker.debian.org> |
PackageName | python3-dacite |
PackageSection | python |
PackageVersion | 1.6.0-1 |
SHA-1 | 0E47699A8D5DF4DC5B91678924306156FC275676 |
SHA-256 | 9BAB56D650F37550AD90818DC6FF4AFEFAF1818968C205D4E27E56323685A6C0 |
Key | Value |
---|---|
FileSize | 17088 |
MD5 | 3D1D9FEF147CCE949AE5EFB93FDF21D5 |
PackageDescription | Simple creation of data classes from dictionaries Passing plain dictionaries as a data container between your functions or methods isn't a good practice. Of course you can always create your custom class instead, but this solution is an overkill if you only want to merge a few fields within a single object. . Fortunately Python has a good solution to this problem - data classes. Thanks to `@dataclass` decorator you can easily create a new custom type with a list of given fields in a declarative manner. Data classes support type hints by design. . However, even if you are using data classes, you have to create their instances somehow. In many such cases, your input is a dictionary - it can be a payload from a HTTP request or a raw data from a database. If you want to convert those dictionaries into data classes, `dacite` is your best friend. . This library was originally created to simplify creation of type hinted data transfer objects (DTO) which can cross the boundaries in the application architecture. . It's important to mention that `dacite` is not a data validation library. There are dozens of awesome data validation projects and it doesn't make sense to duplicate this functionality within `dacite`. If you want to validate your data first, you should combine `dacite` with one of data validation library. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | python3-dacite |
PackageSection | python |
PackageVersion | 1.5.1-1 |
SHA-1 | AE2C306F33660AD48B81369C8399A4408CD0546F |
SHA-256 | 766D8A4B306472E90BB5C34352DBC09EC5C44E86954890BBD10ED637F46540FB |
Key | Value |
---|---|
FileSize | 17432 |
MD5 | 78BFA38216BDFFFBC8B1CD9B12CA2766 |
PackageDescription | Simple creation of data classes from dictionaries Passing plain dictionaries as a data container between your functions or methods isn't a good practice. Of course you can always create your custom class instead, but this solution is an overkill if you only want to merge a few fields within a single object. . Fortunately Python has a good solution to this problem - data classes. Thanks to `@dataclass` decorator you can easily create a new custom type with a list of given fields in a declarative manner. Data classes support type hints by design. . However, even if you are using data classes, you have to create their instances somehow. In many such cases, your input is a dictionary - it can be a payload from a HTTP request or a raw data from a database. If you want to convert those dictionaries into data classes, `dacite` is your best friend. . This library was originally created to simplify creation of type hinted data transfer objects (DTO) which can cross the boundaries in the application architecture. . It's important to mention that `dacite` is not a data validation library. There are dozens of awesome data validation projects and it doesn't make sense to duplicate this functionality within `dacite`. If you want to validate your data first, you should combine `dacite` with one of data validation library. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | python3-dacite |
PackageSection | python |
PackageVersion | 1.6.0-1 |
SHA-1 | A9117DD0A722F531DAC6708FFD15B4DA3D822992 |
SHA-256 | E9B11CB01AB11131771F116A903B5AD0333D8CEDA5D48BF09F4A267BF01064F1 |