From: Clark C . E. <cc...@cl...> - 2002-08-06 23:45:11
|
Hello Brian! I'll let Steve address the other items, but from what I know he's not going to be able to do any further work on PyYaml for a wee bit. I'm sure you are welcome to "hack" it some... support for explicit transfers could be much better, etc. | | - Using a magic method called __yaml__ is evil | Steve originally had to_yaml for the method name. I think that __yaml__ is entirely appropriate: - It is quite magical and is othogonal to application concerns. It's not any where near a "normal" function. - It follows the same pattern as __str__, __iter__, and __repr__ that is, it returns an object which complies with the appropriate protocol. - It won't have a name clash. YAML is big enough now that no one would be using __yaml__ for anything. Eventually yaml may even get popular enough to be included in the Python core, and in this case __yaml__ will be entirely appropriate. So, overall, I think that __yaml__ is the best route and I've thought about this quite hard. As for the protocol for __yaml__, now that's something that needs some deep thought. It really needs to expect a tuple (type-family, value) instead of just a value for starters. Ideally the value would be an iterator. Best, Clark |