ptah.form

[dm73]

I'm frequently suffering by the many choices that are available in the
python ecosystem. Like, it is hard to make an informed choice between
Deform, pyramid_simpleform, wtforms and 20 other available libraries
without spending a lot of time on each of them. Now I see there is one
more: ptah.form.
I would like to know if there are some hard dependencies on ptah?
And why didn't you use any of the existing libraries / what were the
specific reasons to implement your own form generator?

Thanks,
dm73

[Nikolay Kim]

there are several reasons

1. initially it was port of z3c.form, but much more simple.
it was more than year ago, i was much more familiar with z3c.form

2. we need some serialization library, we used zope.schema
then switched to colander. over time we found that colander just adds
too much complexity.

we use ptah.form in 3 different subsystem. form ui, rest api and
settings. ptah.form is more about fields(schema) rather than form
generation

[dm73]

Thanks a lot Nikolay, that clears up a lot!

[Nikolay Kim]

and we do not force you to use ptah.form
its very easy to use any other form library, even for ptah management
module.