I finally decide to use only colander. I know it, I like it.
Thanks for your feedback everybody.
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to pylons-devel+u
I had not seen schematics before. The information on the pypi page does
look promising. And active is good. The only reason you might consider
limone at this point, I would think, is if you want to continue using your
Colander schemas instead of writing new schematics models. Conversion is
prob
Hi,
thanks for your answer.
I use Colander for a rest api (using Cornice) but this time
I d'like to consume that API and I will prefer to manipulate objects
instead of dict and simple types.
I will take a look at schematics which looks like limone and may
be more alive.
--
You received this mes
Hi Guillaume,
On Mon, Sep 29, 2014 at 12:49:42AM -0700, Guillaume Gauvrit wrote:
> I currently use colander but, for a new project, I like
> to have Python object instead of dict, the project I found
> via stackoverflow is limone.
>
> https://github.com/chrisrossi/limone
>
> It's not on the Pylo
It's dead in that no one is currently using or maintaining it. It was a
fun hack, but I never really found much use for it myself. I don't
remember super well, but I think it starts to show its rough edges with
complex schemas with many nested layers, but is really slick for simple,
shallow schem
Hi,
I currently use colander but, for a new project, I like
to have Python object instead of dict, the project I found
via stackoverflow is limone.
https://github.com/chrisrossi/limone
It's not on the Pylon official repository, still in alpha version,
and have not changed since 3 years. Is it a
