Key | Value |
---|---|
FileName | ./usr/share/doc/python3-dacite/changelog.Debian.gz |
FileSize | 599 |
MD5 | 6AD33EAAB0E13705C050FC936E5094C7 |
SHA-1 | 53785FF38ED9C4370E5DF77B70E9C238ADDA6800 |
SHA-256 | CD1EB34B70296AC8A9BC6D2C2D2D5A9B5EEDE47F254F5779B512F2C79B795B8C |
SSDEEP | 12:XEBYbl2ejlcTbghU3qlRVleM8htYF0mpi4d+57XPcuOdBeThyGwww2phRY:XJBjlI58b8M8zQJi7TUukBMMGXw2pM |
TLSH | T186F096F40F65CB39C0A86002225C22F053FF8A0524CE52CF60A8E3FF426A165D62139B |
hashlookup:parent-total | 2 |
hashlookup:trust | 60 |
The searched file hash is included in 2 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 | 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 |