tree 5385178e4699ee2fe1b1c4ce446564aefde5a1f2
parent a2a8bbbcf2dff6e625ce6d601f1af9e84270c049
author Ilya Etingof <etingof@gmail.com> 1564562205 +0200
committer GitHub <noreply@github.com> 1564562205 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJdQVMdCRBK7hj4Ov3rIwAAdHIIAHjVfKpSRrohNcrnavN/7eAm
 trvGk0wJ7QCBMJRBW2llTG6MQxM/O1wQVeO9OZlOvPRZbHP9ncrQbnXOoJo7gta4
 qV9eX2xCuVEQHR6w2xCDXayNZJcJAVNNO21ITfofW3Y11xVWAfycAfoRRdLJpsTy
 WPKjR96p+pozMYlN6EO4oc/wc65aDFZRX/w5xa5FYvrGHWHMgmJ7MeWqlpBthjch
 99e19n/X4kNIEeWCldFGeL+Tid5F37vW0KwlGNLWRceBKW03ix8Bke36lxm1x/eS
 W/shYqyo5fJl5UO/xZimkO9jBGZ3VkMVpDz6p8l0ijMX8BGSJW2LchRPHxMJkpk=
 =PLxx
 -----END PGP SIGNATURE-----
 

Make SIZE OF constraint operational (#46)

Changes `ValueSizeConstraint` erroneously applied to `SequenceOf`
and `SetOf` objects via `subtypeConstraint` attribute to be applied
via `sizeSpec` attribute.

Although `sizeSpec` takes the same constraint objects as
`subtypeConstraint`, the former is only verified on de/serialization
i.e. when the [constructed] object at hand is fully populated, while
the latter is applied to [scalar] types at the moment of instantiation.

This change also bumps pyasn1 requirement to 0.4.6.