[pylons-discuss] migrating away from formencode?

['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.

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/22190c16-6299-41c3-a1e4-25fed04606ccn%40googlegroups.com.

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

[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:
https://github.com/pylons/deform

Deform 3.0.0 will use Bootstrap 4 for its templates and drop Python 2 support, 
although it might still work under Python 2.
https://github.com/Pylons/deform/milestone/3

--steve

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/5e5cc926-2729-67ee-cf2e-2834e0a4dfdf%40gmail.com.

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

['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 about migrating the 
code that interacts with forms.

FormEncode should my *last* Python2 library to support!  There is a 
longstanding bug on it file uploads breaking on Python3 . I've been using 
someone's stale PR as a patch for 2 years now, but that is just making 
everything too fragile so I try to keep all those apps running under 
Python2..


On Friday, October 2, 2020 at 3:40:22 PM UTC-4 Steve Piercy wrote:

> 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:
> https://github.com/pylons/deform
>
> Deform 3.0.0 will use Bootstrap 4 for its templates and drop Python 2 
> support, although it might still work under Python 2.
> https://github.com/Pylons/deform/milestone/3
>
> --steve
>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/d0a0d404-f081-41f8-865f-b073ed17bc78n%40googlegroups.com.

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

[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 Vanasco' via pylons-discuss wrote:
> 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 about migrating the 
> code that interacts with forms.
> 
> FormEncode should my *last* Python2 library to support!  There is a 
> longstanding bug on it file uploads breaking on Python3 . I've been using 
> someone's stale PR as a patch for 2 years now, but that is just making 
> everything too fragile so I try to keep all those apps running under Python2..
> 
> 
> On Friday, October 2, 2020 at 3:40:22 PM UTC-4 Steve Piercy wrote:
> 
> 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:
> https://github.com/pylons/deform
> 
> Deform 3.0.0 will use Bootstrap 4 for its templates and drop Python 2 
> support, although it might still work under Python 2.
> https://github.com/Pylons/deform/milestone/3
> 
> --steve
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "pylons-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to pylons-discuss+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pylons-discuss/d0a0d404-f081-41f8-865f-b073ed17bc78n%40googlegroups.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/6f0f2332-daa6-70a1-f148-2b32abdbb459%40gmail.com.

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

[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
> 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 Vanasco' via pylons-discuss wrote:
> > 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 about
> migrating the code that interacts with forms.
> >
> > FormEncode should my *last* Python2 library to support!  There is a
> longstanding bug on it file uploads breaking on Python3 . I've been using
> someone's stale PR as a patch for 2 years now, but that is just making
> everything too fragile so I try to keep all those apps running under
> Python2..
> >
> >
> > On Friday, October 2, 2020 at 3:40:22 PM UTC-4 Steve Piercy wrote:
> >
> > 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:
> > https://github.com/pylons/deform
> >
> > Deform 3.0.0 will use Bootstrap 4 for its templates and drop Python
> 2 support, although it might still work under Python 2.
> > https://github.com/Pylons/deform/milestone/3
> >
> > --steve
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "pylons-discuss" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to pylons-discuss+unsubscr...@googlegroups.com  pylons-discuss+unsubscr...@googlegroups.com>.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/pylons-discuss/d0a0d404-f081-41f8-865f-b073ed17bc78n%40googlegroups.com
> <
> https://groups.google.com/d/msgid/pylons-discuss/d0a0d404-f081-41f8-865f-b073ed17bc78n%40googlegroups.com?utm_medium=email&utm_source=footer
> >.
>
> --
> You received this message because you are subscribed to the Google Groups
> "pylons-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pylons-discuss+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pylons-discuss/6f0f2332-daa6-70a1-f148-2b32abdbb459%40gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pylons-discuss/CADj1%3D65K%2BtQ-wAehgrGcfH5eB0Bq1c4A1yFeLVsHTc2HWrcHzA%40mail.gmail.com.