Sergey Polzunov

+1 to that, it would be extremely helpful

bump. this would be a super useful feature to have

My comment from another ticket stands here as well: I see no reason to enforce STIX2 spec on _python objects_, since enforcing it during serialisation would be enough. Until my...

> this was an implementation decision - to treat python objects as fully realized STIX objects that's unfortunate and limits how I can use the library. At the moment I...

> With this API we wanted to make it hard for people to create invalid STIX content. is there a reason, apart from educating people on STIX2 spec, to have...

simpler example: ```python In [3]: str(stix2.EqualityComparisonExpression(stix2.ObjectPath('port', ['value']), '1112')) Out[3]: 'port:value = 1112-02-28 00:00:00+00:00' ```

it is happening not only for numbers, I see some IPv4 addresses being converted into datetime string as well

this is the cause - https://github.com/oasis-open/cti-python-stix2/blob/ba2f63f745167ba9919b5a7ef1636460b8ab950d/stix2/patterns.py#L229

+1

@arcsector I'm not at EclecticIQ anymore, so I can't 😅 Unfortunately, this project is essentially dead, as you can see by the other open issues and the commit history