Key | Value |
---|---|
FileName | ./usr/share/doc/python3-dacite/changelog.gz |
FileSize | 750 |
MD5 | 3272D3DFD54B35CB6FD3A0FF3289B671 |
SHA-1 | 6D724909DB94F404ED2B4BB331139470F81EEFD4 |
SHA-256 | 89CD7997247FF9A69227634FEED8792BF01329D82FC5AAFE6D9AEE4ED9842317 |
SSDEEP | 12:XnUW8jSqVocR/rNH3/zMj2i8Y53wyTl2Fk9++yHKo9mT9v38ZcqSHQnUB6dEWYo0:XndJuocR/xX/Yj25YmQl26+/p9mT98Zu |
TLSH | T11901B58C72437690BC225DFA5169012428BCDDB2EBD63069C3D324AD4513822441A4B0 |
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 | 18120 |
MD5 | CBE5038AAB36813A46AE13E10D314C5D |
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-2 |
SHA-1 | E0C655470839C7501F769E9724F8A0B6852ACA1B |
SHA-256 | 46BA7E7417B95AE7AFDAA60FD155E4B53439EECABF17EA82A600E3079E2BE1DB |