Colm O'Connor

Your PR basically looks perfect (thanks for accommodating my custom testing framework. it's appreciated!), but I'm still somewhat uncomfortable about this ".inf" thing. I'm sort of ok with accepting ".inf"...

It seems that the IEEE 754 standard doesn't really have an opinion on text representation of inf and nan (which is why everybody seems to do it differently). I'm leaning...

Yes, I agree it's disgusting :) I'm almost inclined to say that it shouldn't even accept ".nan", but I know if we do that then people who have YAML 1.2...

Yes, please do. I'll merge and release a new version on pypi once you're done. Thank you for doing this.

Yep no rush. On Mon, 10 Aug 2020, 17:03 Danilo Silva, wrote: > Ok, nice! I think I can finish that tomorrow, ok? > > Thank you for the discussion....

>StrictYAML aims to be fully roundtripable, which means there should only be one valid representation. Actually, come to think of it, it should still roundtrip ok. Put .inf in and...

>My vote is to make the output INF and NaN Is there a reason you want these in particular to be the default versions? (i.e. as_document({"x": float(nan)}).as_yaml() == "x :...

What are the use cases? Can you give an example? On Wed, 3 Feb 2021, 18:56 Yakov Goldberg, wrote: > Hi, > I wonder how could I support the following:...

Would you be using basic and extended on the same document depending on something within the document or would you have some other sort of logic to determine whether to...

Sounds like you might want https://hitchdev.com/strictyaml/using/alpha/howto/revalidation/ On Wed, Feb 3, 2021 at 7:58 PM Yakov Goldberg wrote: > I was thinking of smth like that: > > def func1(document): >...