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 will try to find some time to spend on PyRJ and to sort out how I should proceed (this is related to the doubts I wrote in issue #68). Lately I'm biased toward implementing a serializer and a deserializer classes, that would collect such options and expose much simpler .encode()/.decode() methods. I'd really like to depart from the standard library json module where the exposed loads()/dumps() functions accept way too many options...
FWIW. I think keeping minimalistic compatibility with loads/dumps is all that is needed. No need to force the existing json option pattern onto your module. If someone wants parser specific unique features they can adapt to whatever that module provides. Basically, Im good with whatever you choose as related to #68
Activity
lelit commentedon Aug 1, 2017
Yes, reasonable.
I will try to find some time to spend on PyRJ and to sort out how I should proceed (this is related to the doubts I wrote in issue #68). Lately I'm biased toward implementing a serializer and a deserializer classes, that would collect such options and expose much simpler
.encode()/.decode()methods. I'd really like to depart from the standard library json module where the exposedloads()/dumps()functions accept way too many options...cavanaug commentedon Aug 1, 2017
FWIW. I think keeping minimalistic compatibility with loads/dumps is all that is needed. No need to force the existing json option pattern onto your module. If someone wants parser specific unique features they can adapt to whatever that module provides. Basically, Im good with whatever you choose as related to #68
New option `parse_mode` to select a more relaxed parser
New option `parse_mode` to select a more relaxed parser
lelit commentedon Aug 24, 2017
Implemented in the 0.2 version.