Vladimir Keleshev
Vladimir Keleshev
This is interesting. I never had such need myself, but could be useful. Let's wait and see if someone else finds this useful (and comments here).
@agutc interesting, but then you would only be able to use literals and simple values in that case.
That looks like a useful proposal.
I think this is useful, but I'm not 100% about the `{value}` syntax. Let me think if there is any better alternative.
Yes, it's ok that Travis is failing. However, I need to think about this feature.
I'm just thinking, what if someone wants to use format method on the error message. It would look awkward: ``` python Use(int, error='Invalid {}: {{value}}'.format('year')) ```
Hm, seems like `default=...` and `Default(...)` are redundant. If we introduce something like that into **schema** we need to pick one I think. And I'm not sure which one.
I never needed this feature, so I'm not totally sure which API is better yet.
Sorry for taking so long. Recently I actually needed to have some default functionality with schema. Here are my thoughts: The default value should be used only if no value...
> Last but not least, you mentioned that you would prefer not relying on inheritance for defaults handling (see point 2 on top of that message). Could you elaborate on...