You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I managed to solved some issues in my journey into using pyasn1 for MMS so far, but I hit a wall on this one:
Decoding seems fine, but when I'm trying to encode an object that has an optional property, the property is suddenly added to the object even tho I did not specify it.
For example, the property "listOfModifier" in the example bellow:
- Removed default initializer from `SequenceOf`/`SetOf` types to ensure
consistent behaviour with the rest of ASN.1 types. Before this change,
`SequenceOf`/`SetOf` instances immediately become value objects
behaving like an empty list. With this change, `SequenceOf`/`SetOf`
objects remain schema objects unless a component is added or
`.clear()` is called.
In my case, it seems that I still have objects behaving as lists even when empty.
It possible to troubleshoot this issue by enabling debugging in your code:
from pyasn1 import debug
debug.setLogger(debug.Debug('encoder'))
Hello dear pyasn1 maintainers,
I managed to solved some issues in my journey into using pyasn1 for MMS so far, but I hit a wall on this one:
Decoding seems fine, but when I'm trying to encode an object that has an optional property, the property is suddenly added to the object even tho I did not specify it.
For example, the property "listOfModifier" in the example bellow:
The printed result is:
Definition files used:
https://pastebin.com/JitDfL2R
(named it mms_classes.py)
The text was updated successfully, but these errors were encountered: