Re: [pylons-discuss] migrating away from formencode?

2020-10-02 Thread Ian Wilson
I guess I'm still using formencode too with python3 but maybe I just worked around the bugs. Do you know what is holding up the release? Is it for sure a dead-end? - Ian On Fri, Oct 2, 2020 at 1:20 PM Steve Piercy wrote: > Deform uses Colander and Peppercorn. Use Colander for schemas and >

Re: [pylons-discuss] migrating away from formencode?

2020-10-02 Thread Steve Piercy
Deform uses Colander and Peppercorn. Use Colander for schemas and validation. There are no tutorials to migrate, but the demo should provide sufficient Colander schema examples for each Deform widget that you want. If you don't see something, ask! --steve On 10/2/20 1:00 PM, 'Jonathan

Re: [pylons-discuss] migrating away from formencode?

2020-10-02 Thread 'Jonathan Vanasco' via pylons-discuss
Thanks, Stev! Deform is high on the list; I should have been more specific - I'm looking for any guidelines/tutorials/tools to migrate the code from Formencode to other libraries. I have a lot of forms schemas/definitions to migrate. I wrote my own validation layer, so I'm not too worried

Re: [pylons-discuss] migrating away from formencode?

2020-10-02 Thread Steve Piercy
On 10/2/20 10:06 AM, 'Jonathan Vanasco' via pylons-discuss wrote: > Does anyone have tips/advice for migrating away from Formencode? For server side rendering of forms, Deform is under active development and works under both Python 2 and 3. Demo: https://deformdemo.pylonsproject.org/ GitHub:

[pylons-discuss] migrating away from formencode?

2020-10-02 Thread 'Jonathan Vanasco' via pylons-discuss
Does anyone have tips/advice for migrating away from Formencode? I have a lot of apps using Formencode and will likely need to move off it. It's no longer maintained, and needs to a patch/fork to run under Python3. That's been fine for internal apps, but it's a pain for open sourced efforts.